[Nagiosplug-devel] [ nagiosplug-Bugs-668778 ] check_ircd - invalid argument

[SourceForge.net]

Bugs item #668778, was opened at 2003-01-15 17:51
Message generated for change (Comment added) made by justdave72
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=397597&aid=668778&group_id=29880

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Harper Mann (harpermann)
Summary: check_ircd - invalid argument

Initial Comment:
Any ideas what im doing wrong here

libexec]# ./check_ircd -v -H xxx.xxx.xxx.xxx
MAIN(debug): hostname = something.host.name
MAIN(debug): binding to remote host: xxx.xxx.xxx.xxx -
> 6667 -> something.host.name
IRCD UNKNOWN: Could not connect socket (Invalid 
argument)

something.host.name and xxx.xxx.xxx.xxx are valid 
hostnames and ips just edited out in this post

I get the same (IRCD UNKNOWN: Could not connect 
socket (Invalid argument)) as status when it is run by 
nagios.

 ./check_ircd -V
check_ircd (nagios-plugins 1.3.0-beta2) 1.3
The nagios plugins come with ABSOLUTELY NO 
WARRANTY. You may redistribute
copies of the plugins under the terms of the GNU 
General Public License.
For more information about these matters, see the file 
named COPYING.


This is when it is run in its unmodified form installed 
from source and compiled, or usign an rpm build

Thanks in advance for any advice.

Sarah


----------------------------------------------------------------------

Comment By: David Miller (justdave72)
Date: 2009-09-18 02:32

Message:
The problem seems to be that check_ircd is attempting to bind to the
interface that goes with the machine's primary hostname.  In many cases
that's not correct.  I was also getting this error if I had my hostname
assigned to 127.0.0.1 in /etc/hosts, but removing that caused a timeout. 
This is because my monitoring host has interfaces on several vlans, and
without the entry in /etc/hosts, the dns hostname resolves to the primary
interface's IP address, which isn't necessarily the interface that can talk
to the host being monitored.

I commented out the bind() command and it now works.  If you don't bind()
at all, Socket will automatically pick the interface whose routes include
your destination address when you connect().

----------------------------------------------------------------------

Comment By: Harper Mann (harpermann)
Date: 2006-07-24 15:59

Message:
Logged In: YES 
user_id=939531

This is coded correctly.  You need the "canonical" host name
first in the /etc/hosts file so it's recognizedc by the
remote system.  
>From the "hosts" /etc/hosts man page:
 "IP_address canonical_hostname aliases"
 Example:
 "127.0.0.1       localhost
  192.168.1.10    foo.mydomain.org  foo"
Check_ircd works correctly if hosts are set properly with
FQDN in DNS or /etc/hosts.  
[hmann at sirius plugins-scripts]$ ./check_ircd -w 4000 -c 5000
-H niven.freenode.net
IRCD ok - Current Local Users: 3929
[hmann at sirius plugins-scripts]$ echo $?
0

Closing this one..
- Harper

----------------------------------------------------------------------

Comment By: Matthew Kent (mattkent)
Date: 2004-12-05 17:31

Message:
Logged In: YES 
user_id=983566

I'm having this problem in my testing as well (perl, v5.8.4
debian unstable). It seems to be something broken in perl's
socket code. It's mentioned here
http://wiki.apache.org/spamassassin/IoSocketInetInvalidArgument

The solution for me was to remove my computers hostname from
the /etc/hosts loopback

127.0.0.1       azul localhost
to
127.0.0.1       localhost

and poof it works... strange problem indeed!

----------------------------------------------------------------------

Comment By: Ton Voon (tonvoon)
Date: 2004-11-23 19:50

Message:
Logged In: YES 
user_id=664364

Moving to Bugs tracker as Support Requests will be closed.

----------------------------------------------------------------------

Comment By: Stanley Hopcroft (stanleyhopcroft)
Date: 2004-11-22 23:56

Message:
Logged In: YES 
user_id=395628

I can't repeat this behaviour (ie invalid argument -H)
with check_ircd in the 1.4 alpha plugins release (check_ircd
(nagios-plugins 1.4.0alpha2) 1.3).

Would you retry with this release ?

(Unfortch I can't test the plugin function).



----------------------------------------------------------------------

Comment By: Stanley Hopcroft (stanleyhopcroft)
Date: 2004-11-22 22:06

Message:
Logged In: YES 
user_id=395628

I can't repeat this behaviour (ie invalid argument -H)
with check_ircd in the 1.4 alpha plugins release (check_ircd
(nagios-plugins 1.4.0alpha2) 1.3).

Would you retry with this release ?

(Unfortch I can't test the plugin function).



----------------------------------------------------------------------

Comment By: Subhendu Ghosh (sghosh)
Date: 2003-01-16 00:58

Message:
Logged In: YES 
user_id=46572

Is your IRC server running on port 6667 ??

Please followup on the mailing list.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=397597&aid=668778&group_id=29880