All checks timeout after completing successfully
Brought to you by:
jcrix
Menu
▾
▴
#2 All checks timeout after completing successfully
It seems that the AS400 checks were working for a while
without a hiccup. Lately, however, when I run the
plugin from the command line it connects, does the
check, returns the nagios string correctly, and then
sits there waiting for something to happen that never
does. As if the connection to the remote AS400 server
could not be dropped.
/usr/local/j2re1.4.2_05/bin/java -cp
/etc/nagios/custom_plugins check_as400 -D -H
aa.bb.cc.dd -v LOGIN -u testuser -p testpassword
Establishing connection to server...done.
Logging in...
waiting for screen...
waiting for token IBM CORP...
**BUFFER IS:**
??'??
**END OF BUFFER**
**BUFFER IS:**
??'??
System.......: FOOLSDR Subsystem..: QINTER
Display....: CNIDEV0065
LOGIN screen is then shown, everything goes well, and then:
User . . . . . . Password
. . . . **END OF BUFFER**
token received.
Login completed.BM CORP. 1980, 2003.
Sending command (6)...
OK - Login completed successfully
Logging out...
sending F3...
waiting for token ===>...
**BUFFER IS:**
MAIN OS/400 Main Menu
System: FOOLSDR Select one of the following:
1. User tasks
2. Office tasks
3. General system tasks
4. Files, libraries, and folders
5. Programming
6. Communications
7. Define or change the system
8. Problem handling
9. Display a menu
10. Information Assistant options
11. iSeries Access tasks
90. Sign off
Selection or command
===> **END OF BUFFER** F3=Exit F4=Prompt
F9=Retrieve F12=Cancel F13=Information Assistant
token received.nu
requesting signoff.... 1980, 2003.
waiting for token ;53H...
**BUFFER IS:**
signoff
... same ...
**BUFFER IS:**
signoff
The same screen repeated adn I press CTRL+C to get out
of the plugin.
What is holding up the session open? There is no way to
tell the AS400 plugin to not be nice about dropping the
connection once the Nagios string (plugin output) have
been printed?
What about a way to timeout (-t) the plugin after N
seconds? And perhaps detect that everything actually
went well and not exit with a warn/crit exit code once
the plugin times out.
Cheers.
Logged In: NO
Hi!
if you're still having this problem please contact me!
I had the same problem, but now i solved it ;-)
f01411@heidekreis.de
Logged In: YES
user_id=239796
Sure. I'm still having this problem. Can you post your
solution to this bug thread so that we all know what the
answer is? (unless the information is sensitive in nature
that is).