Litespeed Error Log:[ERROR] Swapping directory is not writable:/tmp/lshttpd/swap/

I booted up a server yesterday that I had not used in quite a long time and had some issues right from the beginning. I remembered the server working the last time it was live so I was assuming I could boot it up and test something on the ruby application that was installed on it. Anyhow when I attempted to connect to the web server, which is Litespeed, via a browser it would simply hang. Below is information regarding what I did to troubleshoot, what the error was, and how the error was corrected.

Troubleshoot Connection To Litespeed Web Server Hanging:

I started troubleshooting with some very basic items such as verifying the web server or Litespeed was running, making sure that the ports the web server runs on were open, and attempting to connect to the Litespeed Admin Console. Below are quick notes and results from that troubleshooting.

Verify Litespeed Web Server Is Running On CentOS Linux Server:

Verify Litespeed Ports Are Open On CentOS Linux Server:

As you can see above the Litespeed process (lshttpd) was running and the proper ports were open. The web server itself runs on port 80 and the admin console runs on port 7080 by default. I was unable to connect to any web pages as well as unable to connect to the Litespeed admin console on port 7080.

Investigate Litespeed Issue In LSWS Error Logs:

After the initial troubleshooting I took a look into the Litespeed logs which is what led me to the issue on the server. The below snips from the error logs displays point us in the right direction.

Litespeed Web Server swap Directory Error:

So next I looked into the /tmp/lshttpd directory to see if there was a permissions problem with the swap sub directory and noticed that the swap folder did not exist at all. After looking on another server that is configured exactly the same I saw that the swap folder should be created and have permissions of 700 belonging to the same user that Litespeed runs with. I created the folder with the proper permissions, restarted Litespeed, and was able to now connect to the Admin Console. Something still was incorrect so I looked back into the Litespeed error logs and now noticed the below errors.

Litespeed Web Server Real Time Report Generation Error:

Before creating the .rtreport file, which is required for the Litespeed real time reports, in the /tmp/lshttpd directory I looked further into what could be the issue with the server itself. It was definitely more than a coincidence that there were two similar Litespeed issues with files in the /tmp directory. Using “df” I was able to quickly determine that the primary disk on the server was full thus causing issues with the generation of temporary Litespeed files which caused the initial connection issue.

Verify Disk Space Available On CentOS Server:

I was able to easily clear out some log files that filled up right before this development server was taken offline a couple of months ago. Once I created space on the drive I was able to start Litespeed and connect to both port 80 and port 7080 without any issues.