Follow-up to topic: Enabling Proxmox app
I’m in a similar state, where I (believe) I’ve followed the instructions:
added line in config.php
enabled “Unix Agent” and “Application” modules
enabled “Proxmox” app
Installed agent on my Proxmox server and verified it returns valid data by “telnet 192.168.10.7 6556”
other snmp data on that server is working just fine
However, the GUI App page still shows “? Proxmox” with no data from the system.
Running a docker install with the latest version.
Edit: If I force a Poller run with ebug, I can see it populating the VM’s and they show up on the App now - but the graphs all end up with rrd errors.
Qube
15 February 2022 23:08
2
I had the same problem recently and figured out that the default access rules in my snmpd configuration
blocked access to the extension subtree.
So I enabled read only access to .1 and it worked now…
Can you give me an example?
Qube
15 February 2022 23:32
4
This is a part of my snmpd,conf file (on the proxmox host):
###########################################################################
#SECTION: Access Control Setup
#This section defines who is allowed to talk to your running
snmp agent.
#Views
#arguments viewname included [oid]
#system + hrSystem groups only
#view systemonly included .1.3.6.1.2.1.1
#view systemonly included .1.3.6.1.2.1.25.1
view systemonly included .1
#rocommunity: a SNMPv1/SNMPv2c read-only access community name
#arguments: community [default|hostname|network/bits] [oid | -V view]
#Read-only access to everyone to the systemonly view
rocommunity public default -V systemonly
rocommunity6 public default -V systemonly
…
In the default installation these rules are enabled:
view systemonly included .1.3.6.1.2.1.1
view systemonly included .1.3.6.1.2.1.25.1
Which limits the access to the two MIB Subtrees - they not include the one needed for the extensions
I replaced them with:
view systemonly included .1
which gives full read access to the complete MIB tree.
DIdn’t seem to have any impact. I’m still seeing this when I try and display the graphs:
Qube
16 February 2022 06:33
6
Have you restarted the snmp daemon after changing the conf file?
Yea, and the odd thing is that if I look at the poller output in the debug window I can clearly see the VM stats being returned. I even tried deleting and re-adding the proxmox server.
So - I ended up creating a new librenms server, using native install instead of docker - that seems to work just fine…
Qube
17 February 2022 06:48
9
Good to hear that!!
I frankly had no idea anymore what could went wrong in your first install…
system
Closed
18 May 2022 06:48
10
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.