check_3ware-20120204
Woah, 3 (three!) posts in one day... I've put up a new version of my check_3ware script.
And again, no thanks to me but to Simon Deziel and Stas (Станислав) for reporting a bug, sending in a patch, and a feature request. Now check_3ware will not issue a warning when an array is in verifying state.
I didn't test the script since I do not have any 3ware hardware anymore, so get it here and use it at your own risk ;-)
autofwd 0.6-2
Today I've also released a new package of autofwd. It's still the same version, I've only fixed some packaging bugs. You can get it here...
Ow, and you like a new packaged version of libparanoid to go with that? Sure, I've backported that as well (hmz... as far as you can call it a backport...). It's in the same dir as the autofwd package.
Have Fun!
HAProxy 1.5-dev7 snapshot 20120124
Today I've packaged snapshot 1.5-dev7-ss-20120124 of HAProxy for Debian Squeeze (amd64 only). I've been running the 1.5-dev version for quite some time but hit some bugs which are fixed in this version.
It is available at http://www.roedie.nl/downloads/haproxy/20120124/
Note to self
When replacing servers with new ones:
- Upgrade the firmware
- Connect the iLO card
- Let it run for a couple of days before setting it live
BTW, is it just me, or are the new hp dl360 g7 servers a bit buggy. They are giving me memory problems and iLO problems.
check_3ware 20101010
Due to some small bugs in the previous release I've put up a new version. Thanks to Wiebe Cazemier for noticing this since I didn't check well enough.
It's available at: http://www.roedie.nl/downloads/check_3ware/check_3ware-20101010.tar.bz2
check_3ware 20100920
With no thanks to me at all, I've released a new version of check_3ware. This version supports the 'VERIFYING' state and has a minor tweak to the battery testing part.
The code was contributed by Dan Langille so all credits are for him.
You can get it from http://www.roedie.nl/wiki/index.php/Nagios_3ware.
Have fun!
IPv6 en politiek
Zo, dan nu eens wat in het nederlands...
Vandaag is er in de 2e kamer een debat geweest over het gebruik van IPv6. Nu ben ik een groot voorstander van het gebruik van IPv6 (nee ik draai het nog niet) en ben voor mijn werk al druk bezig met de implentatie ervan. Maar, nu schiet het volgende mij toch even in het verkeerde keelgat.
Tijdens het debat werd er door Arda Gerkens (SP) gezegd dat leveranciers verplicht moeten worden om IPv6 te leveren al zij willen leveren aan de overheid. Het plan word gesteund door het CDA en de PVDA. Let nu even op het volgende lijstje:
marvin:~ roedie$ host www.cda.nl
www.cda.nl has address 93.95.113.130
marvin:~ roedie$ host www.sp.nl
www.sp.nl has address 82.94.240.194
marvin:~ roedie$ host www.pvda.nl
www.pvda.nl has address 62.112.225.33
marvin:~ roedie$ host www.pvv.nl
www.pvv.nl has address 195.20.9.130
marvin:~ roedie$ host www.d66.nl
www.d66.nl has address 212.204.201.17
marvin:~ roedie$ host www.groenlinks.nl
www.groenlinks.nl has address 81.23.231.220
marvin:~ roedie$ host www.sgp.nl
www.sgp.nl has address 80.247.220.16
marvin:~ roedie$ host www.christenunie.nl
www.christenunie.nl has address 213.193.247.115
marvin:~ roedie$ host www.partijvoordedieren.nl
www.partijvoordedieren.nl is an alias for partijvoordedieren.nl.
partijvoordedieren.nl has address 81.17.33.17
marvin:~ roedie$ host www.trotsopnederland.nl
www.trotsopnederland.nl is an alias for trotsopnederland.nl.
marvin:~ roedie$ host www.vvd.nl
www.vvd.nl has address 91.184.6.107
Tel even met mij mee hoeveel IPv6 adressen daar tussen zitten.... Neem gerust de tijd....
Dat zijn er dus NUL. Beste mensen die ons land besturen, mag ik jullie er op wijzen dat als jullie deze wet nu invoeren jullie zelf niet eens voldoen aan die wet. Ik ben het er absoluut mee eens dat IPv6 ingevoerd MOET worden, maar zorg er in ieder geval voor dat als je ergens een mening over hebt, of een wet voor bedenkt dat je dan zelf ook hier aan kan voldoen.
Debian/Ubuntu not resolving domains with the .local tld
For some time I've been wondering why none of my Debian/Ubuntu workstations would resolve something like 'proxy.mycompany.local'. Simpy resolving 'proxy' would work.
I already knew that .local is not a correct tld, but since it was recomended by Microsoft to use this when installing Active Directory we used it. I never had any problems with it because most of the time I just use ip addresses when I need to access a server.
Now I installed a proxy server and a new mail relay server so I started using them as proxy.mycompany.local and relay.mycompany.local. The I found out that none of my Debian or Ubuntu workstations would resolve those addresses. At first I blamed the Microsoft DNS server for this. That's the easiest and most logical thing to do ;-). But Windows XP/Vista clients did resolve those addresses. Strange huh?
Then I started wireshark on my client. I did a query for proxy.mycompany.local and then there was.... an MDNS request instead of a normal DNS request?!?
This quickly gave me the conclusion that it was something avahi related because this does all the zeroconf stuff with Debian/Ubuntu. Avahi seems to be configured to pick up any request ending in .local and make MDNS requests for it. This must be a problem for more people because there must be loads of Microsoft networks out there ending in .local. I won't say this is a fault from the avahi guys because it's also completely wrong to use .local as tld.
My current solution is to just simply disable Avahi on my workstations. On Ubuntu I just do 'System -> Administration -> Services' and disable 'Multicast DNS Service Discovery' there. With Debian I just disable the startup of Avahi in /etc/default/avahi-daemon by settting 'AVAHI_DAEMON_START=0'.