Oxidized integration to Librenms

amaizenshtein · 17 September 2017 11:26

Hi Guys,

Please assist, I’ve followed the following link https://techstat.net/how-to-integrate-oxidized-into-librenms/
after trying to activate the service , it gives me the following errors:

[root@dl1-librenms-srv01 ~]# systemctl status oxidized
● oxidized.service - Oxidized - Network Device Configuration Backup Tool
Loaded: loaded (/usr/lib/systemd/system/oxidized.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2017-09-17 10:44:10 UTC; 36min ago
Main PID: 19801 (code=exited, status=1/FAILURE)

Sep 17 10:44:10 dl1-librenms-srv01.pan.local systemd[1]: Started Oxidized - Network Device Configuration Backup Tool.
Sep 17 10:44:10 dl1-librenms-srv01.pan.local systemd[1]: Starting Oxidized - Network Device Configuration Backup Tool…
Sep 17 10:44:10 dl1-librenms-srv01.pan.local oxidized[19801]: A server is already running. Check /root/.config/oxidized/pid
Sep 17 10:44:10 dl1-librenms-srv01.pan.local systemd[1]: oxidized.service: main process exited, code=exited, status=1/FAILURE
Sep 17 10:44:10 dl1-librenms-srv01.pan.local systemd[1]: Unit oxidized.service entered failed state.
Sep 17 10:44:10 dl1-librenms-srv01.pan.local systemd[1]: oxidized.service failed.

laf · 17 September 2017 11:35

The error tells you that a service is already started so either oxidized is already running or something on the same port is.

amaizenshtein · 17 September 2017 11:39

I’m doing this check [root@dl1-librenms-srv01 ~]# ps -A |grep oxidized
don’t see any service running

laf · 17 September 2017 11:49

The oxidized process is called puma. Check what’s running on the port.

amaizenshtein · 17 September 2017 11:52

Checking this one, no puma service [root@dl1-librenms-srv01 bin]# ps -A | grep puma

amaizenshtein · 17 September 2017 12:01

How to move it to Active running?

root@dl1-librenms-srv01 bin]# sudo systemctl status oxidized -l
● oxidized.service - Oxidized - Network Device Configuration Backup Tool
Loaded: loaded (/usr/lib/systemd/system/oxidized.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2017-09-17 11:59:45 UTC; 17s ago
Process: 6126 ExecStart=/usr/local/bin/oxidized (code=exited, status=1/FAILURE)
Main PID: 6126 (code=exited, status=1/FAILURE)

Sep 17 11:59:45 dl1-librenms-srv01.pan.local oxidized[6126]: /usr/local/share/gems/gems/oxidized-0.20.0/lib/oxidized/core.rb:15:in initialize': source returns no usable nodes (Oxidized::Core::NoNodesFound) Sep 17 11:59:45 dl1-librenms-srv01.pan.local oxidized[6126]: from /usr/local/share/gems/gems/oxidized-0.20.0/lib/oxidized/core.rb:4:innew’
Sep 17 11:59:45 dl1-librenms-srv01.pan.local oxidized[6126]: from /usr/local/share/gems/gems/oxidized-0.20.0/lib/oxidized/core.rb:4:in new' Sep 17 11:59:45 dl1-librenms-srv01.pan.local oxidized[6126]: from /usr/local/share/gems/gems/oxidized-0.20.0/lib/oxidized/cli.rb:12:inrun’
Sep 17 11:59:45 dl1-librenms-srv01.pan.local oxidized[6126]: from /usr/local/share/gems/gems/oxidized-0.20.0/bin/oxidized:9:in <top (required)>' Sep 17 11:59:45 dl1-librenms-srv01.pan.local oxidized[6126]: from /usr/local/bin/oxidized:23:inload’
Sep 17 11:59:45 dl1-librenms-srv01.pan.local oxidized[6126]: from /usr/local/bin/oxidized:23:in `'
Sep 17 11:59:45 dl1-librenms-srv01.pan.local systemd[1]: oxidized.service: main process exited, code=exited, status=1/FAILURE
Sep 17 11:59:45 dl1-librenms-srv01.pan.local systemd[1]: Unit oxidized.service entered failed state.
Sep 17 11:59:45 dl1-librenms-srv01.pan.local systemd[1]: oxidized.service failed.

amaizenshtein · 17 September 2017 12:37

Now I’m getting this:

[root@dl1-librenms-srv01 extra]# systemctl status oxidized
● oxidized.service - Oxidized - Network Device Configuration Backup Tool
Loaded: loaded (/usr/lib/systemd/system/oxidized.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2017-09-17 12:35:23 UTC; 18s ago
Process: 25232 ExecStart=/usr/local/bin/oxidized (code=exited, status=1/FAILURE)
Main PID: 25232 (code=exited, status=1/FAILURE)

Sep 17 12:35:23 dl1-librenms-srv01.pan.local oxidized[25232]: /usr/local/share/gems/gems/oxidized-0.20.0/lib/oxidized/core.rb:15:in initialize': source returns no usable nodes...odesFound) Sep 17 12:35:23 dl1-librenms-srv01.pan.local oxidized[25232]: from /usr/local/share/gems/gems/oxidized-0.20.0/lib/oxidized/core.rb:4:innew’
Sep 17 12:35:23 dl1-librenms-srv01.pan.local oxidized[25232]: from /usr/local/share/gems/gems/oxidized-0.20.0/lib/oxidized/core.rb:4:in new' Sep 17 12:35:23 dl1-librenms-srv01.pan.local oxidized[25232]: from /usr/local/share/gems/gems/oxidized-0.20.0/lib/oxidized/cli.rb:12:inrun’
Sep 17 12:35:23 dl1-librenms-srv01.pan.local oxidized[25232]: from /usr/local/share/gems/gems/oxidized-0.20.0/bin/oxidized:9:in <top (required)>' Sep 17 12:35:23 dl1-librenms-srv01.pan.local oxidized[25232]: from /usr/local/bin/oxidized:23:inload’
Sep 17 12:35:23 dl1-librenms-srv01.pan.local oxidized[25232]: from /usr/local/bin/oxidized:23:in `'
Sep 17 12:35:23 dl1-librenms-srv01.pan.local systemd[1]: oxidized.service: main process exited, code=exited, status=1/FAILURE
Sep 17 12:35:23 dl1-librenms-srv01.pan.local systemd[1]: Unit oxidized.service entered failed state.
Sep 17 12:35:23 dl1-librenms-srv01.pan.local systemd[1]: oxidized.service failed.

Gorian · 17 September 2017 18:54

@amaizenshtein - looks like you are running an OS with systemd. You should be able to run ss -plnt to get a list of what ports you are listening on, and what service is listening on them.

amaizenshtein · 17 September 2017 18:55

can you please provide how the config file looks on your side?

amaizenshtein · 17 September 2017 20:29

I succeded to make service running, but now i’m getting different errors:

[root@dl1-librenms-srv01 librenms]# sudo systemctl status oxidized
● oxidized.service - Oxidized - Network Device Configuration Backup Tool
Loaded: loaded (/usr/lib/systemd/system/oxidized.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2017-09-17 20:16:08 UTC; 12min ago
Main PID: 10781 (oxidized)
CGroup: /system.slice/oxidized.service
└─10781 puma 3.10.0 (tcp://127.0.0.1:8888) [/]

Sep 17 20:23:18 dl1-librenms-srv01.pan.local oxidized[10781]: /usr/local/share/gems/gems/rack-1.6.8/lib/rack/urlmap.rb:66:in block in call' Sep 17 20:23:18 dl1-librenms-srv01.pan.local oxidized[10781]: /usr/local/share/gems/gems/rack-1.6.8/lib/rack/urlmap.rb:50:ineach’
Sep 17 20:23:18 dl1-librenms-srv01.pan.local oxidized[10781]: /usr/local/share/gems/gems/rack-1.6.8/lib/rack/urlmap.rb:50:in call' Sep 17 20:23:18 dl1-librenms-srv01.pan.local oxidized[10781]: /usr/local/share/gems/gems/rack-1.6.8/lib/rack/builder.rb:153:incall’
Sep 17 20:23:18 dl1-librenms-srv01.pan.local oxidized[10781]: /usr/local/share/gems/gems/puma-3.10.0/lib/puma/configuration.rb:225:in call' Sep 17 20:23:18 dl1-librenms-srv01.pan.local oxidized[10781]: /usr/local/share/gems/gems/puma-3.10.0/lib/puma/server.rb:605:inhandle_request’
Sep 17 20:23:18 dl1-librenms-srv01.pan.local oxidized[10781]: /usr/local/share/gems/gems/puma-3.10.0/lib/puma/server.rb:437:in process_client' Sep 17 20:23:18 dl1-librenms-srv01.pan.local oxidized[10781]: /usr/local/share/gems/gems/puma-3.10.0/lib/puma/server.rb:301:inblock in run’
Sep 17 20:23:18 dl1-librenms-srv01.pan.local oxidized[10781]: /usr/local/share/gems/gems/puma-3.10.0/lib/puma/thread_pool.rb:120:in call' Sep 17 20:23:18 dl1-librenms-srv01.pan.local oxidized[10781]: /usr/local/share/gems/gems/puma-3.10.0/lib/puma/thread_pool.rb:120:inblock in spawn_thread’

amaizenshtein · 18 September 2017 05:51

Please advise how to fix these errors:

[root@dl1-librenms-srv01 ~]# sudo systemctl status oxidized -l
● oxidized.service - Oxidized - Network Device Configuration Backup Tool
   Loaded: loaded (/usr/lib/systemd/system/oxidized.service; enabled; vendor preset: disabled)
   Active: active (running) since Sun 2017-09-17 20:16:08 UTC; 9h ago
 Main PID: 10781 (oxidized)
   CGroup: /system.slice/oxidized.service
           └─10781 puma 3.10.0 (tcp://127.0.0.1:8888) [/

Sep 18 05:36:37 dl1-librenms-srv01.pan.local oxidized[10781]: /usr/local/share/gems/gems/rack-1.6.8/lib/rack/urlmap.rb:66:in `block in call'
Sep 18 05:36:37 dl1-librenms-srv01.pan.local oxidized[10781]: /usr/local/share/gems/gems/rack-1.6.8/lib/rack/urlmap.rb:50:in `each'
Sep 18 05:36:37 dl1-librenms-srv01.pan.local oxidized[10781]: /usr/local/share/gems/gems/rack-1.6.8/lib/rack/urlmap.rb:50:in `call'
Sep 18 05:36:37 dl1-librenms-srv01.pan.local oxidized[10781]: /usr/local/share/gems/gems/rack-1.6.8/lib/rack/builder.rb:153:in `call'
Sep 18 05:36:37 dl1-librenms-srv01.pan.local oxidized[10781]: /usr/local/share/gems/gems/puma-3.10.0/lib/puma/configuration.rb:225:in `call'
Sep 18 05:36:37 dl1-librenms-srv01.pan.local oxidized[10781]: /usr/local/share/gems/gems/puma-3.10.0/lib/puma/server.rb:605:in `handle_request'
Sep 18 05:36:37 dl1-librenms-srv01.pan.local oxidized[10781]: /usr/local/share/gems/gems/puma-3.10.0/lib/puma/server.rb:437:in `process_client'
Sep 18 05:36:37 dl1-librenms-srv01.pan.local oxidized[10781]: /usr/local/share/gems/gems/puma-3.10.0/lib/puma/server.rb:301:in `block in run'
Sep 18 05:36:37 dl1-librenms-srv01.pan.local oxidized[10781]: /usr/local/share/gems/gems/puma-3.10.0/lib/puma/thread_pool.rb:120:in `call'
Sep 18 05:36:37 dl1-librenms-srv01.pan.local oxidized[10781]: /usr/local/share/gems/gems/puma-3.10.0/lib/puma/thread_pool.rb:120:in `block in spawn_thread'

laf · 18 September 2017 17:08

I don’t see an error.

Sachin_Sharma · 24 November 2018 14:52

Hi
Im getting this error please help me to resolve this

root@airjaldi:~/.config/oxidized# sudo systemctl status oxidized -l
● oxidized.service - Oxidized - Network Device Configuration Backup Tool
Loaded: loaded (/lib/systemd/system/oxidized.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Sat 2018-11-24 19:16:53 IST; 1h 3min ago
Process: 4662 ExecStart=/usr/local/bin/oxidized (code=exited, status=0/SUCCESS)
Main PID: 4662 (code=exited, status=0/SUCCESS)

Nov 24 19:16:53 airjaldi systemd[1]: Started Oxidized - Network Device Configuration Backup Tool.
Nov 24 19:16:53 airjaldi oxidized[4662]: I, [2018-11-24T19:16:53.778445 #4662] INFO – : Oxidized starting, running as pid 4662
Nov 24 19:16:53 airjaldi oxidized[4662]: I, [2018-11-24T19:16:53.785062 #4662] INFO – : lib/oxidized/nodes.rb: Loading nodes
Nov 24 19:16:53 airjaldi oxidized[4662]: F, [2018-11-24T19:16:53.786966 #4662] FATAL – : Oxidized crashed, crashfile written in /root
Nov 24 19:16:53 airjaldi oxidized[4662]: No such file or directory @ rb_sysopen - /root/.config/oxidized/router.db
lines 1-11/11 (END)

Sachin_Sharma · 24 November 2018 16:31

now getting this

PLEASE Help Me.

root@airjaldi:~/.config/oxidized# sudo systemctl status oxidized
● oxidized.service - Oxidized - Network Device Configuration Backup Tool
Loaded: loaded (/lib/systemd/system/oxidized.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Sat 2018-11-24 21:36:24 IST; 24min ago
Process: 30509 ExecStart=/usr/local/bin/oxidized (code=exited, status=0/SUCCESS)
Main PID: 30509 (code=exited, status=0/SUCCESS)

Nov 24 21:36:23 airjaldi systemd[1]: Started Oxidized - Network Device Configuration Backup Tool.
Nov 24 21:36:24 airjaldi oxidized[30509]: edit ~/.config/oxidized/config
root@airjaldi:~/.config/oxidized#

laf · 3 December 2018 21:15

The clue is in both of those debug outputs.

The first one you don’t have the specified router.db file and the second you now need to edit the config file it’s pointed out.

Kevin_Krumm · 6 February 2020 22:29

A post was split to a new topic: Help the service