HP/Compaq ILO and check_http

Karl DeBisschop karl at debisschop.net
Tue Jun 10 13:16:13 CEST 2003


On Tue, 2003-06-10 at 02:40, Jens Kruse wrote:
> Hi Karl,
> 
> Karl DeBisschop wrote:
> 
> > I wonder if runnig tcpdump or ethereal while making the request would
> > provide useful data? Maybe log the connection once for wget and a second
> > time for for check_http?

> OK, here's the dump for wget ...

I have only just scanned it, but it looks to me like the ILO is
streaming the data...

Could that be true?

If so, you need to be able put a size and/or time limit on it. You would
probably like to be able to say 'report an error if in n seconds less
than j bytes are delivered.'

Does that make any sense for your context? (I admit I'm doing alot of
guessing here still, as I still don't know much [anything, actually]
about the device -- I've heard of a 'Lights Out' card for campaq, I
think - is that what this is? Are there any technical specs available
for the device? Do they say anything about a streaming mode or something
similar?)

I don't think you can set a max on bytes delivered with check_http
presently, tyhough you can with check_tcp from CVS. But it's a feature
that could and probably should be added.

--
Karl

> <------------------------ schnipp ------------------------------>
> monitor2-lx:~ # tcpdump -i eth0 host 10.35.178.154
> tcpdump: listening on eth0
> 08:33:48.382982 monitor2-lx.mobilcom.de.57059 > 
> mccg-lx-rilo.mobilcom.de.http: S 307329410:307329410(0) win 5840 <mss 
> 1460,sackOK,timestamp 196131746 0,nop,wscale 0> (DF)
> 08:33:48.383782 arp who-has monitor2-lx.mobilcom.de (0:50:8b:e2:2e:b3) 
> tell mccg-lx-rilo.mobilcom.de
> 08:33:48.383798 arp reply monitor2-lx.mobilcom.de is-at 0:50:8b:e2:2e:b3
> 08:33:48.384202 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57059: S 693572000:693572000(0) ack 307329411 
> win 5840 <mss 1460>
> 08:33:48.384223 monitor2-lx.mobilcom.de.57059 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 1 win 5840 (DF)
> 08:33:48.384364 monitor2-lx.mobilcom.de.57059 > 
> mccg-lx-rilo.mobilcom.de.http: P 1:99(98) ack 1 win 5840 (DF)
> 08:33:48.387907 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57059: P 1:16(15) ack 99 win 5840
> 08:33:48.387921 monitor2-lx.mobilcom.de.57059 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 16 win 5840 (DF)
> 08:33:48.388731 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57059: P 16:18(2) ack 99 win 5840
> 08:33:48.388741 monitor2-lx.mobilcom.de.57059 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 18 win 5840 (DF)
> 08:33:48.389579 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57059: P 18:41(23) ack 99 win 5840
> 08:33:48.389590 monitor2-lx.mobilcom.de.57059 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 41 win 5840 (DF)
> 08:33:48.390244 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57059: P 41:43(2) ack 99 win 5840
> 08:33:48.390254 monitor2-lx.mobilcom.de.57059 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 43 win 5840 (DF)
> 08:33:48.391103 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57059: P 43:81(38) ack 99 win 5840
> 08:33:48.391113 monitor2-lx.mobilcom.de.57059 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 81 win 5840 (DF)
> 08:33:48.391732 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57059: P 81:83(2) ack 99 win 5840
> 08:33:48.391749 monitor2-lx.mobilcom.de.57059 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 83 win 5840 (DF)
> 08:33:48.392648 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57059: P 83:106(23) ack 99 win 5840
> 08:33:48.392672 monitor2-lx.mobilcom.de.57059 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 106 win 5840 (DF)
> 08:33:48.393500 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57059: P 106:125(19) ack 99 win 5840
> 08:33:48.393518 monitor2-lx.mobilcom.de.57059 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 125 win 5840 (DF)
> 08:33:48.394156 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57059: P 125:127(2) ack 99 win 5840
> 08:33:48.394175 monitor2-lx.mobilcom.de.57059 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 127 win 5840 (DF)
> 08:33:48.395005 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57059: P 127:153(26) ack 99 win 5840
> 08:33:48.395024 monitor2-lx.mobilcom.de.57059 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 153 win 5840 (DF)
> 08:33:48.395649 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57059: P 153:155(2) ack 99 win 5840
> 08:33:48.395667 monitor2-lx.mobilcom.de.57059 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 155 win 5840 (DF)
> 08:33:48.396511 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57059: P 155:157(2) ack 99 win 5840
> 08:33:48.396531 monitor2-lx.mobilcom.de.57059 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 157 win 5840 (DF)
> 08:33:48.398632 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57059: P 157:160(3) ack 99 win 5840
> 08:33:48.398668 monitor2-lx.mobilcom.de.57059 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 160 win 5840 (DF)
> 08:33:48.400319 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57059: P 160:696(536) ack 99 win 5840
> 08:33:48.400335 monitor2-lx.mobilcom.de.57059 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 696 win 6432 (DF)
> 08:33:48.400323 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57059: . 696:1232(536) ack 99 win 5840
> 08:33:48.400349 monitor2-lx.mobilcom.de.57059 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 1232 win 7504 (DF)
> 08:33:48.402360 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57059: P 1232:1464(232) ack 99 win 5840
> 08:33:48.402376 monitor2-lx.mobilcom.de.57059 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 1464 win 8576 (DF)
> 08:33:48.404361 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57059: P 1464:1936(472) ack 99 win 5840
> 08:33:48.404371 monitor2-lx.mobilcom.de.57059 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 1936 win 9648 (DF)
> 
> 
> 
> 40 packets received by filter
> 0 packets dropped by kernel
> <------------------------ schnipp ------------------------------>
> 
> And here for the check_http ...
> 
> <------------------------ schnipp ------------------------------>
> monitor2-lx:/usr/local/nagios/libexec # ./check_http -H 10.35.178.154
> Socket timeout after 10 seconds
> monitor2-lx:~ # tcpdump -i eth0 host 10.35.178.154
> tcpdump: listening on eth0
> 08:37:08.065489 monitor2-lx.mobilcom.de > mccg-lx-rilo.mobilcom.de: 
> icmp: echo request (DF)
> 08:37:08.066027 mccg-lx-rilo.mobilcom.de > monitor2-lx.mobilcom.de: 
> icmp: echo reply
> 08:37:08.280371 monitor2-lx.mobilcom.de.57412 > 
> mccg-lx-rilo.mobilcom.de.http: S 521852342:521852342(0) win 5840 <mss 
> 1460,sackOK,timestamp 196151735 0,nop,wscale 0> (DF)
> 08:37:08.281148 arp who-has monitor2-lx.mobilcom.de (0:50:8b:e2:2e:b3) 
> tell mccg-lx-rilo.mobilcom.de
> 08:37:08.281171 arp reply monitor2-lx.mobilcom.de is-at 0:50:8b:e2:2e:b3
> 08:37:08.281564 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57412: S 693771910:693771910(0) ack 521852343 
> win 5840 <mss 1460>
> 08:37:08.281620 monitor2-lx.mobilcom.de.57412 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 1 win 5840 (DF)
> 08:37:08.281827 monitor2-lx.mobilcom.de.57412 > 
> mccg-lx-rilo.mobilcom.de.http: P 1:92(91) ack 1 win 5840 (DF)
> 08:37:08.285304 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57412: P 1:16(15) ack 92 win 5840
> 08:37:08.285322 monitor2-lx.mobilcom.de.57412 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 16 win 5840 (DF)
> 08:37:08.285995 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57412: P 16:18(2) ack 92 win 5840
> 08:37:08.286007 monitor2-lx.mobilcom.de.57412 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 18 win 5840 (DF)
> 08:37:08.286883 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57412: P 18:41(23) ack 92 win 5840
> 08:37:08.286896 monitor2-lx.mobilcom.de.57412 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 41 win 5840 (DF)
> 08:37:08.287544 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57412: P 41:43(2) ack 92 win 5840
> 08:37:08.287556 monitor2-lx.mobilcom.de.57412 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 43 win 5840 (DF)
> 08:37:08.288390 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57412: P 43:81(38) ack 92 win 5840
> 08:37:08.288411 monitor2-lx.mobilcom.de.57412 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 81 win 5840 (DF)
> 08:37:08.289048 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57412: P 81:83(2) ack 92 win 5840
> 08:37:08.289211 monitor2-lx.mobilcom.de.57412 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 83 win 5840 (DF)
> 08:37:08.289944 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57412: P 83:106(23) ack 92 win 5840
> 08:37:08.290077 monitor2-lx.mobilcom.de.57412 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 106 win 5840 (DF)
> 08:37:08.290896 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57412: P 106:108(2) ack 92 win 5840
> 08:37:08.291064 monitor2-lx.mobilcom.de.57412 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 108 win 5840 (DF)
> 08:37:08.291821 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57412: P 108:155(47) ack 92 win 5840
> 08:37:08.291898 monitor2-lx.mobilcom.de.57412 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 155 win 5840 (DF)
> 08:37:08.292734 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57412: P 155:157(2) ack 92 win 5840
> 08:37:08.292851 monitor2-lx.mobilcom.de.57412 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 157 win 5840 (DF)
> 08:37:08.294812 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57412: P 157:160(3) ack 92 win 5840
> 08:37:08.294978 monitor2-lx.mobilcom.de.57412 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 160 win 5840 (DF)
> 08:37:08.296288 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57412: P 160:696(536) ack 92 win 5840
> 08:37:08.296379 monitor2-lx.mobilcom.de.57412 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 696 win 6432 (DF)
> 08:37:08.297090 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57412: . 696:1232(536) ack 92 win 5840
> 08:37:08.297142 monitor2-lx.mobilcom.de.57412 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 1232 win 7504 (DF)
> 08:37:08.299364 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57412: P 1232:1768(536) ack 92 win 5840
> 08:37:08.299417 monitor2-lx.mobilcom.de.57412 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 1768 win 8576 (DF)
> 08:37:08.301282 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57412: P 1768:1936(168) ack 92 win 5840
> 08:37:08.301752 monitor2-lx.mobilcom.de.57412 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 1936 win 8576 (DF)
> 08:37:09.072478 monitor2-lx.mobilcom.de > mccg-lx-rilo.mobilcom.de: 
> icmp: echo request (DF)
> 08:37:09.072998 mccg-lx-rilo.mobilcom.de > monitor2-lx.mobilcom.de: 
> icmp: echo reply
> 08:37:10.072510 monitor2-lx.mobilcom.de > mccg-lx-rilo.mobilcom.de: 
> icmp: echo request (DF)
> 08:37:10.072984 mccg-lx-rilo.mobilcom.de > monitor2-lx.mobilcom.de: 
> icmp: echo reply
> 08:37:11.072511 monitor2-lx.mobilcom.de > mccg-lx-rilo.mobilcom.de: 
> icmp: echo request (DF)
> 08:37:11.072996 mccg-lx-rilo.mobilcom.de > monitor2-lx.mobilcom.de: 
> icmp: echo reply
> 08:37:12.072495 monitor2-lx.mobilcom.de > mccg-lx-rilo.mobilcom.de: 
> icmp: echo request (DF)
> 08:37:12.072990 mccg-lx-rilo.mobilcom.de > monitor2-lx.mobilcom.de: 
> icmp: echo reply
> 08:37:18.272849 monitor2-lx.mobilcom.de.57412 > 
> mccg-lx-rilo.mobilcom.de.http: F 92:92(0) ack 1936 win 8576 (DF)
> 08:37:18.273526 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57412: . ack 93 win 5840
> 08:37:18.274257 mccg-lx-rilo.mobilcom.de.http > 
> monitor2-lx.mobilcom.de.57412: F 1936:1936(0) ack 93 win 5840
> 08:37:18.274280 monitor2-lx.mobilcom.de.57412 > 
> mccg-lx-rilo.mobilcom.de.http: . ack 1937 win 8576 (DF)
> 
> 
> 
> 50 packets received by filter
> 0 packets dropped by kernel
> <------------------------ schnipp ------------------------------>
> 
> Maybe the ICMP Packages are a hint ... ?
> 
> > Since I know zip about this ILO thingie, I'm not coming up with alot of
> > other ideas.
> 
> Thnaks for helping!
> 
> Jens
> 
> 
> >>On Fri, 6 Jun 2003, Jens Kruse wrote:
> >>
> >>
> >>>Hi -sg,
> >>>
> >>>Subhendu Ghosh wrote:
> >>>
> >>>
> >>>>have you tried the timeout option (-t) 
> >>>>It defaults to 10 seconds and then sends a SIGALARM to self.
> >>>
> >>>Yes, same behavior ...
> >>>
> >>>
> >>>>port 80 transaction looks fine - can you run it under "time" and see how 
> >>>>long it took?
> >>>
> >>>Appr. 2 sec., so the -t option didn't help too ...
> >>>
> >>>
> >>>>port 443 should be ssl so a regular telnet will not work. Try wget or 
> >>>>curl.
> >>>
> >>>All right, it works with wget:
> >>>
> >>>monitor2-lx:/usr/local/nagios/libexec # wget https://10.35.178.154/
> >>>--15:10:47--  https://10.35.178.154/
> >>>            => `index.html'
> >>>Connecting to 10.35.178.154:443... connected!
> >>>HTTP request sent, awaiting response... 200 Ok
> >>>Length: unspecified [text/html]
> >>>
> >>>     0K .
> >>>
> >>>Does this give you a clue?
> >>>
> >>>Regards, Jens
> >>>
> >>>
> >>>
> >>>
> >>>>>>But, to start, have you tried the --verbose option? What was the output?
> >>>>>
> >>>>>Yes I did:
> >>>>>
> >>>>>monitor1-lx:~ # /usr/local/nagios/libexec/check_http -H 10.35.178.154 -p 
> >>>>>80 --verbose
> >>>>>Socket timeout after 10 seconds
> >>>>>
> >>>>>That's the result I receive with or without the --verbose option ...
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>>Have you tried just running the seesion over telnet?
> >>>>>
> >>>>>Yes. It works with port 80:
> >>>>>
> >>>>>monitor1-lx:~ # telnet 10.35.178.154 80
> >>>>>Trying 10.35.178.154...
> >>>>>Connected to 10.35.178.154.
> >>>>>Escape character is '^]'.
> >>>>>GET
> >>>>>HTTP/1.1 405 Method Not Allowed
> >>>>>Content-Type:text/html
> >>>>>
> >>>>><HTML><HEAD><TITLE>Remote Insight</TITLE></HEAD><BODY>
> >>>>><H1>Request Error</H1>
> >>>>>HTTP/1.1 405 Method Not Allowed
> >>>>></BODY></HTML>
> >>>>>Connection closed by foreign host.
> >>>>>
> >>>>>
> >>>>>But not with 443:
> >>>>>
> >>>>>monitor1-lx:~ # telnet 10.35.178.154 443
> >>>>>Trying 10.35.178.154...
> >>>>>Connected to 10.35.178.154.
> >>>>>Escape character is '^]'.
> >>>>>GET
> >>>>>
> >>>>>
> >>>>>I also tried it with 'strace':
> >>>>>
> >>>>>monitor1-lx:~ # strace /usr/local/nagios/libexec/check_http -H 
> >>>>>10.35.178.154 -p 80 --verbose
> >>>>>
> >>>>>The final output
> >>>>>...
> >>>>>connect(3, {sin_family=AF_INET, sin_port=htons(80), 
> >>>>>sin_addr=inet_addr("10.35.178.154")}}, 16) = 0
> >>>>>send(3, "GET / HTTP/1.0\r\nHost: 10.35.178."..., 91, 0) = 91
> >>>>>recv(3, "HTTP/1.1 200 Ok", 1023, 0)     = 15
> >>>>>recv(3, "\r\nContent-Type: text/html\r\n", 1023, 0) = 27
> >>>>>recv(3, "Expires: Fri, 30 Oct 1998 14:19:"..., 1023, 0) = 38
> >>>>>recv(3, "\r\nCache-Control: no-cache\r\nConne"..., 1023, 0) = 44
> >>>>>recv(3, "\r\nTransfer-Encoding: chunked\r\n\r\n", 1023, 0) = 32
> >>>>>recv(3, "514", 1023, 0)                 = 3
> >>>>>recv(3, "\r\n<!DOCTYPE HTML PUBLIC \"-//W3C/"..., 1023, 0) = 536
> >>>>>brk(0x8052000)                          = 0x8052000
> >>>>>recv(3, " licensed to the U.S. Government"..., 1023, 0) = 1023
> >>>>>brk(0x8053000)                          = 0x8053000
> >>>>>recv(3, " server is not configured to use"..., 1023, 0) = 49
> >>>>>brk(0x8054000)                          = 0x8054000
> >>>>>recv(3, "ou will not be able \r\nto communi"..., 1023, 0) = 168
> >>>>>recv(3, 0x804f440, 1023, 0)             = ? ERESTARTSYS (To be restarted)
> >>>>>--- SIGALRM (Alarm clock) ---
> >>>>>fstat64(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), ...}) = 0
> >>>>>old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, 
> >>>>>-1, 0) = 0x40016000
> >>>>>write(1, "Socket timeout after 10 seconds\n", 32Socket timeout after 10 
> >>>>>seconds
> >>>>>) = 32
> >>>>>munmap(0x40016000, 4096)                = 0
> >>>>>_exit(2)                                = ?
> >>>>>
> >>>>>
> >>>>>It stops until it receives a SIGALRM ... (from whome? - The embedded 
> >>>>>webserver? - Thats the part I do not understand)
> >>>>>
> >>>>>
> >>>>>In addition: We use iLO Firmware 1.26
> >>>>>
> >>>>>Can I provide you more information to find a solution for this?
> >>>>>
> >>>>>Regards,
> >>>>>
> >>>>>Jens
> >>>>>
> >>>>
> > 
> > 
> > 
> > -------------------------------------------------------
> > This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
> > thread debugger on the planet. Designed with thread debugging features
> > you've never dreamed of, try TotalView 6 free at www.etnus.com.
> > _______________________________________________
> > Nagios-users mailing list
> > Nagios-users at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/nagios-users
> > ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
> > ::: Messages without supporting info will risk being sent to /dev/null



-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null





More information about the Users mailing list