I have been re-testing the i5 toolkit results we had seen and wanted to make sure I had the latest Zend Server version so I ran the upgrade process for the Zend Server (uses the support tool provided on the ZENDSVR/ZSMENU). After the upgrade had completed I came across a problem I had seen posted on the Zend Forums. The problem is the following message is sent from the EASYCOM for PHP server to the QSYSOPR message queue.
EASYCOM for PHP – The PHP Toolkit for IBM i – For Support & Updates
Register at http://www.easycom-aura.com , or contact
info@easycom-aura.com
Unfortunately this message is now sent every time a new user connects to the web pages and sometimes after the same user reconnects. In the post on the Zend Forums the original poster was instructed to restart the Zend and Easycom Server processes which resolved the problem for him. I did this but in doing so came across another issue, the Zend Server would not start up! A quick review of the joblog for the server showed the following message
40 10/14/11 07:16:49.788236 QZSRAPR QHTTPSVR *STMT QZSRCORE
From module . . . . . . . . : QZSRSNDM
From procedure . . . . . . : sendMessageToJobLog_CCSID
Statement . . . . . . . . . : 27
To module . . . . . . . . . : HTTP_CONFI
To procedure . . . . . . . : process_resource_config_nofnmatch
Statement . . . . . . . . . : 53
Message . . . . : Error occurred opening file.
Cause . . . . . : An error occurred when attempting to open file
/www/zendsvr/conf/httpd.conf. As a result, the HTTP server did not start
The error number received was: 3401. Recovery . . . : If the error num
is a value other than 0, determine the meaning of the error number and
perform the appropriate recovery for that error. Correct the errors and
I had not changed the config file and when I looked at the content everything looked the same as it did before? However, when I looked closer I found the owner was QSECOFR not QTMHHTTP. That was strange because I never use the QSECOFR profile except when doing an install that requires it? I am not sure (and as I do not subscribe to the Zend Support I cannot post a ticket to find out) if the update process set the ownership to QSECOFR? However the fix was very easy, I simply changed the owner back to QTMHHTTP which also set the authorities correctly.
The servers then restarted OK, I also restarted the Easycom Server as this could be the source of the problem. Unfortunately it has not resolved the messages issue and I have sent off a request to Aura Equipments to take a look. As soon as I get an answer back I will post the results. if you come across the problem with the Zend Server not starting hopefully the above information will help you get up and running again. Not sure what the fix for the message problem is until I hear back from Aura Equipments.
Chris…
