litespeed service keeps going to 100% CPU usage

C

czeddie

Member
#1
#1
lsphp service seems fine, but the litespeed service gets stuck at 100% CPU usage at least once a week or so.
If I restart services then it goes back to normal and stays normal a few days.

I'm unsure of commands needed to gather logs or get other info ya'll may need to help me with.
When I click on "logs" from the menu pictured below, there is nothing there.

CentOS7 is the OS on my server.
I've done yum updates & full reboots several times but issue still happens.

Untitled.jpg
 
C

czeddie

Member
#3
#3
I'm already on 5.4.3.

[root@xxxxxx /]# /usr/local/lsws/bin/lshttpd -v
LiteSpeed/5.4.3 Enterprise
[root@xxxxxx /]#

I'll follow your debugging link.
 
C

czeddie

Member
#5
#5
Ahh, okay. No then, I'm on "1". But it didn't like the second command.

[root@xxxxxx /]# cat /usr/local/lsws/BUILD
1
[root@xxxxxx /]# lsup.sh -f -v 5.4.3
bash: lsup.sh: command not found
 
C

czeddie

Member
#7
#7
Got it upgraded! Thanks!

[root@xxxxxx lsws]# /usr/local/lsws/admin/misc/lsup.sh -f -v 5.4.3
Installed '5.4.3 build 1'
2019-12-30 09:32:28 URL:http://update.litespeedtech.com/ws/latest.php [51/51] -> "/usr/local/lsws/autoupdate/latest" [1]
2019-12-30 09:32:28.822452 [NOTICE] [13468] [AutoUpdate] Checking for new releases...
Query latest build of lsws-5.4.3-ent-x86_64-linux.tar.gz
2019-12-30 09:32:29 URL:http://www.litespeedtech.com/packages/5.0/lsws-5.4.3-ent-x86_64-linux.tar.gz.lastbuild [2/2] -> "/usr/local/lsws/autoupdate/build" [1]
Download Build [3].
/usr/bin/wget -nv -O /usr/local/lsws/autoupdate/lsws-5.4.3-ent-x86_64-linux.tar.gz http://www.litespeedtech.com/packages/5.0/lsws-5.4.3-ent-x86_64-linux.tar.gz.3
2019-12-30 09:32:33 URL:http://www.litespeedtech.com/packages/5.0/lsws-5.4.3-ent-x86_64-linux.tar.gz.3 [24501070/24501070] -> "/usr/local/lsws/autoupdate/lsws-5.4.3-ent-x86_64-linux.tar.gz" [1]
Start to follow STABLE releases.
/usr/local/lsws/admin/misc/update.sh 5.4.3 ent x86_64-linux
2019-12-30 09:32:34.705581 [NOTICE] Memory size is: 3880240KB.
2019-12-30 09:32:34.855739 [NOTICE] [OK] Updated license key has been created at /usr/local/lsws/autoupdate/lsws-5.4.3/license.key.
2019-12-30 09:32:35.183230 [NOTICE] Memory size is: 3880240KB.
groupadd: group 'lsadm' already exists
useradd: user 'lsadm' already exists
[OK] lshttpd.service has been successfully installed!
Restarting LSWS
Redirecting to /bin/systemctl stop lsws.service
Redirecting to /bin/systemctl start lsws.service
Done
[root@xxxxxx lsws]# cat /usr/local/lsws/BUILD
3
 
C

czeddie

Member
#8
#8
mistwang said:
If problem persists, please turn on full debug logging while it is happening.
https://www.litespeedtech.com/suppo...wiki:config:bug-reporting#submit_a_bug_report
Click to expand...
The problem happened again.
But I'm stuck on the first step of enable logging:

Code: 
How to Toggle Debug Logging and Capture Output
Let's give an example in a cPanel EA4 environment. One PHP URL/request works with Apache, but it doesn't work with LSWS. Go to the logs folder:
cd /etc/apache2/logs
There is no apache folder at /etc/.
 
M

mistwang

LiteSpeed Staff
#11
#11
Unfortunately, you did not enable debug logging at all.
You should practice that when error is not happening, so you can do it properly.
 
C

czeddie

Member
#12
#12
Good suggestion. Because the very next step in your directions link is giving me trouble also.

Toggle LiteSpeed server debug log (run once to turn on, run again to turn off):

killall -USR2 litespeed
Click to expand...
Code: 
[root@root lsws]# killall -USR2 litespeed
bash: killall: command not found
Code: 
[root@root/]# find / -name killall
[root@root/]#
 
C

czeddie

Member
#20
#20
Hi, the issue is occurring again.
But this time, pkill -USR2 litespeed is not creating any logs?
I toggled it several times, waiting between each time.
All during this, Litespeed is averaging about 95% CPU.

# cat /usr/local/lsws/BUILD
5

Code: 
2020-02-04 14:04:40.729174 [NOTICE] [1137] SIGUSR2 received, shutdown allowed ...
2020-02-04 14:04:43.000577 [NOTICE] [1137] time is up, server shutdown disabled
2020-02-04 14:09:03.147499 [NOTICE] [1137] [1137] Cmd from child: [extappkill:23571:-3:0]
2020-02-04 14:09:03.149316 [INFO] [1137] [CLEANUP] Send signal: 15 to process: 23571
2020-02-04 14:09:03.149346 [NOTICE] [1137] [1137] Cmd from child: [extappkill:22892:-3:0]
2020-02-04 14:09:03.149362 [INFO] [1137] [CLEANUP] Send signal: 15 to process: 22892
2020-02-04 14:09:07.780544 [NOTICE] [1137] SIGUSR2 received, shutdown allowed ...
2020-02-04 14:09:10.100195 [NOTICE] [1137] time is up, server shutdown disabled
2020-02-04 14:12:43.469930 [NOTICE] [1137] SIGUSR2 received, shutdown allowed ...
2020-02-04 14:12:46.101526 [NOTICE] [1137] time is up, server shutdown disabled
2020-02-04 14:15:48.380047 [NOTICE] [1137] SIGUSR2 received, shutdown allowed ...
2020-02-04 14:15:51.000537 [NOTICE] [1137] time is up, server shutdown disabled
2020-02-04 14:18:25.592475 [NOTICE] [1137] [1137] Cmd from child: [extappkill:23229:-3:0]
2020-02-04 14:18:25.594170 [INFO] [1137] [CLEANUP] Send signal: 15 to process: 23229
2020-02-04 14:32:12.518060 [NOTICE] [1137] SIGUSR2 received, shutdown allowed ...
2020-02-04 14:32:15.005514 [NOTICE] [1137] time is up, server shutdown disabled
 

Attachments

You must log in or register to reply here.
Top