botanix faw down go boom
Friday, 3 January 2003 08:38Yesterday, I noticed that /tmp on our machine botanix was full. I deleted a couple of files I still had lying around there and had a look to see what was wrong.
Apparently, the database had been writing two error messages every hour for the past several days. The error log file itself wasn't that big, and the info dumps even smaller, but the fact that there were two of them every hour caused them to add up.
I called Ralf and ( got some advice, and then ) called reboot without a time argument. I saw the message "Reboot time reached" (or similar) on my terminal window, then another couple of lines and then my connection was gone.
Oh good, I thought, and waited a while. Then I went to the server room, but when I switched on the console, it was blank. Oops. After twenty minutes, Swetlana came by and asked whether botanix was back up. I had another look but couldn't connect to it.
( And botanix didn't come back up again. )
Edit 09:00: An HP chap might be coming over today... probably not this morning, though. I'll have to think of something else to do. Argh.
Apparently, the database had been writing two error messages every hour for the past several days. The error log file itself wasn't that big, and the info dumps even smaller, but the fact that there were two of them every hour caused them to add up.
I called Ralf and ( got some advice, and then ) called reboot without a time argument. I saw the message "Reboot time reached" (or similar) on my terminal window, then another couple of lines and then my connection was gone.
Oh good, I thought, and waited a while. Then I went to the server room, but when I switched on the console, it was blank. Oops. After twenty minutes, Swetlana came by and asked whether botanix was back up. I had another look but couldn't connect to it.
( And botanix didn't come back up again. )
Edit 09:00: An HP chap might be coming over today... probably not this morning, though. I'll have to think of something else to do. Argh.