cPanel starts Apache instead of Litespeed
Hi all,
A few days ago when cPanel did a software update cPanel stopped httpd and restarted httpd Apache, but I am using Litespeed webserver. As a result of this my websites had errors. Together with Litespeed support we found the reason for this issue. Litespeed told me that they will contact cPanel support too.
[root@host logs]# pwd
/usr/local/cpanel/logs
[root@host logs]# grep "26 05:38:" * | grep httpd
grep: packman: Is a directory
grep: error_log:[2020-03-26 05:38:53 +0100]: "/usr/local/cpanel/scripts/restartsrv_httpd --stop" called by (10880 - /usr/local/cpanel/3rdparty/bin/perl /etc/yum/universal-hooks/multi_pkgs/posttrans/ea-__WILDCARD__/500-restartsrv_httpd --pkg_list=/root/tmp/tmp8pAiTc)
php-fpm: Is a directory
error_log:[2020-03-26 05:38:53 +0100]: "/usr/local/cpanel/scripts/restartsrv_httpd " called by (10880 - /usr/local/cpanel/3rdparty/bin/perl /etc/yum/universal-hooks/multi_pkgs/posttrans/ea-__WILDCARD__/500-restartsrv_httpd --pkg_list=/root/tmp/tmp8pAiTc)
grep: update_analysis: Is a directory
[root@host logs]# grep "26 05:39:" * | grep httpd
error_log:[2020-03-26 05:39:09 +0100] info [restartsrv_httpd] All other attempts to stop the service have failed. The system successfully used an internal function to stop the service 'httpd'.
grep: packman: Is a directory
grep: php-fpm: Is a directory
grep: update_analysis: Is a directory
-
Hello, I checked in on the discussion between us and litespeed and because this is not able to be replicated right now we'd like to request that you open a ticket. Can you please open a ticket using the link in my signature? Once open please reply with the Ticket ID here so that we can update this thread with the resolution once the ticket is resolved. Thanks! 0 -
Ticket ID is: 93467103 0 -
Thanks! While the issue is marked as being solved, it looks like some of our Level 3 analysts may be taking a second look at the issue at the behest of Litespeed today. 0 -
Yes, it is marked as solved, but it isn't solved. There are 2 different statements coming from cPanel and LiteSpeed. Both are contrary, so it sounds good that cPanel will take a second look at this issue. 0 -
Hi @serpent_driver Where it stands now from what I understand after thoroughly reading the ticket and discussing this with the L3 Analyst who took a second look at it is that they were unable to replicate the issue no matter what they did. Easyapache Developers indicated that the only way this could have potentially happened was if somehow the restart occurred outside of systemd but even that we couldn't replicate the same behavior on a test server. You noted that this isn't the first time this has occurred in the ticket and you've got some software to notify you if it does happen again. What do these scripts do exactly? Either way, should this occur again, the best and most recommended course of action would be to contact us immediately when it does occur so that we can look at what's occurring. 0 -
Hi @cPanelLauren This script is really simple. I check with PHP which Server Software is running. If it is not LiteSpeed I will be notified and it writes a logfile with time. Really simple! 0 -
Awesome. There seems to be some confusion from both sides on how this happened so it'll be really good to see. 0 -
It doesn't matter for me who is right or wrong, but it matters that this issue will be fixed. But I am wondering why I seem to be the only one?! 0 -
Hi @serpent_driver Exactly! For both points. If it's an issue with either product, you'd think others would be experiencing the issue. 0 -
Current Status: Both sides confirm that there was an event where Apache has been started instead of LiteSpeed, but nobody can reproduce it, so it's on me to monitor it. But I doubt that it can be reproduced if it happens the next time. 0
Please sign in to leave a comment.
Comments
10 comments