Server errors
Sometimes it seems impossible to acess the blogs, and the WATCH output shows 500 errors – with no particular text. The server log however does.
Fairly often there is:
%HTTPD-W-NOTICED, 22-JUL-2015 08:21:54, CGI:1997, not a strict CGI response
-NOTICED-I-SERVICE, http://www.grootersnet.nl:80
-NOTICED-I-CLIENT, 68.180.229.122
-NOTICED-I-URI, GET (20 bytes) /sysblog/?m=20110727
-NOTICED-I-SCRIPT, /sysblog/index.php sysblog:[000000]index.php (phpwasd:) SYSBLOG:[000000]index.php
-NOTICED-I-CGI, 504850205761726E696E673A20204D6F64756C652027646F (2048 bytes) PHP Warning: Module 'dom' already loaded in Unknown on line 0.
-NOTICED-I-RXTX, err:0/0 raw:196/0 net:196/0
and once in a while:
%HTTPD-W-NOTICED, 15-JUL-2015 00:12:17, CGI:2107, not a strict CGI response
-NOTICED-I-SERVICE, http://www.grootersnet.nl:80
-NOTICED-I-CLIENT, 89.248.167.137
-NOTICED-I-URI, POST (19 bytes) /sysblog/xmlrpc.php
-NOTICED-I-SCRIPT, /sysblog/xmlrpc.php sysblog:[000000]xmlrpc.php (phpwasd:) SYSBLOG:[000000]xmlrpc.php
-NOTICED-I-CGI, 2553595354454D2D462D53544B4F56462C20737461636B20 (66 bytes) %SYSTEM-F-STKOVF, stack overflow, PC=FFFFFFFF8083B42C, PS=0000001B
-NOTICED-I-RXTX, err:0/0 raw:462/0 net:462/0
%HTTPD-W-NOTICED, 22-JUL-2015 08:51:37, CGI:2107, not a strict CGI response
-NOTICED-I-SERVICE, http://www.grootersnet.nl:80
-NOTICED-I-CLIENT, 192.3.154.170
-NOTICED-I-URI, POST (19 bytes) /sysblog/xmlrpc.php
-NOTICED-I-SCRIPT, /sysblog/xmlrpc.php sysblog:[000000]xmlrpc.php (phpwasd:) SYSBLOG:[000000]xmlrpc.php
-NOTICED-I-CGI, 2553595354454D2D462D41434356494F2C20616363657373 (118 bytes) %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=000000003B22676E, PC=FFFFFFFF8083B42C, PS=0000001B
that occurs in different places within the PHP engine.
I restarted the server and for now, the blogs can be accessed again.
The problems have been signaled but I didn’t get an answer yet. Stack overflow and Access violations may be related to the lack of memory – which is to be handled shortly.
Update
On posting an update, I got a complete stackdump on screen (without formatting, of course). This may help[ to solve the issue:
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=000000002D70772F, PC=00000000003F6870, PS=0000001B%TRACE-F-TRACEBACK, symbolic stack dump follows image module routine line rel PC abs PC PHPSHR 0 00000000003A4870 00000000003F6870 PHPSHR 0 00000000003A9E74 00000000003FBE74 PHPSHR 0 00000000003E3894 0000000000435894 PHPSHR 0 00000000003A43B8 00000000003F63B8 PHPSHR 0 00000000003B58A4 00000000004078A4 PHPSHR 0 0000000000370B8C 00000000003C2B8C PHP52-13WASD PHPWASD ProcessRequest 47240 00000000000020F8 00000000000320F8 PHP52-13WASD PHPWASD main 46824 0000000000000728 0000000000030728 PHP52-13WASD PHPWASD __main 46717 000000000000006C 000000000003006C PTHREAD$RTL 0 0000000000057718 FFFFFFFF80A77718 PTHREAD$RTL 0 0000000000030444 FFFFFFFF80A50444 0 FFFFFFFF8037FC44 FFFFFFFF8037FC44%TRACE-I-END, end of TRACE stack dumpPHP Warning: Module 'dom' already loaded in Unknown on line 0 PHP Warning: Module 'session' already loaded in Unknown on line 0 PHP Warning: Module 'SimpleXML' already loaded in Unknown on line 0 PHP Warning: require(/sysblog/000000/wp-includes/author-template.php) [function.require]: failed to open stream: not enough core in /sysblog/000000/wp-settings.php on line 126 PHP Fatal error: require() [function.require]: Failed opening required '/sysblog/000000/wp-includes/author-template.php' (include_path='.:/php_root/000000') in /sysblog/000000/wp-settings.php on line 126 PHP Fatal error: Maximum execution time of 60 seconds exceeded in Unknown on line 0 PHP Fatal error: Cannot redeclare redirect_post() (previously declared in ðÅCblog/wp-admin/SYSBLOG:[WP-ADMIN]post.php:41) in /sysblog/wp-admin/SYSBLOG:[WP-ADMIN]post.php on line 83
Update 2
Didn’t want to wait. The 2Gb memory has arrived and I decided to install it right away.
$ sho mem
System Memory Resources on 22-JUL-2015 20:20:41.50
Physical Memory Usage (pages): Total Free In Use Modified
Main Memory (2.00GB) 262144 168149 87963 6032
Far better figures than before!
All in all it took less than half an hour. After restart, it became clear that the startup needed to be adapted as well, wasn’t done yet, so it took several more minutes to get it all up and running again. There were a few issues, mainly logicals that needed to be redefined. But once that was done, all went well.
It seems to be quite an improvement: the blogs loads faster (once the runtime environment is loaded and initialized) and since there is much more memory, my guess is that paging – especially hard faults – will be less. But that will show within a few days.
To get things even better, the system has to run for some time after which I could do an autogen to re-configure the system – memory in particular.
Time will also tell whether ACCVIO’s and stack overflows are now a thing of the past.