Hello
I wonder if you could help me, we have been using nagios 2 for a number of 
years now and after plenty of research i have decided to replace this with a 
icinga 1 implementation (as icinga 2 is in development at the moment we don't 
want to be too bleeding edge so have decided to stay with icinga 1 for the time 
being)
I have installed icinga 1.10.3 on ubuntu 12.04 lts
we have transferred our nagios checks over to the new icinga box maining by 
importing the old config files into nagiosql, after removing some of the 
historic rubbish that has built up over time i now have a working icinga 
implementation.
however we do seem to be have a few problems with any check that includes 
backslashes in the status information output, this is usually from checks that 
output a file path (say for files that haven't been processed for a period of 
time as we are using it to monitor folders for file processing systems)  This 
checks display the path in the previous nagios 2 system and they display 
properly in the icinga-web gui, but they don't display in the status 
information for the icinga classic ui.
So my question is, is this a known bug is there any way to get this working 
other that recording the checks to output a double slash, i know this will 
probably fix it for icinga classic but then will probably break the output for 
icinga-web.  As we are intending on using a mixture of icinga classic and 
icinga-web i would like it working on both interfaces.
So is they any other way to fix this, is this a config item for icinga classic 
that get the output back to how it works in nagios 2.
by the way alot of these check are check_nrpe to windows boxes, but if i run 
them on the command line of the icinga server the output is correct so believe 
it purely an output problem with icinga classic ui.
King Regards
Mike Shaw                                         
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users

Reply via email to