Tom, I was just responding Gumilar from my own experience from long time ago about the polling disable discovery if not pingable, havnt even thought about it the last time.
/P
2017-04-24 13:01 GMT+02:00 Tom Laermans tom.laermans@powersource.cx:
Hi Peter,
When did you last update Observium?
There was a while that we enabled a few caching functions by default, leading to this issue (but it should turn up in the web interface after 5 minutes, regardless).
A bit later we disabled the caching again so things should work on latest version.
Let us know if this is not the case.
Tom On 04/24/2017 11:17 AM, Peter Persson wrote:
Would more say that it isnt responding to ping, and discovery isnt checking that. Try a manual polling and Observium checks.
2017-04-24 9:56 GMT+02:00 Daniel Johansson daz@voodoo-people.com:
Did you disable the polling for it? If so look under disabled devices and enable it again.
/Daniel
On Apr 24, 2017 9:40 AM, Gumilar Siegfried <siegfried.gumilar@stadtwerke- feldkirch.at> wrote:
Hello!
We have a device that is no longer visible in Observium. It is not in the device list and the search function can’t find it.
I tried to add it again to Observium, but get this message: “Already got device xyz.”
Running “./discovery.php -h xyz” returns this: “WARNING: 0 devices discovered. Did you specify a device that does not exist?”
Is there something wrong with our database? How to fix it?
Thanks,
Siegfried
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing listobservium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium