LibreNMS Inventory Not Working

Hi

I have 2 LibreNMS systems running, that are not connected. Each NMS polls less than 40 devices via SNMP. Both systems run on Raspberry Pi 5s with 8GB of RAM. Both systems rarely go above 20% load. I’ve set the poller workers to 10 to reduce the load on the Pis.

On both systems, on LibreNMS, if I visit the overview/inventory page the systems say “No results found”. Both systems have always said this from the day they were built, several months ago. If I open a device up, on LibreNMS, and check its inventory tab I see CPUs and network interfaces listed, but no serial numbers. On the device overview page, for example, on all of my switches I see the model number & serial number of the devices. All devices have been auto-discovered by LirbeNMS and when snmp is used I see lots of details on each device’s pages. I would like to use the inventory function on LibreNMS. Inventory is enabled and I’ve also issued a “lnms config:get enable_inventory” on the cli. Other parts of LibreNMS seem to be fine, including eventlog, syslog, email alerting, graphing etc. Are them some additional steps I need to perform to get inventory to work? I’ve reviewed the docs and I can’t see what I’m missing. I do have a scheduler issue, mentioned below, but this doesn’t seem to have broken other parts of LibreNMS. I’ve tried both FireFox and Chrome browsers, both have the same issue.

The output of ./validate.php:

Component Version
LibreNMS 24.7.0-23-g9f4e6cbf0 (2024-07-26T15:09:38+01:00)
DB Schema 2024_07_19_120719_update_ports_stack_table (296)
PHP 8.2.20
Python 3.11.2
Database MariaDB 10.11.6-MariaDB-0+deb12u1
RRDTool 1.7.2
SNMP 5.9.3
===========================================

[OK] Composer Version: 2.7.7
[OK] Dependencies up-to-date.
[OK] Database connection successful
[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 unavailable
[OK] rrdtool version ok
[OK] Connected to rrdcached
[FAIL] Scheduler is not running
[FIX]:
sudo cp /opt/librenms/dist/librenms-scheduler.service /opt/librenms/dist/librenms-scheduler.timer /etc/systemd/system/
sudo systemctl enable librenms-scheduler.timer
sudo systemctl start librenms-scheduler.timer

The scheduler fix above doesn’t fix the issue above but the Librenms items in my crontab appear to be working ok. Daily.sh runs correctly etc and autodiscovery of devices works ok.

My /etc/cron.d/librenms contains:


*/6 * * * * librenms /opt/librenms/cronic /opt/librenms/discovery-wrapper.py 1
*/5 * * * * librenms /opt/librenms/discovery.php -h new >> /dev/null 2>&1

          • librenms /opt/librenms/alerts.php >> /dev/null 2>&1

*/5 * * * * librenms /opt/librenms/poll-billing.php >> /dev/null 2>&1
01 * * * * librenms /opt/librenms/billing-calculate.php >> /dev/null 2>&1
*/5 * * * * librenms /opt/librenms/check-services.php >> /dev/null 2>&1

51 4 * * * librenms 6 /opt/librenms/daily.sh >> /dev/null 2>&1

12 14 * * * root /etc/control/snmp_scan_wrapper.sh >> /dev/null 2>&1

Thanks!

Out of interest I added a Cisco C3850 switch to a network monitored by one of the LibreNMS devices. After running an snmp poll the LibreNMS inventory web page shows inventory from the newly added switch. I guess inventory only supports some devices. I’m surprised the other network equipment I have isn’t able to provide an inventory to LibreNMS but it doesn’t look like I have a fault on the LibreNMS inventory system.

All I needed to do to pull the inventory from the Cisco was add the line “snmp-server community public RO” to the Cisco’s config (as well as setting an ip address etc). This was on an offline system, so I didn’t bother with snmp v3 for testing.

FWIW, I have a lot of stuff in my network and the only thing that produces “inventory” is my Cisco stack.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.