Latest news on PHP
Got two messages from Mark:
1. PHPWASD.EXE in the kit is no good.
2. He reviewed all kits and rebuilt them when needed – there should be no more mismatches any more.
To be tested tonight, or during the weekend.
Evening update
I downloaded the updated kit from Mark’s site and installed it. First, it didn’t work since PHPWASD: couldn’t access PHPSHR, and later, it seemed that the MySQL extension was missing. The reason was just a matter of file protections’, I had to change the n all, and edit php.ini to enable the extensions (PHP_MysQL.EXE in particular -PHP_MySQLI.EXE alone wasn’t enough for this version of WordPress) but now it works, though it looks to be a bit slower. However, I should NOW be able to update to WP 4.2.2. Fingers crossed 🙂
Evening update 2
Updating WP means: revert to default theme and disable plugins – after creating a backup (so if it fails, it’s easy to revert to the stae before the update)/ No it should be a matter of changing the logical (the second location should be where the new version of WordPress is stored, in my case WP42:), than restart the webserver (to remove any running PHPWASD images), and start the blog. It does start with the mentioning that WP version has been changed and that the database needs an update, It starts – and stops without a notice, somewhere in step one of the process.
So I had to revert to the state prior to the update, by simply restoring the database, change the logical back to the original version and restart WASD.
Now it’s a matter of finding out what is going on….
It may be related to the resource limits in PHP.INI:
;;;;;;;;;;;;;;;;;;;
; Resource Limits ;
;;;;;;;;;;;;;;;;;;;
max_execution_time = 30 ; Maximum execution time of each script, in seconds
max_input_time = 60 ; Maximum amount of time each script may spend parsing request data
;max_input_nesting_level = 64 ; Maximum input variable nesting level
memory_limit = 128M ; Maximum amount of memory a script may consume (128MB)
that may be too low, keeping in mind that this system is limited in resources…
Maintenance
It has been a few days ago that the maintenance jib has run. No surprises:
PMAS statistics for May
Total messages : 1026 = 100.0 o/o
DNS Blacklisted : 0 = .0 o/o (Files: 0)
Relay attempts : 88 = 8.5 o/o (Files: 31)
Accepted by PMAS : 938 = 91.4 o/o (Files: 31)
Handled by explicit rule
Rejected : 387 = 41.2 o/o (processed), 37.7 o/o (all)
Accepted : 197 = 21.0 o/o (processed), 19.2 o/o (all)
Handled by content
Discarded : 152 = 16.2 o/o (processed), 14.8 o/o (all)
Quarantained : 185 = 19.7 o/o (processed), 18.0 o/o (all)
Delivered : 17 = 1.8 o/o (processed), 1.6 o/o (all)
The number of relay attempts has been minimal this month: No file exceeded 10 blocks; there have been some, of course, but only three files were large enough (over 2K in size) to be examined: mail was sent from addresses 173.254.223.72 , |185.60.229.89 and 5.79.68.231; faked senders, no doubt, since From: was either empty, a (non-existing) user from grootersnet.nl (and I do know my users, and my address :)) of admin from a site that is not related to the address it is sent from.
