Gang Aft Agley

Seems the best answer for where I’ve been today.

/ web

/web

I didn’t catch it until I went to look at a page and received a 404 error, at which point I poked around and figured out what had happened.

Yesterday I noticed that the server I’m hosted on had needed to be restarted, yet my cron job to restart the lighttpd server had not done its job.

Today as I was getting ready to post something I noticed I was down again. This time because I exceeded my disk quota. So for both days I apologize for the outage, and I hope I won’t have the same issues again.

I have requested a port number from textdrive to run lighttpd on, so I can finally ditch the apache cgi/fcgi issues. The port they assigned me already has lighttpd running on it so I need to get that resolved before I can get it running. Testing the configuration on another port number I was amazed at the speed increase.

The site is crawling for a while—reduced to cgi as opposed to fcgi to run it. It has been flaky for a few days, and I finally got sick of not being able to get to the admin section.

Now that I have Lighttpd working at home and can look at it, I might finally make that request to my hosting provider and get it running for the site.

I don’t know what happened, but the server stopped responding for a few minutes. Dns had me pointed to the right location, and the server would respond to a ping but I couldn’t get any web pages to respond. Telnet on port 80 was stopped, yet I could start WEBrick and connect through port 3000. I tried switching back to CGI from FCGI and that still didn’t help.

In desperation I tried calling the webroot through the servers name using my ~user directory. that seemed to be all it needed to kickstart it all back up and we are off and running again.