System performance view gone
A day usually starts checking the operator logs, system performance and some other things that passed yesterday. This morning, the HyperSpi views on the system performnace were missing – the logical used wasn’t defined properly. Quite likely that it wasn’t working yesterday either – because I used the WASD startup procedure where HyperSpi are defined as well. This probably messed up the logical. That means there are no HyperSpi statistics from the time I ran the procedure after upgrading the webserver. After I corrected the logical, statistics resumed. So there is a gap of 2 days. But I do have the T4 data!
MySql keeps raising issues.
The watcher procedure lists when MySQL is restarted, and the result so far, for 2008:
MYSQL Restarted 2008-01-14 07:31:00.23
MYSQL Restarted 2008-01-21 17:25:00.07
MYSQL Restarted 2008-01-21 22:10:00.23
MYSQL Restarted 2008-02-06 03:35:00.43
MYSQL Restarted 2008-02-17 19:50:00.08
MYSQL Restarted 2008-02-17 20:35:00.63
MYSQL Restarted 2008-03-08 21:35:00.35
MYSQL Restarted 2008-03-10 07:35:00.27
MYSQL Restarted 2008-03-13 21:20:00.51
MYSQL Restarted 2008-03-23 20:51:00.08
MYSQL Restarted 2008-03-24 23:06:00.11
MYSQL Restarted 2008-03-28 07:06:00.24
MYSQL Restarted 2008-03-30 20:36:00.25
MYSQL Restarted 2008-04-01 18:21:00.26
MYSQL Restarted 2008-04-02 21:21:00.35
MYSQL Restarted 2008-04-04 11:51:00.51
WordPress 2.5 IS indeed faster than 2.3, and though it looks like the database engine is used more efficiently (staements are checked more rigourously before actually executing them) it still happens quite often that MySQL runs out of core – and so does PHP. But I’ll need to dig far deeper to find out exactly. A specific T4 examination may show something.
Funny, though, that teh Wiki – being a Python application) seems to have no problem at all. It’s not fast but so far I’ve seen no weird messages stating that free memory is low, or any weird messages. It simply – works.
Perhaps installing MySQL 5.1-22 might help, but I’m afraid it will require an even bigger memory footprint than the current average of 30Mb (according WASD’s Admin SYSTEM output). It’s only feasable if it’s more stable under stress 😉
Spam filter message
There was one funny thing in the operator log:
%%%%%%%%%%% OPCOM 3-APR-2008 09:30:39.87 %%%%%%%%%%%
Message from user SYSTEM on DIANA
%PTSMTP-E-SHAREPRIV, workers require SHARE privilege; setsockopt of UXC$C_SHARE failed
-SYSTEM-F-PROTOCOL, network protocol error
There was no big load on the mail system at this moment, so where this came from – I don’t know. PTSMPT – the spam filter – continued without a problem, with 2 worker processes; a thirrd was not needed at this point, unless there have been messages rejected because of DNS blacklisted senders, or relay attempts, So I ran the statistics procedure:
PMAS statistics for 04
Total messages : 460 = 100.0 o/o
DNS Blacklisted : 305 = 66.3 o/o (Files: 3)
Relay attempts : 3 = .6 o/o (Files: 1)
Processed by PMAS : 152 = 33.0 o/o (Files: 3)
Discarded : 45 = 29.6 o/o (processed), 9.7 o/o (all)
Quarantained : 47 = 30.9 o/o (processed), 10.2 o/o (all)
Delivered : 60 = 39.4 o/o (processed), 13.0 o/o (all)
305 blacklisted messages, in 3 days (today’s files haven’t been renamed yet), is about 3000 in one month. Well, more than usual, but not really extreme. But possible. I would have to scrutenize the logfile, I know the time:
3-APR-2008 09:27:03.63: Address (88.227.51.122) blacklisted (4)
3-APR-2008 09:28:08.69: Address (89.218.166.171) blacklisted (4)
3-APR-2008 09:36:36.56: Address (81.5.15.231) blacklisted (4)
3-APR-2008 09:36:44.76: Address (219.148.119.178) blacklisted (4)
Nor weirdness in other logs.
It’s been considered just an incident.