Power outage
A lightbulb in our bedroom blew up when it was lit – and caused a shortcut, causing the fuse to blow. That meant the firts floor was out of power – and, due to the wiring, the datacenter lost power as well. To allow power top b restored, I had to switch off the disks, because the whole lot: Alpha + HSZ50 + BA356 (including 7 disks) all on power at the same time is too much. It took about 15 minutes to get the system online and do some minor tests to see if everything was in working order again.
Well, it seems so. The big test will be tomorrow 🙂
01-Apr-2009
System Management
A new month means checking things and clearing older files.
Mail statistics
PMAS statistics for March
Total messages : 3680 = 100.0 o/o
DNS Blacklisted : 2520 = 68.4 o/o (Files: 31)
Relay attempts : 123 = 3.3 o/o (Files: 31)
Processed by PMAS : 1037 = 28.1 o/o (Files: 31)
Discarded : 295 = 28.4 o/o (processed), 8.0 o/o (all)
Quarantained : 326 = 31.4 o/o (processed), 8.8 o/o (all)
Delivered : 416 = 40.1 o/o (processed), 11.3 o/o (all)
The relative high number of releay attempts is spread over the month, with a max of 17 on the 4th – weirdly enough quite a number stating to be form support@microsoft.com. As usual there are the yahoo.tw addresses, I’ve seen them more trying to relay over my server. Not that it works 🙂
Other maintenance
Of course, I archived the logfiles.
Patches have been downloaded, but installation will have to wait some time. This weekend has already been reserved, none of them is that urgent that an installation ASAP is required. The VMS system is working well over three months:
OpenVMS V8.3 on node DIANA 1-APR-2009 22:20:04.71 Uptime 98 00:36:36
so it’s hard to imagine that a fortnight extra would do any harm…
April joke?
would be another Big Bang on the nasty Conficker virus, sending out massive amounts of SPAM. But up to this moment (20:30 UTC), at least my server didn’t notice much since midnight:
PMAS statistics for April
Total messages : 125 = 100.0 o/o
DNS Blacklisted : 77 = 61.6 o/o (Files: 1)
Relay attempts : 17 = 13.6 o/o (Files: 1)
Processed by PMAS : 31 = 24.8 o/o (Files: 1)
Discarded : 8 = 25.8 o/o (processed), 6.4 o/o (all)
Quarantained : 7 = 22.5 o/o (processed), 5.6 o/o (all)
Delivered : 16 = 51.6 o/o (processed), 12.8 o/o (all)
It could of course change in the next four hours, but my suspicion it’s one of those jokes.
(But checking a newspaper site on the subject a few moments ago, the Java application crashed and the server became unvailable:
Service Temporarily Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Well, I tried but it didn’t help very much …
I may have trouble with PHP at times, but not as drastic as this 🙂
WASD problem
Something weird is going on with WASD.
I have seven services active. So in a list of services, I would expect to show seven as well. But after some time, the number of entries increases with the same number: 14, 21…up to over 100. At that time I usually restart the server so the list counts 7 services.
It seems I’m the only one that encounters the problem – and I’m trying to find out what causes the behaviour. It might be the PHP or Python engine??
It’s not fatal, at least, I think.