Christian’s blog

As virtualization seems to be a trendy thing to do, I went ahead and virtualized our nagios (while reinstalling the whole thing …).

Now as I went into work today and started my email client, I received 4 nagios warnings about a LOAD service reaching critical state. Looked at the nagios box itself, opened up the VM console, looked into the syslog. Nothing.

Yet over 3/4 of the services were flapping, some ping checks were critical (for whatever reason). So I opened the nagios webinterface again, and noticed it dropping the connection over and over again (had to reauthentificate me again and again).

So I opened up Putty, which established the connection without a single problem, but dropped me like a stone after a short amount of time. I restarted the session and got a security warning from Putty (due to different than the saved sshd public key). That raised my suspicion. So I took a look at the hostname, and lookie there.

Somehow my old nagios box (which is a physical box), got turned online again, thus having the same IP address as my virtualized one. So the virtualized nagios wasn’t really dropping my connection, but I was being directed to the old nagios.

Walked over into the data center, turned of the old box (well, I kept the power button pressed for a short time), and away went my troubles.

Life Nagios

Well, as some people know, I keep around a small set of packages for my own needs (stuff I need from time to time, packages currently in the distributions but yet too old).

So here are some additions to my small repo (that is so far this month):

• iftop 0.17-7 for SLES10 (i586, x86_64, SRPM) — Rebuild from Fedora’s SRPM
• nagios-nrpe 2.12-1 for SLES10 (i586, x86_64, SRPM) — Rebuild/Bump from my previous SRPM
• nagios 3.0.3-1 for SLES10 — Rebuild/Bump from the original SLES10 SRPM
  • nagios 3.0.3-1 (i586, x86_64, SRPM)
  • nagios-www 3.0.3-1 (i586, x86_64)

Disclaimer: I don’t take any responsibility for faults within the software, I just provide the RPM’s! Feel free to ask me about stuff concerning these RPM’s, but I ain’t accountable if your stuff goes kaboom …

Life RPM, SLES10

Remember my last post about cpu masking ? Well, turns out that you can do it to a “template”.

The only point you don’t need to do, is to mark the VM as a “template“. You still can clone it and move it around and all that other stuff, but the good part is, that the cloned VM keeps the cpu mask set to the “template” *shrug*

I don’t know, why VMware didn’t include that feature into the templates, since it’s a real freaky way to do.

Life VMotion, VMware Infrastructure