Earlier this morning while working on a CentOS Linux development server I received errors when doing anything with the yum package manager. I believe the error started after upgrading the kernel on the server from kernel version 2.6.18-164.15.1.el5 to kernel version 2.6.18-194.3.1.el5. After upgrading the kernel yum would output the same error multiple times as shown in the below output example.
I have a couple development servers I have been using for testing PostgreSQL configured with walmgr for log shipping. The secondary server stopped working the other day and I finally got a chance to look into it this morning and attempted to restart Postgres via a terminal but it failed. Below I describe how the error was noticed, what was done to troubleshoot PSQL not starting, and what was done to resolve the problem so PostgreSQL would start without issue.
While working on a clients computer yesterday I needed to send some of the logs from the computer to myself so I could analyze later on my computer. At first I had to install the Exim MTA which I will write an article on in the near future but once installed mail was still not being received. You won’t actually receive an error from the CLI when attempting to use the mail command from the CLI however after investigating the Exim logs located in /var/log/exim/ the below error was observed and resolving the issue was completed using the steps below.
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.