/scripts/restartsrv_httpd
Yes httpd restarted successfully within 2/3 seconds via SSH but WHM take more then 4/5 min minutes to show me httpd restarted successfully.Is it faster to restart via CLI?
tail -20 /usr/local/cpanel/logs/safeapacherestart_log
Can you show me what the following command outputs?
[root@sa ~]# tail -20 /usr/local/cpanel/logs/safeapacherestart_log
[2018-04-18 01:42:21 +0200] info [safeapacherestart] Forced restart elapsed seconds: 1
[2018-04-18 01:42:52 +0200] info [safeapacherestart] Forced restart elapsed seconds: 1
[2018-04-18 06:33:19 +0600] info [safeapacherestart] Forced restart elapsed seconds: 9
[2018-04-18 06:35:56 +0600] info [safeapacherestart] Forced restart elapsed seconds: 14
[2018-04-20 18:11:16 +0600] info [safeapacherestart] Forced restart elapsed seconds: 14
[2018-04-20 18:24:38 +0600] info [safeapacherestart] Forced restart elapsed seconds: 18
[2018-04-25 13:44:28 +0600] info [safeapacherestart] Forced restart elapsed seconds: 105
[root@sa ~]#
I am using apache CentOS7.Can you also tell me the webserver you're running (apache, litespeed, nginx, etc) and your OS (CloudLinux7, CentOS7, etc.)?
I am using v70.0.27Hi @Nirjonadda
What version of cPanel are you using? This sounds similar to an internal case CPANEL-18326 but that not only seemed to be only occurring on litespeed servers but it should have been fixed in v60.0.29 of cPanel
If you're running that version can you go ahead and open a ticket so we can take a closer look, the last line of 105 seconds is definitely a long time to restart apache.
Thank you,
Hi
In that case I don't believe it to be the same issue, but I would like for you to open a ticket so we can investigate further. Please post the ticket ID here once the ticket is opened so we can update this thread with the outcome.
Thank you,