the thing is I have to keep reverting to a snapshot because it keeps breaking with no change that I can tell when it does break. The closest thing i can find is the error the two ppl get in the bottom links:
[FAIL] Discovery has not completed in the last 24 hours, check the cron job
the fixes dont seem to help when it breaks hence the reverting to old snapshots.
my cron is as follows and works until the second week mark.
[ @monitoring ~]$ id librenms
uid=996(librenms) gid=994(librenms) groups=994(librenms),48(apache)
[@monitoring ~]$ cat /etc/cron.d/librenms
Using this cron file requires an additional user on your system, please see install docs.
All i see in any log are that snmp connections stop to the local host at the time it all fails but snmpd is running fine space is fine sql is fine, reboot of host and restart of all the applicable services does not help. Not sure if i need to register the product? and some sort of license expires? any ideas ?
Thank you for the reply!
just did and it got 1.33
Im curious since this actualy broke last night and im guessing this daily.sh runs nightly my build would have been up to date last night would it not ?
also you may need to this If you have devices suddenly showing as down, you need to set $config[‘fping’] = ‘/usr/sbin/fping’; or $config[‘fping’] = ‘/usr/bin/fping’; in your config.php and it will start working again. We fixed a bug where fping always showed up even if the command failed
Thank you again for the responses. Il add the fping change since i do recall seeing that somewhere while troubleshooting last.Il update with more info as it rolles in
Mr Krumm, i have a question. fping config change, does that only go in a certain section of the ~/config.php ?
i attempted that in an early troubleshooting session when it was down – still up but i got a config error in the gui stating the line after the fping in the config. I commented it out and it went away. Does it need its own section or does it belong in an earlier section ?