SOLVED upcp killing alternate web server

[Anoop P Alias]

Please see the log

This should never be happening .Unlike httpd nginx does not need a hard reset and need only graceful reloading of the config file on config changes . so cPanel scripts should never restart nginx process .

A check must be done to detect if an alternate web server is running and only restart the apache process .

##############
[2017-01-06 03:32:52 +0300]      [25259]
[2017-01-06 03:32:52 +0300]   Cleanup    : ea-apr-1.5.2-5.5.1.cpanel.x86_64                         447/450
[2017-01-06 03:32:52 +0300]      [25259]
[2017-01-06 03:32:52 +0300]   Cleanup    : ea-php-cli-0.1.0-2.4.1.cpanel.x86_64                     448/450
[2017-01-06 03:32:52 +0300]      [25259]
[2017-01-06 03:32:52 +0300]   Cleanup    : ea-php-cli-lsphp-0.1.0-2.4.1.cpanel.x86_64               449/450
[2017-01-06 03:32:52 +0300]      [25259]
[2017-01-06 03:32:52 +0300]   Cleanup    : ea-libmcrypt-2.5.8-3.3.2.cpanel.x86_64                   450/450
[2017-01-06 03:32:52 +0300]      [25259] Purging all relevant cached command results
[2017-01-06 03:32:52 +0300]      [25259] Building global cache for cpanel...Done
[2017-01-06 03:32:52 +0300]      [25259] Building global cache for cpanel...Built /etc/apache2/conf/httpd.conf OK
[2017-01-06 03:32:52 +0300]      [25259] Building global cache for cpanel.../usr/sbin/apachectl is already updated.
[2017-01-06 03:32:52 +0300]      [25259] Building global cache for cpanel...Fix mailman RPM directories
[2017-01-06 03:32:52 +0300]      [25259] Building global cache for cpanel...Aligning modsec config to Whostmgr
[2017-01-06 03:32:52 +0300]      [25259] Building global cache for cpanel...Waiting for “httpd” to stop ……Terminating process: nginx with pid 22247 and owner nobody....Done
[2017-01-06 03:32:54 +0300]      [25259] Building global cache for cpanel...Waiting for “httpd” to stop ……Terminating process: nginx with pid 22247 and owner nobody....Done
[2017-01-06 03:32:54 +0300]      [25259] Building global cache for cpanel...Waiting for “httpd” to stop ……Terminating process: nginx with pid 22247 and owner nobody....Done
[2017-01-06 03:32:54 +0300]      [25259] Building global cache for cpanel...Waiting for “httpd” to stop ……Terminating process: nginx with pid 22247 and owner nobody.......waited 1 second(s) for 1 process(es) to terminate....Done
[2017-01-06 03:32:54 +0300]      [25259] Building global cache for cpanel...Waiting for “httpd” to stop ……Terminating process: nginx with pid 22247 and owner nobody....…finished.
[2017-01-06 03:32:54 +0300]      [25259] Building global cache for cpanel...Waiting for “httpd” to stop ……Terminating process: nginx with pid 22247 and owner nobody....g normal operations
###################

Please fix this as this forbids people from running third party web server alternatives which are listed in
cPanel's application catalog too.

 

[Johncar69]

hi,

I agree totally, i opened a ticket with them, and issue does not appear with cpnginx, but Xtendweb yes...

 

[vacancy]

Yes i live with this error.

If cPanel is just running the process as if it is running apache, editing for alternative webserver configurations is a must. Due to this error, access to our 6 servers was interrupted. (Cpanel 11.60 build 28 - build 31 auto update after)

 

[Johncar69]

Response from cPanel:

I have submitted an internal bug report with our developers requesting that we modify the /scripts/restartsrv_httpd script to honor the Apache ports configured to be used and not kill processes listening on the default HTTP ports(80/443) should Apache not be configured to listen on them. The case was assigned the ID CPANEL-10695 which, while our internal bug reports are not able to be viewed by the public, if the change does get made it will be included in the cPanel release notes which you can find at the link provided below.

 

[cPanelMichael]

Hello,

As mentioned, internal case CPANEL-10695 is open to address an issue where the script /scripts/restartsrv_httpd is designed to kill any running process that is actively listening on ports 80 and 443, even when Apache is configured to use non-default ports. This can lead to issues with custom Nginx implementations. I'll update this thread with more information on the status of this case as it becomes available.

Thank you.

 

[cPanelMichael]

Hello,

To update, internal case CPANEL-10695 ensures that cPanel will consider the custom Apache ports configured under the System tab in WHM >> Tweak Settings instead of killing the processes running on the default ports (80/443). This resolution is scheduled for inclusion with cPanel version 64.

Thank you.