SMTP Checks Always Critical

[Fredrik Wänglund]

You should have this line in check_smtp.c:

#define SMTP_QUIT       "QUIT\r\n"

If you don't - Fix it and recompile...


/FredrikW



-----Original Message-----
From:	Marc Powell [mailto:mpowell at ena.com]
Sent:	Wed 12-Feb-03 16:17
To:	Sarkees, Steve; Tom DE BLENDE
Cc:	nagios-users at lists.sourceforge.net
Subject:	RE: [Nagios-users] SMTP Checks Always Critical
As a followup to my previous short email, the problem is that Exchange
expects to see a \r\n after the QUIT but the previous plugin version
only sent a \r (or \n, I can't remember). The net effect was that while
the SMTP service would respond OK, the connection wouldn't terminate
properly leading to the CRITICAL status because of a timeout.

--
Marc

> -----Original Message-----
> From: Sarkees, Steve [mailto:steves at ipctech.com]
> Sent: Wednesday, February 12, 2003 8:40 AM
> To: 'Tom DE BLENDE'
> Cc: nagios-users at lists.sourceforge.net
> Subject: RE: [Nagios-users] SMTP Checks Always Critical
> 
> Hope this helps.. I appreciate the help.
> 
> ##Verbose Output in Nagios (actually show critical)
> 
> SMTP
>   CRITICAL 02-12-2003 09:47:11 8d 10h 41m 53s 6/6 SMTP OK - 0 sec.
> response
> time, 220 vafb.com Microsoft ESMTP MAIL Service, Version:
5.0.2195.5329
> ready at Wed, 12 Feb 2003 09:43:52 -0500
> 
> 
> ##Checkcommands.cfg for check_smtp
> 
> define command {
> command_name                   check_smtp
> command_line                   $USER1$/check_smtp -H $HOSTADDRESS$ -c
120
> -v
> }
> 
> 
> ##Services.cfg Config:
> 
> define service {
> use                            generic-service          ; Name of
service
> template to use
> host_name                      VFBEXCHANGE2
> service_description            SMTP
> is_volatile                    0
> check_period                   24x7
> max_check_attempts             6
> normal_check_interval          5
> retry_check_interval           2
> contact_groups                 engineering
> notification_interval          120
> notification_period            24x7
> notification_options           w,u,c,r
> check_command                  check_smtp
> }
> 
> -----Original Message-----
> From: Tom DE BLENDE [mailto:tdeblend at gcc.dhl.com]
> Sent: Wednesday, February 12, 2003 9:41 AM
> To: Sarkees, Steve
> Cc: nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] SMTP Checks Always Critical
> 
> 
> 
> > "Sarkees, Steve" wrote:
> >
> >It is possible that my syntax is incorrect..?..
> 
> Well, if you'd paste it here, we could have a look... Together with
> the output...
> 
> 
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.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:
SourceForge Enterprise Edition + IBM + LinuxWorld =omething 2 See!
http://www.vasoftware.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:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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