While working on a server farm for a client I kept running into some issues with one of the servers. The issue appeared to be a single CentOS Linux server in a cluster of ten CentOS Linux servers configured exactly the same as the other nine CentOS Linux servers was having issues writing to a network storage device. Initially I figured that the CentOS Linux server having the issues had some permission issues with the directory that was mounted to the SAN (Storage Area Network) however after minimal troubleshooting it was verified that the permissions were identical to the other servers. I started looking through other logs on the server having the issue and located some SELinux errors that were noticeably related to the issue at hand. Below I describe where the SELinux error was located, what the specific errors were, and how I was able to resolve the errors on this specific CentOS Linux server.
It had been awhile since I have installed NRPE or Nagios Remote Plugin Executor running through xinetd so once I thought I had everything configured I attempted to restart xinetd but NRPE was not working properly. Below I describe the error in more detail along with how I resolved the issue. In the below example the server was running CentOS Linux.
I had a client over the weekend that had a computer crash which required a new computer to be configured and old data imported. The old computer was Windows XP and the new computer was Windows 7 so one of the things to import was Outlook Express email into the new Windows 7 Windows Live Mail. The directions below will assist in importing the Outlook Express .DBX files into Windows Live Mail.
A company I work with uses Gmail to log exception emails from our Ruby on Rails application. This allows us to always capture issues with the application and keep a lengthy history of all the issues without using up disk space on the server itself. Sometimes if there is an issues on a development server that is not fixed right away we may get thousands of emails into the Gmail account that are all the same and it benefits us to clear these out from time to time since they can number over 50,000 at times. The example image below shows our Ruby on Rails application exception inbox from Gmail.
With Trillian you may from time to time get connection admin messages that describe some sort of problem. At times these error messages or warning messages will pop up when Trillian starts and you may be in a hurry to just close them out so you can get on with working. The problem with this is that if the issue needs to be resolved you may not know how to retrieve these messages. One such error could be similar to my last post that described an error with the Yahoo Messenger plugin so in this case the error message came from the Yahoo Admin.