It is possible to receive an error after updating wpscan via “svn up” complaining about the nokogiri gem. This might be confusing because likely you already have the nokogiri gem installed on Backtrack Linux however it is likely a simple path issue. To resolve you can issue the below gem install –user-install command as shown in the below example.
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.
Earlier this afternoon I was working on a development server that has a web server, a PostgreSQL database, Ruby, and rubygems installed on it. I was curious to find out if a specific gem I was about to install had any dependencies or other gems that would also be installed as dependents of the gem I wanted to test. Below I describe how to find out the dependencies of a specific gem by querying the remote server but also how to download a specific gem version to see what gems are dependents.
I ran into a error when installing the first gem on a CentOS development server I was creating. The error states that the extconf.rb file could not the header files. Below I show the output of the error along with what was done to resolve the error.
I recently setup a new server with Ruby and Rubygems however I received an error when attempting to install my first gem which happened to be ruby-lsapi. Below I explain the error including an example of the error in the output of installing a gem as well as what was done to resolve the error.