In early January 2019 I inherited a CentOS 7 server running librenms for network monitoring and oxidized for switch config backups. All seemed well until Feb. 5, when oxidized stoped working I had not made any changes in the interim, but since have only updated the server (monthly) with CentOS system updates. We weren’t making any changes to the switch configs so fixing was on a back burner, but now I need to get it working. There seem to be several different problems reported in the oxidized log files, so I’m not sure where to start. Running validate.php on the server comes back with everything ok, but says the “install is more than 24 hours out of date, last updated 23 June 2019”. When I run the daily.sh script I get no errors, but running validate again still says the install was last updated 23 June 2019. librenms appears to be otherwise working fine, though.
I copied the oxidized config file into the librenms Validate YAML screen, and I get this message:
Tags support is not enabled. Enable the “Yaml::PARSE_CUSTOM_TAGS” flag to use “!ruby/regexp” at line 11 (near “prompt: !ruby/regexp /^([\w.@-]+[#>]\s?)$/”).
Oxidized is actually standalone software it just happens to have nice integration with librenms so unfortunately you won’t gain much from running validate etc
What do your oxidized service logs say, or your log file ?
is oxidizied web working and just the fetching of config from devices failing?
What version are you running ?
gem list | grep oxidized
This is similar to the error I got when validating the config file, so I edited the config file and added the line that the validate said I needed, right before line 11:
Yaml: PARSE_CUSTOM_TAGS
This did not fix the problem, but I think I’ll pursue this a little further before reinstalling.
Personally I’d recommend you install oxidized on a dev box so you understand how it works, and then from that you’ll be able to fix your prod box.
Have a look at the oxidized github page. It has quite extensive docs. Secondly there’s a few good guides on google for installing Oxidized.
My main tip would be instead of running oxidized with systemctl, start the daemon manually with verbose mode configured. It should give more debug for why it’s failing.
I no longer use oxidized (in a different job), but feel free to update here how you get on and I’ll see if I can help.
Thanks, that seems like a good suggenstion. I have poked around some on the server it’s supposedly installed on, and running gem list does not show that oxidized is installed. Running gem install oxidized, returns the error
ERROR: Error installing oxidized
net-ssh requires Ruby version >= 2.2.6.
When I run yum list ruby, it shows
Installed Packages
ruby.x86_64 2.0.0.648-35.el7,6
and does not show any available packages. I tried removing ruby and reinstalling, but got the same version. This is running on a VMware guest, so I’m going to go back to the snapshot I took this morning before messing with ruby, and setup a clean guest to try the install like you suggest.
I have built a new CentOS7 guest and installed the packages per the oxidized github page, down to the Running with Docker section. I don’t have any of that stuff installed at this point, no docker or git command on my server, and the instructions did not say anything about installing them. yum list docker does show it’s available to install, but the version (2:1.13.1-96.gitb2f74b2,el7.centos) is nothing like the minimum required version listed in the installation instrutctions (17.05.0-ce or higher). Do I need to find that version of docker? Do I even need to run with docker or is this optional?
