Month: August 2015

It helped
Not just restarting the server.
I still had the maximum execution time for the PHP scripts set to 10 minutes, I used that to upgrade this blog when still on 512 Mb. Now I’m at 1.5 Gb, I upgraded the Tracks blog as well, using the same setting; but that database is significantly smaller than this one, so it finished well within this timespan. But I forgot to reset this parameter.
So that has been reset as well.
This may, or may not have contributed to the low performance, but there were quite a lot of worker processes that ran PHPWASD: (which is the 5.2.13 version of PHPWASD.EXE) within a far higher memory demand than I’ve seen before, it is possible.

Anyway, though not lightning fast, it is better than yesterday.

I’ve seen on the Wordprsss site that there is a program (plugin?) that creates static pages from posts; it comes with Apache’s MOD-REWRITE settings, It may be useful, so I’ll give it a try. The challenge will be to translate MOD-REWRITE to mapping in WASD :).

Load settles
The load seems to settle a bit; I ran into 100% memory yesterday evening, and there wasn’t much movenemnt during today:

It doesn’t mean all is well. SYSBLOG takes ages to load, if it all succeeds! There are quite few WASD worker proce3ssed in the system and many are referred to by the system itself. I’ll have to restart the Webserver, I think…

Same PHP warnings since startup
Six times, since startup. All in admin – some in dashboard, some in admin-ajax.php:

%HTTPD-W-NOTICED, 18-AUG-2015 15:12:54, CGI:2107, not a strict CGI response
-NOTICED-I-SERVICE, http://www.grootersnet.nl:80
...
-NOTICED-I-CGI, 504850205761726E696E673A20204D6F64756C652027646F (288 bytes) PHP Warning: Module 'dom' already loaded in Unknown on line 0.
-NOTICED-I-RXTX, err:0/0 raw:1094/0 net:1094/0


(No Stack overflow, no ACCVIO – because memory is sufficient.)

No idea where this comes from, the weird thing seems ” Unknown” on line 0. So it comes ‘out of the blue’. It’s just a warning, but still: it shouldn’t occur…

For the rest: All is well.

Update ahead
Downloaded WP 4.2.4 yesterday, in preparation to stay up-to-date. Just found out that 4.3 is out; so downloaded that one as well, to be installed ASAP. So there will be a short interruption, likely tonight.

Results from last maintenance job
The results of the last maintenance job were not exactly lost; Info-Zip creates a temporary file and will move it to the destination (by COPY the file and DELETE it afterwards). These temporary files still exist, since COPY didn’t work since the destination files was not available), DELETE didn’t execute. I located these files and examined them, found they were complete, so I renamed them; they still need to be moved to the archives – another maintenance job to do tonight 🙂
Funny
It is not the fastest or easiest way to add or edit content, but WordPress for Android does work, even on a site you handle yourself. This update proves it 😀

UPDATED
Just updated WordPress to version 4.3, and Akismet to 3.1.3. So I’m up-to-date – for this blog. Trips, Tracks and Travels is done as well, I only have to find a good theme.
This means a lot of old stuff can now be removed from disk.

Also added RSS (using rrs2 (standard available in WP) to both blogs.

Stable – up to now
It looks fine up to nowL the system has been up and running continuously for 48 hours, without a glitch. The ususal peak on Monday just after midnight (processing last week’s logfiles) didn’t trouble it, nor does the occasional higher dem,and on resources – it seems that the last two days, the system has been quite busy between 14:30 and 16:30, acccording paaks in HyperSpy output:

The peaks also show up in the WASD graph over the last 72 hours (starting when the system was booted – the part before holds no data, of course):

Next is to contact the supplier for a replacement DIMM, for the one that seems to be bad.

Hung – again
Two things were wrong this morning: To begin, I couldn’t connect to Wifi. It was switched off – my mistake yesterday: attempting to re-connect a Wifi-connected printer using WPS, I switched it off, apparently. Once that was settled, I could authenticate but it was impossible to get an IP address.
Which in my case means that the server was – again – not responding. Not crashed, since that would cause an auto-restart which would enable DHCP as well, within 5-10 minutes.
And sure enough: no response on ^P nor the HALT button – meaning I had to stop the machine the hard way.
I exchanged one of the DIMMS and restarted – and the system has run ever since. At least, longer that yesterday, since HyperSpy shows the system has been running for just a few hours:

and silently stopped working – for some reason – just after 19:00: The Errorlog doesn’t show ANYTHING after the last volume change,
but the last control-entry.
However, startup does show , yesterday as well, and probably more often on startup, but for that I’ll need to retrace these moments.

These problems occur when I install extra memory, 512 Mb for each DIMM in bank 1; with the original 512Mb (2 x 256 in bank 0) there is nothing wrong. But since the system has run now for 12 hours without a glitch and both HALT and ^P both work and SRM’s show mem doesn’t show any bad pages so far, it seems I found the bad DIMM.
Hopefully.
Anyway, I’m now running on three times the memory I had originally.

Although there are still a few questions to be answered. The console manual I have differs from what I see on screen and what I can specify as parameters. But that will most likely be related to the firmware version (7.2-1) and system spec; the manual seems to be related to either the EV6@466Mhz and EV67&600Mhz, where Diana is EV67&617Mhz. Which may explain the differences in DIP-switch settings…