18W LED Lamp (Warm White)

New light? Enough money? Take a future-ready LED lamp.
No, not these cheap ones with only 1W and cool white sick light.

How about this?
18W (9x2W) LED Lamp with 88° beam angle and nice warm white light ( BLT3827D120-XWW92HRL )



comparing with a 50W halo lamp



and both together



Your choose?



Say Yes.

IBM Tivoli Monitoring (ITM) vs nagios nrpe

Your slaves need watching, right?
There is IBM Tivoli Monitoring (ITM) 6.2 packaged as custom rpm

108624525 Bytes itm-6.2-2.6_1.x86_64.rpm

includes

# du -sk *
1112 bin
23044 classes
8152 config
40 etc
7884 gskit
680 HTML
2328 images
1000 InstallITM
72416 JRE
168 keyfiles
804 LAP
920 licenses
136 logs
39884 lx8266
52 misc
100 registry
39280 tmaitm6
8 tmp

and you have nagios nrpe 2.12

36998 Bytes nagios-nrpe-2.12-1.x86_64.rpm

includes

# du -sk *
60 bin
52 etc
2528 libexec
64 libexec-custom
164 share

So, one question: Who survive the wilderness?
The big-fat one or the slim-easy one?

red hat network satellite and older system date

you use also an enterprise installation environment like red hat network satellite and configure channels, kickstart options, fill pre and post script section with custom code. This take some time and at end of a working day you want see some results.
Firing up a new empty server and processing installation fail.
Your are nerved and look at ks-post.log:

# cat ks-post.log
...
An error has occurred:
The SSL certificate failed verification.
See /var/log/up2date for more information
ERROR: unable to read system id.
ERROR: unable to read system id.
ks-post script start
...

So secure connection to your red hat network satellite failed.

Ommm and why?
Maybe you was lazy and forgot to check new server date.
If new server date is older then the satellite SSL cert startdate you will get a SSL error. Comparing with your red hat network satellite

# echo | openssl s_client -connect satellite:443 2>/dev/null | sed -n '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p' | openssl x509 -noout -startdate
notBefore=Dec 24 12:00:00 2008 GMT

you found a reason and smile.

Right and how to fix?
Well to be lazy furthermore, you need a way to say it to your slave.
You can not use kickstart post script (see ks-post.log above) so you will use
the pre script. You know there is ntpdate to correct the new server date, but kickstart pre script environment support only this commands:
http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Installation_Guide-en-US/s1-redhat-config-kickstart-prescript.html
Unfortunately no ntpdate but date and hwclock command.

Set a date after SSL cert startdate and sync it to hardware clock will do the trick at pre script:
# need a server date after satellite SSL cert startdate
# date -s 010100002009
# hwclock --systohc

I'm sure redhat will support in upcoming versions a ntpdate command at pre script section.
In the meantime have a nice day and keep your slaves running...