Tonight I gave a talk at the Node.js in the wild meetup about Debugging Node.js Applications.
The slides are available at: http://life.neophi.com/danielr/files/DebuggingNodejsApplications.pdf
The sample code used is available at: https://github.com/NeoPhi/debugging
A video of the talk was made and is available at: http://www.youtube.com/watch?v=JNSy1roM82k
Thank you to all that came and the discussion we had.
While recently trying to signup for a new banking service that allowed me to tie authentication to my mobile phone, whenever I had the service send an SMS authorization code to my phone I never got it. I had a friend send me an SMS and that arrived fine. I then remembered for a long time I'd not been getting Zipcar SMS messages about extending my reservation. Even though my Zipcar account said I had two-way messaging activated when I disabled and tried to reenable the service I ran into the same problem. Turns out there are two different types of SMS. Regular phone to phone SMS messages and another type known as short codes. A quick call to T-Mobile's awesome support and I found out, unbeknownst to me, a content block had gotten put on my account for SMS short codes. Once removed everything started working again. Yay!
With the Superbowl two weeks away and this past weekend a resounding success for RumbleTV Playoffs, I was able to take a little breather today and finishing sorting, culling, and posting my pictures from my recent Antarctic trip. Enjoy.
For a long time now I've been posting the books that I've read with my reviews on this site. My original intent with posting books on this blog was to capture the notes I took while reading. Turns out I've very rarely or ever gone back to those notes. I suspect it is a case that the act of writing down the note provides more meaning than the note itself. For a long time now I've been a member of Goodreads and track my books and reviews there since they give me neat statistics and recommendations. Instead of cross posting you can just follow my Goodreads feed or friend me on Goodreads.
I recently noticed I was getting low on space on one of my EBS volumes I mount on my EC2 server. After doing some research (aka Googling) it seemed like a simple procedure: umount, snapshot, create volume, resize, and mount. I even found a concise page that detailed resizing an EBS volume with sample commands. However when I got to the resize step I ran into an error along the lines of "The filesystem is already XXX blocks long. Nothing to do!". Turns out I didn't mount the complete EBS volume as a drive but instead partitioned it. The snapshot and create volume steps had increased the size of the EBS volume but not my partition. Without a graphical interface the prevailing recommendation to use gparted didn't help. Thankfully I stumbled upon another blog posting about resizing partitions using fdisk without losing data. While that post dealt with another virtual server service the same basic principles applied. After carefully deleting and recreating the partition on my EBS volume keeping the starting sector and file type the same resize2fs finally worked and I was off to the races. In retrospect the partition table hacking makes sense that it would work but isn't something I would have thought to try.
