error in config files after first discovery

[alfl]

Hello Forum,

I am new using NagiosXI and downloaded the VMWare version.

All went while and i run an full discovery over my network to let the nagios system discover all network attached devices and servers.

I could place checkmarks on all servers and services it found and then tryed to make the final step. This went in error and the text file i could check gave on every server and device the following errors:
Running pre-flight check on configuration data...

Checking services...
Error: The description string for service 'TCP Port 8000 (irdmi)' on host '10.1.0.4' contains one or more illegal characters.
Error: The description string for service 'TCP Port 8100 (xprint-server)' on host '10.1.0.4' contains one or more illegal characters.
Error: The description string for service 'TCP Port 515 (printer)' on host 'dymo.gandalf.local' contains one or more illegal characters.
Error: The description string for service 'TCP Port 9101 (bacula-dir)' on host 'dymo.gandalf.local' contains one or more illegal characters.

etc.

I didn't do anything else.
I only used the web interface and don't know if i can change any config file as all files say that these will be overwritten by QL scripts.

I attached the complete logfile

How can i add a new device to the monitoring server ?

[lmiltchev]

Nagios cannot start or restart with configuration errors. You will have to remove the illegal characters from your service definitions through the Nagios Core Config Manager in order to be able to apply successfully the configuration. Please, read more about the illegal characters (under "Illegal Object Name Characters") here:

http://nagios.sourceforge.net/docs/nagi ... gmain.html

[alfl]

I understand this, only i don't know how to change this in NagiosXI as i don't know where these files are generated. Also, the names are autogenerated bij NagiosXI and i couldn't make any adjustments to these namings.

[nscott]

It appears there is a bug where it will let certain special characters through that it shouldn't. The fix for now is to remove the special characters in the CCM by hand, and when you run auto discovery jobs in the future, quickly scan the names for special characters, until an update is released.