> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:nagios-users- > [EMAIL PROTECTED] On Behalf Of Bráulio H. Soares > Sent: Tuesday, March 04, 2008 2:35 PM > To: Patrick Morris > Cc: [email protected] > Subject: [Nagios-users] RES: Parameters not passed to event handler's > script > > To test effects, consider the script like the example available at Nagios > online docs, with some modifications (see the attachment). > > The command with the parameters is this: > command_line /fakepath/nagios/fake_script $SERVICESTATE$ > $SERVICESTATETYPE$ $SERVICEATTEMPT$
See below... > -----Mensagem original----- > De: Patrick Morris [mailto:[EMAIL PROTECTED] > Enviada em: terça-feira, 4 de março de 2008 17:24 > Para: Bráulio H. Soares > Cc: [email protected] > Assunto: Re: [Nagios-users] Parameters not passed to event handler's > script > > Hi Br?ulio! > > On Tue, 04 Mar 2008, Br?ulio H. Soares wrote: > > > Hi people, > > > > I?ve a Nagios 3rc1 with a very simple configuration and I?m facing a > problem while using Event Handler. > > > > When the script run, in the logs I can to verify that the parameters is > not passed to the code. See below: > > > > [1204655932] SERVICE ALERT: host1.fake.int;PING;CRITICAL;SOFT;1;PING > CRITICAL - Packet loss = 100% > > [1204655962] HOST ALERT: host1.fake.int;DOWN;SOFT;1;(Host Check Timed > Out) > > [1204655962] HOST EVENT HANDLER: > host1.fake.int;(null);(null);(null);fakescript $SERVICESTATE$, $SERVICESTATETYPE$, $SERVICEATTEMPT$ macros are not valid for host event handlers, only service event handlers. http://nagios.sourceforge.net/docs/3_0/macrolist.html -- Marc ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Nagios-users mailing list [email protected] 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
