Skip to content | Skip to navigation
I'm afraid your observation may be correct. The server was offline yesterday sometime around mid-afternoon until I got home around 20:00 local time. Apparently, in addition to not being quite as fast as promised, my 'net connection has developed the habit of dying in a very creative way once or twice a week: the line is still up, status is OK, but no traffic gets through. I'm sorry for the downtime (and a bit annoyed myself) and am planning to implement a watchdog of some kind.
(If the outage really really bugs you, feel free to call Telecom FL and tell them to improve their lousy service or at least slash their incredible prices in half.)
Consider yourself hugged.
If you need some help - just ask ;)
I could eg. set up a pseudo-cron checking on my hosting account to check if NAO is still alive or add a cron-job to my developer system at work. Last one would only be available during the time I'm at the job, but offers the full row of GNU/Linux tools, while the first option would only offer some primitive 'is this HTML data still available?'-check.
cu, w0lf.
Naturally, I love Jesus very much. I love him so much that I'd like to crucify him all over again.
Today, it was down or at least unreachable once again, during the morning till about now.
If you need some help with an automated ping- or webserver watch-service, I could help out by:
a) using a pseudo-cronjob installed at my site
b) setting up a cron job at this computer (only on during working times, that'll be 9:00 a.m. till 6 p.m., sometimes longer)
cu, w0lf.
Naturally, I love Jesus very much. I love him so much that I'd like to crucify him all over again.
That's nice, but I can already determine when the server is offline (my work PC checks it regularly when I'm logged in, plus I also have a handful of outside servers myself which I could use for that purpose). The tricky part is obviously not to detect an outage but to fix it, so unless you can set up a cron job that lets me sneak out of the office without my boss noticing, or that kicks my ISP's network staff's ass, there's not much you can do from the outside.
As for fixing it, I've written a script to reset the connection when it detects an outage. It's already gotten the server back online several times; to handle today's outage it needed a small change.
Consider yourself hugged.