Minor glitches on startup
There were still a few gltches in accessing the vmswiki, but it was fairly easy so find the cause: A wrong logical diskname for the LD-device holding Python and moinmoin (the wiki software) and a typo in defining moin_static – that I define as a searchlist, so I don’t have to move around with files when installing a new moinmoin version….
After that was settled and repaired, the wiki works like before – a slow starter but once started, pretty fast.
Blogs more responsive
The blogs are more responsive as well, and suffer less partial crashes – so far. More important: I have less trouble logging in into the admin pages. I must have cleaned up quite some things in the attempt of updating and reversing the whole activity.
But now I got the answers on what the heck had happened, I coud give it a try once more. In which case I may decide to upgrade WP as well. That normally is easy, no trouble at all, though I’ll have to prepare a thing or two. But every update went nice and smoothly. But I’ll take Mark’s suggestion: have a look first what changed between 5.2 (supplied by HP and ported by Mark Berryman – which is the current version I’m using curently) and 5.3 (as ported by Mark Berryman). Anyway I’ll have to use the version op PHPWASD that comes with this kit…
27-Mar-2012
Power loss
Shortly after 17:44 local time (the system is set to UTC, no DST, so in nreal time, it’s two hours later) power was llost. The system didn’t restart automaticly since the HSX50 was – once again – too slow. So I had to reboot by hand. By luck, the startup of the web-based stuff didn’t mention the new PHP confuguration so all blogs started as usual.
Speaking the PHP: I got the answers I was looking for. When I use Mark Berryman’s PHP port, I am to use the PHPWASD file he supplies with the kit because Mark Daniel’s PHPWASD kit is not compatible with PHP 5.3, that needs to be called in a different way. Also, some mpdules are built=in where HP delivers them as separate modules.
And I have to do something with PHHP.INI to get the current version of WP running….
So I have to do it again. Perhaps it’s time to upgrade WP as well. meaning I have to do some serious reading. BEFORE the update…
26-Mar-2012
PHP update reversed
It looked right but in short term it turned out the update had severe flaws…As I found out soon after the update, there is big trouble on this update. It comes with a new version of PHPWASD.EXE thnat complains about the NEW function that seems to be deprecated (is it a procedure noewadays?) and a missing module….Building the PHPWASD version 1.4.3 is even more troublesome. It crashed on an Access violation….
WIth some trouble I returned to the previous version…
25-Mar-2012
PHP updated
Taking the big plunge: updated PHP on Diana. Using Mark Berryman’s 5.3 port and WASDPHP 1.4.3, I did an update ‘on the fly’ – fingers crossed. This time, I followed the description to the letter.
You may have noticed.
It’s faster (it seems so anyway) and looks more stable; looking at WordPress anyway. And as the site administartor and maintainer: I got rid of the nasty login-failures.
Does it mean that I can – finally – update WordPress as well? the new setup works on the testbed…But I never tried it with locat MySQL on that box…Well, I’ll have to do the update there as well.
08-Mar-2012
Mail problem solved
Weird: I changed ISP quite a few months ago, and I used their SMTP-server ever since, without a problem – until last weekend:Their server refused relaying…Their suggetsion: use the smtp server at you new ISP. Duh. I could have guessed – but I’ve asked for a postbox, and seems to have never used it…And I had just one receipt for domain registration and DNS; where I would expect more….
That’s administrative, still to be handled, with some other things. But I chnaged the alternate gateway to the current ISP’s server, restarted SMTP and now mail works again.