Major Downtime Today
We’re back up. Sorry for the long delay. It’s amazing what one line of code can do.
Earlier today I removed an administrative feature from the site that logs any site errors to the database. Oh, the irony. I had switched in some newer code that actually sends me an email whenever there are any problems. It’s much more efficient and it reaches me wherever I am.
But I had forgotten to remove a line of code that looks for the old feature when the site starts up. So when I restarted the server, the site choked because it was looking for the old code but couldn’t find it.
Boom! Down goes Jetrecord.
It took me a while to figure out what was going on. I assumed (as all programmers do) that it must be a server error or an operating system error. Surely, it’s anything but my own code!
But no, it was my own stupidity. Thankfully, everything’s fine. Just a bruised ego. I’m sorry if you tried to access the site during the downtime. It’s a real bummer. My top priority right now is site and code stability. I’m writing more tests for the code and adding in lots of system administration tasks to the server behind the scenes.
I’m certain that things like this will happen again. They always do. But hopefully they’ll happen a lot less often.
Cheers,
Harry
Jetrecord is an online logbook for pilots like you.
