Page 1 of 1
Unable to delete unconfigured objects
Posted: Sat Jun 04, 2011 10:39 am
by arnab.roy
HI All,
We have setup where snmp traps are being sent to us but some of the traps dont have a service associated with them hence they result in unconfigured objects in the system, I have tried deleting them manually it says its deleted but it doesnt ! I would like to know if there is a way of turning this feature off completely or better handle this situation. Also I think something is not right about the deletion of the unconfigured objects from the GUI.
Thanks
Arnab
Re: Unable to delete unconfigured objects
Posted: Mon Jun 06, 2011 9:58 am
by nscott
Arnab.Roy,
How did you try to delete it from the GUI? Were you trying to delete them under Admin > Monitoring Config > Unconfigured Objects ?
Re: Unable to delete unconfigured objects
Posted: Mon Jun 06, 2011 12:59 pm
by arnab.roy
Yes from the admin tab, i have a whole load of these now and I am unable to delete it ....Require your help asap.
Cheers
arnab
Re: Unable to delete unconfigured objects
Posted: Mon Jun 06, 2011 1:07 pm
by mguthrie
Currently if new results continue to come in, if I understand it correctly the Unconfigured Objects page will probably offer to generate configs for these new objects that continue to send results. This component parses the log files for unhandled passive checks that are coming in to the Nagios server and generates a list based on that. The list of Unconfigured Objects is generated upon that particular page load, and it's dynamic based on what is in the log.
Re: Unable to delete unconfigured objects
Posted: Mon Jun 06, 2011 2:44 pm
by arnab.roy
hi
thats not happening infact its showing old stale data for devices that are no longer on the network
so I should be able to delete it. is it looking at the nagios log files
cheers
arnab
Re: Unable to delete unconfigured objects
Posted: Mon Jun 06, 2011 4:58 pm
by mguthrie
Ok, my guess is that may be a logical bug in that component then. I'll ask our lead developer about that and get a report posted to the bug tracker.