Business as usual
As might be expected, the monthly maintenance job showed nothing unusual:
PMAS statistics for July
Total messages : 4159 = 100.0 o/o
DNS Blacklisted : 0 = .0 o/o (Files: 0)
Relay attempts : 521 = 12.5 o/o (Files: 28)
Accepted by PMAS : 3638 = 87.4 o/o (Files: 31)
Handled by explicit rule
Rejected : 2848 = 78.2 o/o (processed), 68.4 o/o (all)
Accepted : 225 = 6.1 o/o (processed), 5.4 o/o (all)
Handled by content
Discarded : 351 = 9.6 o/o (processed), 8.4 o/o (all)
Quarantained : 201 = 5.5 o/o (processed), 4.8 o/o (all)
Delivered : 13 = .3 o/o (processed), .3 o/o (all)
relay attempts were concentrated on three days: 9th (162, between 05:45 and 06:02, from 23.254.215.195), 16th (162, between 09:05 and 09:22, from 23.254.215.20) and 29th (166, between 06:33 and 07:29, from 104.168.147.10); All used bogus senders using my domain, and recipient was the same on gmail.com. both networks (23.254.128.0/17 and 104.168.128.0/17 refer to hosting company hostwinds.com, based in the US. They have been notified.
ok, that on maintenance.
There is not news on mariaDB. Mark berrymann was not able to reproduce the problem but may have found something. As soon as he has a new version, I’;; give it another try.
However, it may not really be an issue with MariaDB. the MySQL version I’m running now isn’t the fastest either, and when running PHP 5.4, I get failing connections as well, and the log shows timeouts on MySQL. So it might well be a matter of the database – WordPress in particular. Multiple blogs in one database might be a bad idea ?? Something to discuss with Mark – and WordPress The problem is how to get performance data frem MySQL..
And on Diana, I imported the MySQL database into MariaDB using the script provided. So if there is something rotten in the WordPress database, it will be rotten under MaraiaDB as well…
But there IS something Mark will have to look into: On the Itanium system MariaDB cannot be started with a new database: it may create one but runs into errors when starting. This is to be executed using a telnet session to catch all data. One thing is needed anyway – but it seems unrelated to MariaDB, more to SSL: when creating the (self-signed) certificates SSLROOT: is requested, but that is not present; SSL$ROOT is. So to get around it, define SSLROOT before attempting to start MySQL or the installation script:
$ DEFINE/SYSTEM SSLROOT SSL$ROOT:/TRANSLATION=CONCEALED
(you can also use the full definition of SSL$ROOT but this works as well).
That way, the certificate is created, the my.cnf file is created but starting MariaDB fails: This signals a number of errors and aborts….
Just done: WP updated (4.8.1)