We ran into something we've not seen here before.

We run a Nagios master server with Nagios Core 3.3.1.
We have nrpe version 2.12 on the servers being monitored (clients) and use check_nrpe v2.12 from the master to interrogate them.
The version of check_disk on the clients is v1.4.14 (nagios-plugins 1.4.14).

Typically we setup the nrpe.cfg on the clients to monitor each individual disk by its device name e.g.
command[check_opt_app_logs]=/usr/local/nagios/libexec/check_disk...

On receiving an install media today I tried mount it on my RHEL5 system:

mount /dev/hdc /mnt/cdrom

But that errored out:
mount: block device /dev/hdc is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/hdc,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

In /var/log/messages I saw:
Feb 5 14:17:05...

During an issue overnight I attempted to run the latest Dell Dset version 3.5.1 for 64bit on RHEL 6.1. This didn't complete. It just hung.

By doing "ps -ef |grep dset" I was able to see the dset child of the dset bin file I'd kicked off.

By running "lsof -p <pid>" on that child's PID I was able to see it was creating a log for its run in opt/dell/advdiags/dset/report/temp1391539132.89/logs/dset/dset.log (note that the temp# changes on...

Today I was creating a new init script on RHEL6. This isn't something I've had to do often.

I ran into the common problem that although the new script successfully started and stopped the service from command line and also started it on reboot it did NOT stop it before the server went down when the shutdown was done.

The reason for that is because on RHEL they run a killall script that checks for files in /var/lock/subsys and only run the "stop" portion...

On trying to add a new OpenFire instance today it was found that the admin login to the web page for the OpenFire instances and the Spark client logins were failing. (Essentially each instance is a separate install of Openfire on the same server but in different directories - we do this to segregate the chat groups from one another.)

Review of the logs indicate it was still trying to use the original Windows Domain Controller for LDAP/AD user/password lookups that we'd originally...