Something occurred yesterday and I will be honest I am not sure what but now my CPU on the Libre Server is WAY up. I only graph like 4 things, the server itself, a Palo Alto Firewall and 2 Extreme Networks Switches. The Palo Alto seems normal however the CPU spike is also affecting the Extreme switches. So server CPU spike and Extreme Switch CPU spike and if you look at the graphs of when this started they match each other. I have been banging my head to try and figure out what caused this. In the logs it appears the discovery process keeps running over and over and over on the same devices which I don’t think is normal? I even went in and disable the discovery process in the gui and I still see the logs being populated with discovery events. Any help here would be great as the same thing is also happening on another Libre instance I host at another site.
Ok well now 10 minutes after disabling discovery in the GUI it finally stopped discovering over and over and over And the CPU has settled WAY down. So something is going on with discovery being stuck. Any tips on how to resolve this? Oh rebooting literally everything doesn’t fix it either. It just starts back up
I ran the update and then turned discovery back on. The CPU is still not going backup however discovery doesn’t appear to be running? I have been watching the logs for it to fire but no go. I also did a manual discover on a few devices and the device is not being updated for “last discovered”. That entry doesn’t exist on the main page of each device. So not really sure what is going on? Perhaps reboot the box or maybe some other ideas? Oh also in the poller status is just says 2 devices pending forever with no change. See the newest validate below:
[OK] Composer Version: 2.9.4
[OK] Dependencies up-to-date.
[OK] Database Connected
[OK] Database Schema is current
[OK] SQL Server meets minimum requirements
[OK] lower_case_table_names is enabled
[OK] MySQL engine is optimal
[OK] Database and column collations are correct
[OK] Database schema correct
[OK] MySQL and PHP time match
[OK] Active pollers found
[OK] Dispatcher Service is enabled
[OK] Locks are functional
[OK] Python wrapper cron entry is not present
[OK] Redis is functional
[OK] All 445 RRD files have the correct step.
[OK] rrdtool version ok
[OK] Connected to rrdcached
Understood on the 6hrs deal however I should be able to do a manual discover on a device and then have it populate the “last discovered” field on the homepage of each device. Well a manual discover through the gui appears to do nothing and also the “last discovered” field literally disappeared so there is no “last discovered” anymore. So to your point it may work fine in 6hrs TBD but would appear I cannot fire a manual “rediscover device” I mean I have tried but nothing happens. Hopefully that makes sense. Thank you
Good morning - I rebooted after your last message and let it cook overnight and all is well! The scheduled/automated discovery works and the manual discover works. Not sure what was baked inside of “a00c47d08” but it seems to have fixed me up! Thanks so much!!
