> > Hi,
> > Suddenly my hostextinfo.cfg is not working. Anyone has an idea what
> > can be wrong ?
> > Thanks.
> > Reading configuration data...
> >
> > Error: Invalid object definition type 'hostextinfo' in file
> > '/etc/nagios/hostextinfo.cfg' on line 1.
>
> How do you have this file defined in nagios.cfg? Should be cfg_file.
> Otherwise I'd say you have some non-printable character inserted somewhere
> within the word 'hostextinfo'.
There must be a simple solution but I can't find it :-(
Still not working and only printable characters in hostextinfo.cfg
nagios.cfg says:
cfg_file=/etc/nagios/hostextinfo.cfg
and when I remove this line nagios can start without problem.
I copied a hostextinfo.cfg from another installation and that also
didn't work with my
nagios even it works on the other installation.
I have also tried to make a very small hostextinfo.cfg file for
testing. Still no luck.
sirius:/etc/nagios# od -x hostextinfo.cfg
0000000 6564 6966 656e 6820 736f 6574 7478 6e69
0000020 6f66 0a7b 6809 736f 5f74 616e 656d 7309
0000040 7269 7569 0a73 6909 6f63 5f6e 6d69 6761
0000060 0965 6172 6b63 6c5f 6e69 7875 702e 676e
0000100 090a 6369 6e6f 695f 616d 6567 615f 746c
0000120 6e09 6761 6f69 0973 090a 7473 7461 7375
0000140 616d 5f70 6d69 6761 0965 6172 6b63 6c5f
0000160 6e69 7875 702e 676e 090a 0a7d 0a0a
0000176
sirius:/etc/nagios# cat hostextinfo.cfg
define hostextinfo{
host_name sirius
icon_image rack_linux.png
icon_image_alt nagios
statusmap_image rack_linux.png
}
Regards
Martin
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Nagios-users mailing list
Nagios-users@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
