Nagios 3.4.0 double quote in command bug (fixed)

[Dennis Kuhlmeier]

Hi,

sorry to burst into this, is this about the changed behaviour with
quoted text? I was able to fix it in my check definitions (removing
not needed quotes, etc.) in most cases, also using any kind of
special character, e.g. "|" or "*" fixes this, but I am still unable
to pass check results to a remote Nagios instance by sending them
via NSCA. I use perfdata processing for this and only check results
with special characters (all checks that do actually have
performance data fulfill this as they all contain the pipe
character) are processed, others never even show up in my definied
service_perfdata_file!

Switched backed to Nagios 3.2.3 and everything works like a charm.

Are both problems connected and fixed in an upcoming 3.4 release?

Regards,

Dennis

On 14.05.12 11:31, Randal, Phil wrote:
> Hi Andreas,
> 
> Yours is probably the safest approach.
> 
> Cheers,
> 
> Phil
> 
> --
> Phil Randal
> Infrastructure Engineer
> Hoople Ltd | Thorn Office Centre | Hereford HR2 6JT
> Tel: 01432 260415 | Email: phil.randal at hoopleltd.co.uk
> 
> 
> -----Original Message-----
> From: Andreas Ericsson [mailto:ae at op5.se]
> Sent: 14 May 2012 00:17
> To: Nagios Users List
> Cc: Randal, Phil
> Subject: Re: [Nagios-users] Nagios 3.4.0 double quote in command bug (fixed)
> 
> On 05/13/2012 10:44 PM, Randal, Phil wrote:
>> I've uploaded a patch to
>>
>> http://tracker.nagios.org/view.php?id=332
>>
>> Which fixes the double quote issue and my original compile problem.
>>
> 
> Thanks. The double-quote issue has been resolved by reverting the faulty patch though. I'll see if I get time to take a look at the compile problem tomorrow.
> 
> --
> Andreas Ericsson                   andreas.ericsson at op5.se
> OP5 AB                             www.op5.se
> Tel: +46 8-230225                  Fax: +46 8-230231
> 
> Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace.
> “Any opinion expressed in this e-mail or any attached files are those of the individual and not necessarily those of Hoople Ltd. You should be aware that Hoople Ltd. monitors its email service. This e-mail and any attached files are confidential and intended solely for the use of the addressee. This communication may contain material protected by law from being passed on. If you are not the intended recipient and have received this e-mail in error, you are advised that any use, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited. If you have received this e-mail in error please contact the sender immediately and destroy all copies of it.
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> 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
> 
> 



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
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