Spot on! It was check_smsgateway I ran a quick script to see if a
plugin was causing the problem and got the exact same error message.
I've moved the script out of the way for now
/usr/local/nagios/libexec# for i in * ; do echo running $i && ./$i -h ;
done
Which showed me 2 plugins - check_xml.pl and check_smsgateway.pl
I moved these 2 out of the way and things went much smoother, altho it
did fail again when restarting opsview and opsview-agent so I hacked the
init scripts to make sure opsview and opsview-agent were stopped before
being started again and all is now well
Thanks for the help!
Steve
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Ton Voon
Sent: Sunday, September 13, 2009 11:28 PM
To: Opsview Users
Subject: Re: [opsview-users] Upgrading to 3.3.1
On 12 Sep 2009, at 23:03, Steve Ofsoski wrote:
Hi, everything was going smoothly during the upgrade to
3.1.1 on an Ubuntu 8.04 LTS server until I got this error message and I
have no idea where to look:
All monitoring servers successfully updated
Use of uninitialized value in subroutine entry at
/usr/lib/perl/5.8/Socket.pm line 201.
Bad arg length for Socket::pack_sockaddr_in, length is
0, should be 4 at /usr/lib/perl/5.8/Socket.pm line 201.
Hitting ctrl-c after letting it sit there for over 30
mins continues the rest of the process, but according to apt the
packages are still not installed correctly
After the upgrade, we do a step where we run all the plugins in
/usr/local/nagios/libexec with the -h option. This allows Opsview to
capture the help output for display in the user interface.
My guess is that one of your plugins is not expecting a -h
option, so is executing and actually running to return those Socket
error messages.
And I guess another plugin is waiting for input, hence the 30
minutes waiting.
We'll look into some debug tools for this.
Ton
_______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/lists/listinfo/opsview-users
