Monitoring a ReadyNAS NV+ with Nagios

I use Nagios to monitor my small network, so I wanted to add my ReadyNAS NV+ to the setup and chose to do so with SNMP. The ReadyNAS supports SNMP, but you must enable it in FrontView.

Download READYNAS-MIB.txt and drop it into /usr/share/snmp/mibs/ (or wherever you keep your MIBS).

After enabling SNMP on your NAS, and assigning a community name (e.g. public) to the service, test it. In the following example, I walk down the READYNAS MIB (if you omit the OID, you see all the variables the ReadyNAS makes available):


snmpwalk <del>m ALL -v 2c -c public ip</del>address   .1.3.6.1.4.1.4526
READYNAS-MIB::nasMgrSoftwareVersion.0 = STRING: "4.01c1-p1"
READYNAS-MIB::diskNumber.1 = INTEGER: 1
READYNAS-MIB::diskNumber.2 = INTEGER: 2
READYNAS-MIB::diskNumber.3 = INTEGER: 3
READYNAS-MIB::diskNumber.4 = INTEGER: 4
READYNAS-MIB::diskChannel.1 = INTEGER: 1
READYNAS-MIB::diskChannel.2 = INTEGER: 2
READYNAS-MIB::diskChannel.3 = INTEGER: 3
READYNAS-MIB::diskChannel.4 = INTEGER: 4
READYNAS-MIB::diskModel.1 = STRING: " Seagate ST3500630NS 465 GB"
READYNAS-MIB::diskModel.2 = STRING: " Seagate ST3500630NS 465 GB"
...
...

There are two values I'm mostly interested in: the state of the volume and the NAS' temperature, so I created appropriate services in Nagios, and added a check command to those using the check_snmp plugin. For example, to monitor the device's temperature, I use:


check_snmp <del>H ip -C public -P 2c -o READYNAS</del>MIB::temperatureValue.1
         -w 20:35 -c 15:40

If you run that on your machine's command line, it prints out something similar to this:


SNMP OK - 26 | READYNAS-MIB::temperatureValue.1=26

This check will warn you when the reported temperature is below 20 or above 35, and it will set a critical result for Nagios, when it is below 15 or above 40C.

I recommend you have a look at the other SNMP OIDs the device has to offer: there are lots of goodies there!

Oops…

Burnt-out graphics adapter

The ATI Radeon 9800 in the missus' PC died of heat on the weekend. Not that it was so hot here, but I opened the case, and it appears that the fan on the card got stuck, so the card overheated.

I called Dell support. After discussing the situation with two different people, both with a very strong Polish accent, I asked for a replacement card to be sent to my address.

No problem, said they; it is a replacement, so we send you a new one, and you send us your old one. Sure, and what will that cost? It costs EUR 230.00 plus VAT, postage and packing.

What?

Just as well I checked online while we are talking; the street price of the card is around EUR 40.00. I told the Dell Poles the same, and they said they couldn't do anything about it. Ok, thanks, bye.

This afternoon I'll pick up a replacement. Just phoned and had one put aside. The brand new graphics adapter will cost EUR 45.00 (and I get to keep the old adapter, not that it'll be of any use).

If Dell charged that amount for sending the spare part with a guy who replaces it, I'd understand, but they don't.

That sucks.

My new T-shirt

Thanks for the T-shirt, guys, I really appreciate it:

and it fits. :-) I hope the chapter in my book does your brand new server justice.

How I got started with LaTeX

A comment posted the other day made me consider writing up a bit on how I got started with LaTeX, so here goes.

When the idea of writing a book was born, I dreaded the thought of using a typical word processor to do the job; I've used MS-Word (in umpteen versions except the latest: I refuse to) and OpenOffice.org on larger documents before, and the programs suck. Both programs are good enough to write up a shopping list or an invitation to a booze-up on the weekend but little else. I had a publisher (that's the guy who made me start writing the book), and he recommended I do it in LaTeX. His main arguments being I could use Unix tools to "manage" the creation of the book (grep, sed, etc.), and write it with my favorite text editor. That was the argument that really got me.

I ordered two books: Leslie Lamport's LaTeX: a document preparation system (Lamport invented LaTeX, so that is the reference), and Frank Mittelbach's The LaTeX Companion, 2nd ed (an excellent and very thick book that shows you how to use LaTeX' packages with a trillion examples). There are plenty more books, so take your pick. Oh, and I recently read (and loved) LaTeX Hacks which, to my knowledge, doesn't exist in English. The books took a while to be delivered by the post office, so I started off with some online resources.

There is an incredible amount of good stuff on LaTeX, and here are a few I liked best: start off on the LaTeX project page of course, where they tell you (in just a few words), what LaTeX is all about. This bit is very important to understand: LaTeX is a document preparation system for high-quality typesetting. Read that short page five times, go grab a coffee and read it again, and then go to their documentation page.

WikiPedia's LaTeX article gives a bit more insight and some goodish links. The next bit is: don't get confused by all the maths stuff: many clever people use LaTeX for typesetting mathematic formulae; now, that doesn't interest me in the slightest, but unfortunately a lot of documentation focusses on that (it is after all one of the many powerful facets of TeX, the underlying system in LaTeX). Anyways, just forget about those (unless of course, you are a mathematician and want formulae).

A goodish document is Getting Started with LaTeX, by Wilkins, available as PDF and as LaTeX source (is that cool?). Very good, because it is geared towards how you get started with the tools, is Talbot's LaTeX for complete novices (PDF). WikiBooks has a book on LaTeX (PDF) that is also worth looking at. Cambridge University has a good list of introductions, some as PDF, others as PostScript, most in HTML, so you'll be ok with that. And, last but not least, the FAQ. If you're conversant in the German language, consider listening to a podcast on the use of LaTeX, available for download at Pofacs: it is a bit long-winded, and I didn't like it very much, but you might. A Germany site for LaTeX is Dante where you'll find further links and literature, including a list of books.

So, and then? Well, LaTeX exists for most, if not all, Linux distributions, so there is no problem getting the software. You'll also find it for Windows, Mac OS X and probably for your toaster as well (BTW, Mittelbach's Companion has a CD on it, with a TeX/LaTeX distribution on it, but I didn't further look at that, as I had all I required to start with).

I started with your typical Hello World type document: nice and easy, to get a feel for the tools, the debug output (which sucks) and all the intermediate files LaTeX gives you. The first thing I did was create a small Makefile (you can use a shell script to do the same) which cleaned up all the stuff, just so I could start-over if I wanted to. After getting the hang of things (which takes an hour or two), I sat back and read the books.

And the rest? Well, the rest is history, as they say. I am certainly not proficient in LaTeX, but I fully understand what it can be used for, and let me tell you: you can use it for any writing. The most important to remember is to structure your text and use macros. For everything. The rest is easy.

As soon as I've completed this project, I'll be re-structuring my office. With that will come using LaTeX for all correspondence (yep, you can also write letters with it; packages g-brief, dinbrief, etc), and I'll report on that in due course.

LaTeX is really, really worth looking into.

Scared? I can imagine: I was.

Then why not start off easy? LyX is a document processor with a GUI-frontend to a LaTeX back-end. It runs on Linux and Windows (Win32 and Cygwin), and is probably a good way to start easy, with a bit of GUI support. There is another project known as Kile, an integrated LaTeX environment, which runs on a number of platforms. I've glanced at LyX, and it really looks very good, but I can't say much about either of these programs. If you do try them, or if you have experience with either, I'd be interested in your opinion.

Cheaper than gas

Thanks, Nic.

E-mail signatures working again

EximEarly yesterday, I detected that our outgoing BATV signatures weren't correctly being verified upon being returned to us, and some Exim debugging confirmed that:

13:06:15 15374 prvscheck: received hash is b745ee
13:06:15 15374 prvscheck:      own hash is b745ee
13:06:15 15374 prvscheck: signature expired, $pvrs_result unset

Unfortunately I had to disable BATV until that was fixed.

Tom Kistner quickly found the error, which as I'd supposed was a miscalculation in the date. He writes:

Not your fault. An off-by-one error in the expiry date calculation. This happens every
1000 days only. Next occurence would be early in 2011.

which is great, because I don't have to hurry to apply the patch. ;-)

And without the patch? Today everything works as expected:

07:45:37 32621 prvscheck: received hash is 5f859e
07:45:37 32621 prvscheck:      own hash is 5f859e
07:45:37 32621 prvscheck: success, $pvrs_result set to 1

Now tell me: do you get that kind of support with your multi-million Euro/Dollar enterprise agreement from your wiz-bang company? No. You don't. That kind of support, you get only with Open Source.

Nocens Executor

Wir befassen uns heute mit der Spezies Nocens Executor, besser bekannt als "schlechter CIO".

Mehr>

[danke, Jürgen.]