I’ve got Oxidized and LibreNMS installed on the same server. Oxidized is successfully pulling configs and these are viewable in the Oxidized web UI and via the API, complete with the ability to diff the versions and so on. This suggests to me that the Oxidized side is correctly configured.
When I go to the configs page on LibreNMS and click “Show version” or “Show diff”, the page just reloads without giving me any errors or the configs. There are no errors in the browser console and my ./validate.php has no errors (though my chowns seem to change fairly regularly causing a fail, though fixing these doesn’t have any effect on oxidized). There are also no errors in the Apache log.
When I click the refresh button on LibreNMS, Oxidized does cause the device to fetch new configs, so the API integration is clearly working, but why I can’t see the configs, I don’t know.
Screenshot of all I have on my config screen. This doesn’t change no matter what button I press.
I couldn’t upload this in the original post because my account is new, but here is the Oxidized integration settings. I don’t really want to feed data back into Oxidized since my use case is small enough to be able to use a routers.db file.
So it really should be coming up in either root’s gem list or oxidized’s, since those are the only two accounts I used in setup.
I should’ve mentioned that I’m on CentOS 7.7.1908 as well, though I had the same problem when I installed it in a test environment running CentOS 7.6.1810.
Hmm i’m pretty sure you should see something there, but im not too great with ruby.
I saw on an oxidized github issue where someone couldn’t show diffs and show ver from librenms because they were missing gem packages, so that might relate to this somehow.
I would try gem install oxidized oxidized-web again, does it say its installed?
I just realised I needed to do the scl enable rh-ruby23 bash command and that dropped me to the correct version of Ruby which shows oxidized as installed.
When I installed oxidized, I had some issues daemonising it because of this and the workaround I found for it was to set the following environment variable LD_LIBRARY_PATH=/opt/rh/rh-ruby23/root/usr/local/lib64:/opt/rh/rh-ruby23/root/usr/lib64
Perhaps I should be symlinking /usr/bin/ruby to the Ruby 2.3 version I’m using for oxidized?
Tried the symlink trick but no luck, still won’t load my configs.
gem install lets me install oxidized even though it appears in the list now (with the correct scl command). Restarted httpd and oxidized after doing the below as well but no dice.
[oxidized@epicnetmon01v ~]# gem install oxidized
Successfully installed oxidized-0.26.3
Parsing documentation for oxidized-0.26.3
Done installing documentation for oxidized after 34 seconds
1 gem installed
[oxidized@epicnetmon01v ~]# gem install oxidized-web
Successfully installed oxidized-web-0.13.1
Parsing documentation for oxidized-web-0.13.1
Done installing documentation for oxidized-web after 0 seconds
1 gem installed
I am experiencing the same issue except there are a few differences. In my case the config file trying to be displayed is greater than 4M. All the other devices I am collecting configs for are collecting fine but their sizes are 29K or less. Also, the banner I see is different since this device was discovered using ./snmp-scan -P. If I try to delete this device LibreNMS fails to remove it from the system. Below is the output I am see when trying to navigate from the Availability map.
Juniper MX480 JD_router
System Name
JD_router
IP Address
10.13.0.5
Hardware
Juniper MX480 Midplane Internet Backbone Router
Operating System
Juniper JunOS 12.3R6.6
Serial
JN12FE345ABC
Object ID
.1.3.6.1.4.1.2636.1.1.1.2.25
Contact
John Doe
Device Added
5 days 16 hours 14 minutes 28 seconds ago
Last Discovered
2 hours 23 minutes 30 seconds ago
Uptime
154 days 21 hours 36 minutes 47 seconds
Location
ABC C46
Lat / Lng
N/A
View Overall Traffic
I changed the .rb file to pull a smaller portion of the config and this seems to work. It seems that something about large configuration files causes display issues in LibreNMS. Again, I can view the full configuration file from Oxidized web interface. Are there any timers that might be getting exceeded causing this failure to display the 4M file?
