Hi, I tried running the config through the yaml validator until it passed and even then I received the same error. The purpose of me reaching out (and my hope), was to gain an understanding of what needs to be changed in the yaml config to get this running.
I’ve been comparing my config with a bunch of other examples online and I can’t grasp how to properly configure it as everyone is doing it differently.
I think you might need the hyphens at the top of the config file.
Username and password is indeed the ssh or telnet credentials
For the LibreNMS integration, you want to change the source to http and provide the correct URL and create an administrative user in LibreNMS e.g “oxidized” and create a auth token through the LibreNMS GUI, paste that into your config.
Jul 25 11:32:00 librenms systemd[1]: Started Oxidized - Network Device Configuration Backup Tool.
Jul 25 11:32:00 librenms systemd[1]: Starting Oxidized - Network Device Configuration Backup Tool…
Jul 25 11:32:00 librenms oxidized[18481]: Error loading config: (): found character that cannot start any token while scanning for the next token at line 3 column 11
Jul 25 11:32:42 librenms systemd[1]: Started Oxidized - Network Device Configuration Backup Tool.
Jul 25 11:32:42 librenms systemd[1]: Starting Oxidized - Network Device Configuration Backup Tool…
Jul 25 11:32:42 librenms oxidized[18552]: Error loading config: (): found character that cannot start any token while scanning for the next token at line 3 column 11
Jul 25 11:40:43 librenms systemd[1]: Started Oxidized - Network Device Configuration Backup Tool.
Jul 25 11:40:43 librenms systemd[1]: Starting Oxidized - Network Device Configuration Backup Tool…
Jul 25 11:40:43 librenms oxidized[19275]: Error loading config: (): found character that cannot start any token while scanning for the next token at line 3 column 11
After you edited it, is the yaml validators still happy with it? Make sure there are no Tabs and that you are using white spaces, also ensure no comments like the original post e.g “# Is this the username and password for my network devices”
Also are you using plaintext for the username and password, i.e not using $ADMIN and $PASSWORD variables
Yaml validator does not pass, it wants me to remove the variables for the device (name, model, username, password…)
I’ll double check tabs, but I am pretty sure I did not use any tabs
I removed comments and “variables” were replaced with plain text in my running config.
I literally copied your config and adjusted it to fit my environment this last time I tried to get it to run.
Here is my current YAML config:
Oxidized can load config from a variety of locations, I’d check you don’t have more than one. Look at /etc/oxidized/config and ~/.config/oxidized/config
Working through this using multiple sources I think I was able to make some progress, now I am getting this error.
source returns no usable nodes
/usr/local/share/gems/gems/oxidized-0.24.0/lib/oxidized/core.rb:15:in initialize': source returns no usable nodes (Oxidized::Core::NoNodesFound) from /usr/local/share/gems/gems/oxidized-0.24.0/lib/oxidized/core.rb:4:innew’
from /usr/local/share/gems/gems/oxidized-0.24.0/lib/oxidized/core.rb:4:in new' from /usr/local/share/gems/gems/oxidized-0.24.0/lib/oxidized/cli.rb:12:inrun’
from /usr/local/share/gems/gems/oxidized-0.24.0/bin/oxidized:8:in <top (required)>' from /usr/local/bin/oxidized:23:inload’
from /usr/local/bin/oxidized:23:in `’
Here is my updated config (passes YAML validation tool in librenms):
I was able to identify the discrepancies in my config file thanks to some help from the github: https://github.com/ytti/oxidized/issues/1469 and some trial and error testing. I now have a working instance of Oxidized and the web interface works. Though I still can’t pull the configs from the LibreNMS Web UI, I was able to get Oxidized working.