Joey Stanford

30 June 2018 at 18:16

Yeah I don’t get it yet either. Everything broke in our Obs instance immediately after the svn update at midnight. I’m still running everything by hand with -dd to figure out what’s going on.
_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

Adam Armstrong

30 June 2018 at 18:08

Umm...

observium-wrapper is a symlink to poller-wrapper.py

lrwxrwxrwx 1 root root 17 Jun 22 2017 observium-wrapper -> poller-wrapper.py

adam.

Joey Stanford

30 June 2018 at 18:06

it seems I was still running poller-wrapper and not the new observium-wrapper …when I did that I got everything back

_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

Joey Stanford

30 June 2018 at 17:51

as a follow on, poller now runs (as does discovery), but there is another process which I haven’t isolated yet which immediately takes the device from online back to offline (in the UI) while leaving status =1.

_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

Joey Stanford

30 June 2018 at 17:28

Hi,

Overnight the update script brought us to 9304 and the schema up to 378. Immediately after, all of our devices when down and alerts went out. The problem was that the poller script SQL call was failing because it was looking for status = 1 and all of our boxes were in status = 0. poller couldn’t find the host even though the hostname matched hostname in devices. I did an “ update devices set status=1 where `disabled`=0; “ and poller started again but I’m sure something else it at play here.

Joey

_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium