I want to use oxidize to back up my devices. Getting the following error:
[@librenms ~]$ oxidized
I, [2018-08-01T08:54:00.085708 #26156] INFO – : Oxidized starting, running as pid 26156
I, [2018-08-01T08:54:00.086502 #26156] INFO – : lib/oxidized/nodes.rb: Loading nodes
E, [2018-08-01T08:54:00.088820 #26156] ERROR – : node {:name=>“x.x.x.x”, :model=>nil} raised Oxidized::ModelNotFound with message ‘cisco not found for node x.x.x.x’
I, [2018-08-01T08:54:00.088883 #26156] INFO – : lib/oxidized/nodes.rb: Loaded 0 nodes
F, [2018-08-01T08:54:00.088953 #26156] FATAL – : Oxidized crashed, crashfile written in /opt/librenms/.config/oxidized/crash
source returns no usable nodes
Can someone point me to the correct direction on what I’m doing wrong please?
You’ve got no nodes being loaded. The fact a cisco not found for node message is showing, seems like you’ve got the wrong os allocated to at least one node or the only node. You need to match the model/os to the ones Oxidized supports. Have a look at the docs in oxidized for this.
I was able to get the nodes to automatically load from libre. I’m getting a connection error. Not sure if is due to a credential issue or a misconfig. My devices ask for an enable password every time so not sure if that’s an issue.
[librenms@librenms ~]$ oxidized
Connection refused - connect(2)
/usr/share/ruby/net/http.rb:878:in initialize': Connection refused - connect(2) (Errno::ECONNREFUSED) from /usr/share/ruby/net/http.rb:878:inopen’
from /usr/share/ruby/net/http.rb:878:in block in connect' from /usr/share/ruby/timeout.rb:52:intimeout’
from /usr/share/ruby/net/http.rb:877:in connect' from /usr/share/ruby/net/http.rb:862:indo_start’
from /usr/share/ruby/net/http.rb:851:in start' from /usr/share/ruby/net/http.rb:1373:inrequest’
from /usr/local/share/gems/gems/oxidized-0.24.0/lib/oxidized/source/http.rb:40:in load' from /usr/local/share/gems/gems/oxidized-0.24.0/lib/oxidized/nodes.rb:15:inblock in load’
from /usr/local/share/gems/gems/oxidized-0.24.0/lib/oxidized/nodes.rb:128:in synchronize' from /usr/local/share/gems/gems/oxidized-0.24.0/lib/oxidized/nodes.rb:128:inwith_lock’
from /usr/local/share/gems/gems/oxidized-0.24.0/lib/oxidized/nodes.rb:10:in load' from /usr/local/share/gems/gems/oxidized-0.24.0/lib/oxidized/nodes.rb:123:ininitialize’
from /usr/local/share/gems/gems/oxidized-0.24.0/lib/oxidized/core.rb:14:in new' from /usr/local/share/gems/gems/oxidized-0.24.0/lib/oxidized/core.rb:14:ininitialize’
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/core.rb:4:innew’
from /usr/local/share/gems/gems/oxidized-0.24.0/lib/oxidized/cli.rb:12:in run' from /usr/local/share/gems/gems/oxidized-0.24.0/bin/oxidized:8:in<top (required)>’
from /usr/local/bin/oxidized:23:in load' from /usr/local/bin/oxidized:23:in’
The issue I was seeing was due to dependencies missing. I got it all squared away. The issue I see now is that it’s not pulling the actual start-up config or running-config from my cisco devices. Any idea why it’s not? I checked ./scripts/syslog-notify-oxidized.php and all seems to be as per the document.
Usually timeout, if it takes a while to run show run on this device or it’s a distant device so latency is high try increasing the timeout in oxidized.
Otherwise enable oxidized debugging and pastebin the output.
Hey Laf, thanks for the support. After further debugging it turns out to be a permissions issue on my end. I have it all squared away and Oxidized is capturing and displaying the full running-config. Issue is resolved.