#!/bin/bash

ip_url="http://automation.whatismyip.com/n09230945.asp"

oldip=`grep externip /etc/asterisk/sip.conf |sed 's/;.*//' |grep -v ^$ |sed s/.*=\ *//`
ip=`curl -s "$ip_url" |head -n 1`

if [ "$oldip" != "$ip" ]
then
        #echo "Updating IP"
        sed -i "s/externip = $oldip/externip = $ip/" /etc/asterisk/sip.conf
        asterisk -r -x "core reload"

fi

I put it in /etc/cron.d/asterisk-externip as follows:

# Update Asterisk's SIP External IP
3,8,13,18,23,28,33,38,43,48,53,58 * * * * root asterisk_update_externip

Enjoy!

#!/usr/bin/env ruby

require 'optparse'

options = {}
optparse = OptionParser.new do |opts|
  opts.banner = "Usage: #{$0} [OPTIONS]"

  opts.on('-w', '--warn PCT', 'Warn if memory usage goes over PCT') do |val|
    options[:warn_pct] = val.to_i
  end

  opts.on('-c', '--crit PCT', 'Critical if memory usage goes over PCT') do |val|
    options[:crit_pct] = val.to_i
  end

  opts.on('-h', '--help', 'Display this screen') do
    puts opts
    exit
  end
end
optparse.parse!

unless options[:crit_pct] && options[:warn_pct]
  puts optparse.help
  exit
end

# Get the stats from /proc
mem = File.readlines("/proc/meminfo").inject({}) {|m,x| k,v = x.split(/:?\s+/); m[k] = v.to_i; m}
free = mem['MemFree'] + mem['Buffers'] + mem['Cached']
total = mem['MemTotal']
used = total - free
pct_used = used * 100 / total

if pct_used > options[:crit_pct]
  puts "MEMORY CRTIICAL - #{pct_used}% used"
  exit 2
elsif pct_used > options[:warn_pct]
  puts "MEMORY WARNING -  #{pct_used}% used"
  exit 1
else
  puts "MEMORY OK - #{pct_used}% used"
end

This goes in /usr/lib/nagios/plugins/check_memory . You can add it to nrpe.cfg like so:

command[check_memory]=/usr/lib/nagios/plugins/check_memory  -w 75 -c 85

Update: Found a shell script here

Today I started searching for a better solution and found a patch for PuTTY by Diomidis Spinellis.  Unfortunately it was for an old version of PuTTY.  However with a little effort I updated the patch to PuTTY 0.60.

Here’s how it works:

1. Use the modified PuTTY
2. When connecting (or after) click on the Terminal setting, and under “Printer to send ANSI printer output to” select “Windows clipboard”
3. Add the following to your .bashrc (or the appropriate startup file for your shell)  To use it immediately, be sure to type “source .bashrc”

   function wcl {
     echo -ne '\e''[5i'
     cat $*
     echo -ne '\e''[4i'
     echo "Copied to Windows clipboard" 1>&2
   }
   

   }

4. Now when you want some text out of SSH, just pipe it to wcl.   For instance, “ls -la |wcl” places the output of “ls -la” in your Windows clipboard.

Modified PuTTY 0.60 executable

Patch for PuTTY 0.60

I still want to be notified when new versions come out (via my daily upgrade script) so I can recompile it, so I updated the version as little as possible by adding an “a” to the end of it.  

In the source directory, I edited debian/changelog .  The first line said

ffmpeg (3:0.cvs20070307-5ubuntu7.3) hardy-security; urgency=low

The error message was “unable to get local issuer certificate.”  I thought, no big deal, there must be an easy way to get SOAP4R to find all the root CA certificates.  Unfortunately it took a while searching Google to find the right answer, so I’m posting it here to make it easier for the next person (which just might be me next week).

It turns out SOAP4R will read a file called “soap/property” in your ruby library path (which can usually be the directory your app is in).  You can place certain configuration options in this file to control how SOAP4R behaves.  In this case, I needed to add

client.protocol.http.ssl_config.ca_file=/etc/ssl/certs/ca-certificates.crt


This fixed the “unable to get local issuer certificate” error right away.

There was another problem though; it was complaining about the hostname not matching the certificate. Since I’m using a wildcard certificate, I assume this means OpenSSL doesn’t respect wildcard certificates. I grudgingly added this to soap/property file

client.protocol.http.ssl_config.verify_mode=OpenSSL::SSL::VERIFY_NONE

And it’s fine now.

After I started setting up SSL, I realized that I might run into trouble because Apache has always said you can’t combine NameVirtualHost and SSL. The reason for this is that the SSL session is established before the HTTP headers are sent. Since NameVirtualHost relies on the HTTP Host header, which is unavailable since it hasn’t yet been sent at the time SSL is being negotiated, Apache can only use a single SSL cert per combination of IP and port.

So my thought was this should technically not be a problem since both of my hostnames are under the same domain and I have that fancy wildcard certificate for both virtual hosts. I thought Apache just might be cool enough to send the first certificate it finds, but still respect the HTTP Host header and send the request to the right virtual host.

Guess what… Apache is indeed that cool. I now have x.stockpr.com and y.stockpr.com on the same IP and port with two different virtual hosts, sharing the same certificate.

Won’t exactly revolutionize web hosting, but it definitely made my day night go a little easier. (Of course if you read my last post, something else more than made up for it)

Google revealed that I’m not the first to run into this problem with an EC2 instance. Several posts said to install the Xen version of libc

apt-get install libc6-xen 

and do this:

echo "hwcap 0 nosegneg" > /etc/ld.so.conf.d/libc6-xen.conf; ldconfig

And then reboot.

This seems to have fixed it, but I’m wondering why this was either not included in the Ubuntu AMI I’m using or somehow got undone.

The first time I tried to bundle the volume I noticed it was taking a very long time.  I had incorrectly assumed that ec2-bundle-vol would automatically exclude any EBS volumes.  Instead, it only excludes a static list of directories, so I had to add the EBS volume (/mail) to the exclusion list.  

Here are the commands I used to bundle the volume:

ec2-bundle-vol -k /mnt/aws-config/pk-xxxxx.pem \
-c /mnt/aws-config/cert-xxxx.pem \
-u xxxx-xxxx-xxxx -d /mnt/bundle \
-p image-name-20080924
-e /mail

ec2-upload-bundle -b ae-ami \
-m /mnt/bundle/image-name-20080924.manifest.xml \
-a xxxx -s xxxx

ec2reg bucket-name/image-name-20080924.manifest.xml

The next step will be to figure out how to set up the AMI so it will have a swap partition when it boots up in a new instance.