Issue

Sometimes there is a need to restart the ZENDPHP7 (or ZENDSVR6 for versions 6 - 8.5.x) Apache instance on the IBM i.  This article tells how to do it from the 5250 command line.  Doing it this way also provides the opportunity to look into the subsystem and verify that the jobs stop and start as intended.

Environment

Zend Server running on any supported version of IBM i.

Resolution

Versions 9.1.x and higher

From the 5250 command line:

GO ZENDPHP7/ZSVMENU

Use option "11. Stop Apache server instances" 

Use option "3. Work with Zend Server subsystems".  Key "2", and press Enter.  Verify that there are no jobs named "ZENDPHP7" active in this subsystem.  If any are there, use F5 a few times until all of them are gone.  If they will not end within a reasonable time, say 5 minutes or more, please end the jobs using option 4, option(*immed). 

ZENDPHP7 jobs that will not end may be of interest

If any of the ZENDPHP7 jobs stubbornly persist, these jobs will be of interest. First make a note of the status for the jobs, which you can do with a screen shot. Then, use option 5 to display a job, then option 10 on the Work with Job menu to display the joblog. Use F10 to show all messages and F18 to navigate to the bottom. You will often see the job is connected to a QSQSRVR job, and you can display that job to see if it is failed or if it is still running. This can be an important clue as to why your web site may be unresponsive.


When there are no more ZENDPHP7 jobs in the QHTTPSVR subsystem, use F3 to return to the menu.

Use option "5. Start Apache server instances".

Once again, use option "3. Work with Zend Server subsystems".  Key "2", and press Enter.  Verify that there are at least 16 jobs named "ZENDPHP7" active in this subsystem.  If they do not appear right away, use F5 a few times until they are all there. 

Note: If FastCGI has been modified from the default of 10 child processes, there should be 6 plus the number of child process jobs.

If FastCGI has been modified from the default of 10 child processes, there should be 6 plus the number of child process jobs.

Versions 6 - 8.5.x

From the 5250 command line:

GO ZENDSVR6/ZSVMENU

Use option "6. Stop Apache server instances"

Use option "3. Work with Zend Server subsystems". Key "2", and press Enter.  Verify that there are no jobs named "ZENDSVR6" active in this subsystem.  If any are there, use F5 a few times until all of them are gone.  If they will not end within a reasonable time, say 5 minutes or more, please end the jobs using option 4, optiion(*immed). 

ZENDSVR6 jobs that will not end may be of interest

If any of the ZENDSVR6 jobs stubbornly persist, these jobs will be of interest. First make a note of the status for the jobs, which you can do with a screen shot. Then, use option 5 to display a job, then option 10 on the Work with Job menu to display the joblog. Use F10 to show all messages and F18 to navigate to the bottom. You will often see the job is connected to a QSQSRVR job, and you can display that job to see if it is failed or if it is still running. This can be an important clue as to why your web site may be unresponsive.

When there are no more ZENDSVR6 jobs in the QHTTPSVR subsystem, use F3 to return to the menu.

Use option "5. Start Apache server instances".

Once again, use option "3. Work with Zend Server subsystems".  Key "2", and press Enter.  Verify that there are at least 16 jobs named "ZENDSVR6" active in this subsystem.  If they do not appear right away, use F5 a few times until they are all there.  Note: If FastCGI has been modified from the default of 10 child processes, there should be 6 plus the number of child process jobs.

Note: If FastCGI has been modified from the default of 10 child processes, there should be 6 plus the number of child process jobs.

If FastCGI has been modified from the default of 10 child processes, there should be 6 plus the number of child process jobs.