Solution to /tmp/ Mount Filling Up and Breaking Litespeed

[TEKFused]

All,

I'm running cPanel, CloudLinux, and Litespeed. I recently started having an issue where the ~4GB /tmp/ mount would fill up completely, and break Litespeed, and other pieces of my server. These files would be created in the /tmp/lshttpd/ directory, and be named similar to core.52890. These files would also end up in the /usr/share/cagefs-skeleton/ directory, and begin to fill up the rest of my file system - what a disaster.

The solution that Litespeed support gave me was to disable CRIU in the /usr/local/lsws/conf/httpd_config.xml file like this:

<criuEnabled>0</criuEnabled>

If you want to do this through the Litespeed Admin interface, go to Configuration -> Server -> PHP, and then set Enable CRIU to "No."

After that was done, I didn't have any other issues. I hope this will help someone else!

Jacob Hill

 

[Pong]

Thanks for the tips. Just a few things to clarify in case others may be interested:
1. <criuEnabled>0</criuEnabled> , CRIU is commended to be disabled since it has no performance benefit.
2. If there is any core file issue under /tmp/lshttpd/bak_core/core.* when CRIU disabled, you can log a bug report https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:config:bug-reporting