More on PHP
More testing done tonight.
The “zend mm heap corruption” issue has been solved, more or less. Mark notified to define a logical (/SYSTEM since it is to be used by every PHP process) to bypass the Zend memory manager: Set it to “0” and the problem would be solved. It was – but another appeared: it looks it slows the system down – which makes sense if I have read the doc well: zend allocates one chunk of memory, and keeps its own administration (and fails sometimes, hence the error) and with that bypassed, each allocation means another call to the OS to get a few bytes. Far less efficient, thouh it shouldn’t matter that much…
WordPress was the first to be tried. Normal access is no problem, as it has always been. The admin pages now come up nicely, most activities can indeed be done – except for uploading a file. I checked the protections of the upload directories – upload should create a new directory and put the files on that, so the processes require RWE acces to the main directory (wp-content.upload] ) and all directories below. But a new directroy [2009] is not created, despite the protetection or W:REW on [wp-content]uploads.dir… Not even a message – expect when the file is not that big: I got “Error writing to disk” when I tried to upload a 40K image – but a 400K image will silently be discarded.
PHPMyAdmin was even more frustrating.
The login pages may appear with, or without CSS applied. But at least, login is possible. But than things go wrong
and it all takes A LOT of time…
Observing the system, it seems I got 4 instances of PHPWASD running, and all working on PHPMyAdmin (since that was the only application I was working on). That also happened with WordPress, but at least, that didn’t get messed up.
What’s more: it has worked before; I created the WP263 database with it, but today, I could’t get at a point that the 284 database was created. I tried whenever the main page appeared, but without notice, the login screen reappeared after some time – and the new database was not created…..
WATCH didn’t show something weird – it all looked fine. But I’ll have to scrutenize the output to really understand the process.
Perhaps the latest release of PHP solves the issues – but the nasty thing is: it has worked before.
VERY frustrating.
Blog security
I have disabled new login on the blogs and removed the users I I don’t know – mainly on the Trips, Tracks and Travels blog; for this one, I left all users in place – I know them (at least, most of them), but new users cannot be created.
I doublechecked protection of the directories to be READONLY – and they are.
It is intended to make abuse a little harder.
I cannot upgrade to a higher version until my problems with WP 2.8.x are solved: There is a redirection by the PHP code that causes a loop, which is signalled by Firefox (IE8 runs into a timeout). That’s why the BC2007b log is disabled, I used that for testing. I’ll look into 2.8.4 to see if the problem persists – but my feeling is it will still be there and so I won’t be able to upgrade. I’m not the only one experiencing these problems, but none of the solutions on the WP forum has helped me.