Site getting very slow to browse

Support and Discussion Web Server
,
1

Hi,
One of my site getting really slow and only way to make it return to normal is by deleting and restoring from backups and my server give me this log:

2024-08-13 21:57:01.634385 [INFO] [184988] [lsphp]: locked pid file [/tmp/lshttpd/lsphp.sock.pid].
2024-08-13 21:57:01.634389 [INFO] [184988] [lsphp] remove unix socket for detached process: /tmp/lshttpd/lsphp.sock
2024-08-13 21:57:01.634455 [NOTICE] [184988] [LocalWorker::workerExec] Config[lsphp]: suExec uid 65534 gid 65534 cmd /usr/local/lsws/lsphp74/bin/lsphp, final uid 65534 gid 65534, flags: 0.
2024-08-13 21:57:01.648954 [NOTICE] [184988] [lsphp] add child process pid: 184993
2024-08-13 21:57:01.649380 [INFO] [184988] [lsphp]: unlocked pid file [/tmp/lshttpd/lsphp.sock.pid].
2024-08-13 21:57:01.649463 [INFO] [184988] [vmico8535.655340]: locked pid file [/tmp/lshttpd/vmico8535.sock.pid].
2024-08-13 21:57:01.649468 [INFO] [184988] [vmico8535.655340] remove unix socket for detached process: /tmp/lshttpd/vmico8535.sock
2024-08-13 21:57:01.649539 [NOTICE] [184988] [LocalWorker::workerExec] VHost:vmi1790496.contaboserver.net suExec check uid 65534 gid 65534 setuidmode 0.
2024-08-13 21:57:01.649546 [NOTICE] [184988] [LocalWorker::workerExec] Config[vmico8535.655340]: suExec uid 1004 gid 1004 cmd /usr/local/lsws/lsphp80/bin/lsphp, final uid 1004 gid 1004, flags: 0.
2024-08-13 21:57:01.668382 [NOTICE] [184988] [vmico8535.655340] add child process pid: 184994
2024-08-13 21:57:01.668775 [INFO] [184988] [vmico8535.655340]: unlocked pid file [/tmp/lshttpd/vmico8535.sock.pid].
2024-08-13 21:57:01.668819 [NOTICE] [184988] Setup swapping space…
2024-08-13 21:57:01.668911 [NOTICE] [184988] LiteSpeed/1.7.19 Open starts successfully!
2024-08-13 21:57:01.668971 [NOTICE] [184734] New litespeed process is ready, stops listeners
2024-08-13 21:57:01.668981 [INFO] [184734] Stop all listeners.
2024-08-13 21:57:01.668986 [NOTICE] [184734] Stop listener *:80, fd 8.
2024-08-13 21:57:01.668994 [NOTICE] [184734] Stop listener *:443, fd 12.
2024-08-13 21:57:01.668998 [NOTICE] [184734] Stop listener [::]:443, fd 23.
2024-08-13 21:57:01.669003 [NOTICE] [184734] Stop listener *:7080, fd 31.
2024-08-13 21:57:01.669014 [NOTICE] [184734] Event-loop lingering done.
2024-08-13 21:57:01.669016 [NOTICE] [184734] Shut down successfully!
2024-08-13 21:57:01.669022 [NOTICE] [184734] HttpServerImpl::releaseAll called.
2024-08-13 21:57:01.670889 [NOTICE] [184736] New litespeed process is ready, stops listeners
2024-08-13 21:57:01.670911 [INFO] [184736] Stop all listeners.
2024-08-13 21:57:01.670916 [NOTICE] [184736] Stop listener *:80, fd 10.
2024-08-13 21:57:01.670924 [NOTICE] [184736] Stop listener *:443, fd 14.
2024-08-13 21:57:01.670929 [NOTICE] [184736] Stop listener [::]:443, fd 25.
2024-08-13 21:57:01.670939 [NOTICE] [184736] Event-loop lingering done.
2024-08-13 21:57:01.670942 [NOTICE] [184736] Shut down successfully!
2024-08-13 21:57:01.670948 [NOTICE] [184736] HttpServerImpl::releaseAll called.
2024-08-13 21:57:01.672271 [NOTICE] [184732] [AutoRestarter] cleanup children processes and unix sockets belong to process 184734 !
2024-08-13 21:57:01.673198 [NOTICE] [184735] New litespeed process is ready, stops listeners
2024-08-13 21:57:01.673214 [INFO] [184735] Stop all listeners.
2024-08-13 21:57:01.673219 [NOTICE] [184735] Stop listener *:80, fd 9.
2024-08-13 21:57:01.673228 [NOTICE] [184735] Stop listener *:443, fd 13.
2024-08-13 21:57:01.673232 [NOTICE] [184735] Stop listener [::]:443, fd 24.
2024-08-13 21:57:01.673247 [NOTICE] [184735] Event-loop lingering done.
2024-08-13 21:57:01.673262 [NOTICE] [184735] Shut down successfully!
2024-08-13 21:57:01.673268 [NOTICE] [184735] HttpServerImpl::releaseAll called.
2024-08-13 21:57:01.675632 [NOTICE] [184732] [AutoRestarter] child process with pid=184734 exited with status=0!
2024-08-13 21:57:01.675678 [NOTICE] [184732] [AutoRestarter] cleanup children processes and unix sockets belong to process 184735 !
2024-08-13 21:57:01.676725 [NOTICE] [184732] [AutoRestarter] child process with pid=184735 exited with status=0!
2024-08-13 21:57:01.676760 [NOTICE] [184732] [AutoRestarter] cleanup children processes and unix sockets belong to process 184736 !
2024-08-13 21:57:01.777063 [NOTICE] [184732] [AutoRestarter] child process with pid=184736 exited with status=0!
2024-08-13 21:57:23.674110 [NOTICE] [184737] Event-loop lingering done.
2024-08-13 21:57:23.674148 [NOTICE] [184737] Shut down successfully!
2024-08-13 21:57:23.674156 [NOTICE] [184737] HttpServerImpl::releaseAll called.
2024-08-13 21:57:23.677101 [NOTICE] [184732] [AutoRestarter] cleanup children processes and unix sockets belong to process 184737 !
2024-08-13 21:57:23.784430 [NOTICE] [184732] [AutoRestarter] child process with pid=184737 exited with status=0!
2024-08-13 21:57:23.784550 [NOTICE] [184732] Server Stopped!

does any one know any solution
Thanks

2

adding when i disable lite speed cache every thing return to normal

3

This happens with me on a regular.
Check memcached to see if it’s running.

service lsmcd status

If it’s stopped, then start it.

service lsmcd start

If it’s wordpress, then go to https://yourwebsite.com/wp-admin/admin.php?page=litespeed-cache#object and make sure that The extension and the connection is “Passed” in green text.
image

If it’s not passed, then run the following to fix the issue.

service lsmcd stop
mkdir /dev/shm/lsmcd.bak 2>>/dev/null
mv -f /dev/shm/lsmcd/* /dev/shm/lsmcd.bak
service lsmcd start

You can remove the backup if it’s not needed.

rm -rf /dev/shm/lsmcd.bak

You site should be back to normal.
A temporary quick fix if you don’t have access to SSH right away to fix the issue is to just disable object cache from litespeed cache backend.

1 Like
4

@sajetek_developer
Thanks you so much sir