{"id":1058,"date":"2011-11-14T15:58:35","date_gmt":"2011-11-14T23:58:35","guid":{"rendered":"http:\/\/digitalnigel.com\/wordpress\/?p=1058"},"modified":"2012-01-23T13:48:08","modified_gmt":"2012-01-23T21:48:08","slug":"asterisk-memory-usage","status":"publish","type":"post","link":"https:\/\/digitalnigel.com\/wordpress\/?p=1058","title":{"rendered":"Asterisk Memory Usage"},"content":{"rendered":"

So, I recently went and updated my google password, as I do every so often, and managed to get most things updated fairly quickly. However, it seems I forgot about my asterisk server.<\/p>\n

I have my asterisk server configured to connect in with my Google Voice account via jabber, just like GTalk does, so I can use my desk phone to make and receive phone calls. Seeing as how I don’t make or receive a ton of calls, I didn’t really notice that asterisk could no longer connect to Google Voice. That is, until the server started crashing…<\/p>\n

At first it crashed, and I didn’t really look too deeply into it. The server I have asterisk running on is a VM running on VirtualBox on my mac. VirtualBox isn’t known for having rock solid kernel drivers, so I chocked it up to a fluke. Then I went and took a look this afternoon at my system stats graphs, and noticed the ram was totally used up, and the swap space was rapidly diminishing. Doing a little digging I saw it was the asterisk process, and logging into the asterisk CLI, saw a billion errors about it complaining of an incorrect password.<\/p>\n

A-HA!<\/p>\n

Anyway, to cut a long story short, I fixed the password and now asterisk is happy and not making my server all crashy. Also I filed a bug report. I kinda figure crashing a system is not the intended failure mode for an incorrect password.<\/p>\n

Here’s some pretty graphs of memory and swap usage during the crashy period.<\/p>\n