I was contacted by a client last week regarding a monitoring server they have deployed. One of the applications they have gathering data from this server is Cacti. Anyhow they were able to login to Cacti but the graphs were not displaying. After logging into the server, which is running CentOS Linux, I saw the error clearly in the Litespeed logs. Below I describe the error in more detail as well as how to resolve this problem if you run into it.
LiteSpeed: [STDERR] /usr/lib/ruby/site_ruby/1.8/ rubygems/custom_require.rb:31:in `gem_original_require’: no such file to load — lsapi (MissingSourceFile)
After restarting LiteSpeed on a server used to develop various Ruby applications there was an error in the LSWS logs. It should be pointed out that the below error was received after straightening out a Ruby installation problem that the server had. The issue was two versions of Ruby were installed with one being installed via source and the other being installed via the Yum Package Manager on this CentOS server. Once the Ruby installation issue was resolved I thought that Rubygems and all of the proper gems had been installed though that was not the case as explained in the below resolution.
Once I finally made it past the PHP build process the Litespeed Admin Console Detailed Log complained of not being able to find autoconf. This one is fairly obvious but wanted to note just in case someone is not familiar with the autoconf package. Again since this is a new server with a minimal install the autoconf package had not been installed. Below are details about the error from the Litespeed Detailed Log and how to install autoconf via yum.
Another error I ran into while attempting to build PHP via the Litespeed Admin Console. This error directly related to the MySQL libraries or the MySQL version. Below is more information on the error itself and how the error was resolved. This error was resolved by simply installing a couple MySQL packages via the yum package manager as shown below.
This is the second of three or four issues I ran into while building PHP via the Litespeed Admin Console. Each of the errors was caused by missing packages on a new development server I was bringing online. Below I describe the error in more detail, the cause of the error, and how the error can be corrected.