(solved) Oxidized service not working, wrong key

Help Oxidized
1

Hi,

After this weekend oxidized service doesn’t start, I suspect that the ./daily might have bricked it.

sudo systemctl status oxidized.service
● oxidized.service - Oxidized - Network Device Configuration Backup Tool
   Loaded: loaded (/lib/systemd/system/oxidized.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since mån 2019-02-18 08:01:40 CET; 17min ago
  Process: 2806 ExecStart=/usr/local/bin/oxidized (code=exited, status=0/SUCCESS)
 Main PID: 2806 (code=exited, status=0/SUCCESS)

feb 18 08:01:40 NAME systemd[1]: Started Oxidized - Network Device Configuration Backup Tool.
feb 18 08:01:40 NAME oxidized[2806]: I, [2019-02-18T08:01:40.863048 #2806]  INFO -- : Oxidized starting, running as pid 2806
feb 18 08:01:40 NAME oxidized[2806]: I, [2019-02-18T08:01:40.893439 #2806]  INFO -- : lib/oxidized/nodes.rb: Loading nodes
feb 18 08:01:40 NAME oxidized[2806]: F, [2019-02-18T08:01:40.957343 #2806] FATAL -- : Oxidized crashed, crashfile written in /home/oxidized/.config/oxidized/crash
feb 18 08:01:40 NAME oxidized[2806]: 765: unexpected token at '<!doctype html>
feb 18 08:01:40 NAME oxidized[2806]: <html lang="en">
feb 18 08:01:40 NAME oxidized[2806]:     <head>
feb 18 08:01:40 NAME oxidized[2806]:         <title>Error</title>
feb 18 08:01:40 NAME oxidized[2806]:         <meta charset="utf-8">
feb 18 08:01:40 NAME oxidized[2806]:         <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">

Looking at the crash dump I’m getting a error page with the below error.

765: unexpected token at '<!doctype html>

I´ve verified the X-auth token and it´s okay, anyone has any ideas?

2

Validate:
sudo -u librenms ./validate.php
====================================
Component | Version
--------- | -------
LibreNMS | 1.48.1-64-g9dba9f6
DB Schema | 2019_01_16_195644_add_vrf_id_and_bgpLocalAs (131)
PHP | 7.2.14-1+ubuntu16.04.1+deb.sury.org+1
MySQL | 10.0.36-MariaDB-0ubuntu0.16.04.1
RRDTool | 1.5.5
SNMP | NET-SNMP 5.7.3
====================================

[OK]    Composer Version: 1.8.4
[OK]    Dependencies up-to-date.
[OK]    Database connection successful
[OK]    Database schema correct
3

So I managed to solve the issue.

For some reason the old key stopped working, I created a new one and it worked. This can be closed.

4

Are you referring to API token under API Access on librenms?

5

Found my problem im hosting to “websites” libernms and Netbox on same vm. netbox uses port 80 librenms uses port 8080.

In oxidized config I had to change

url: http://localhost:/api/v0/oxidized   to    url: http://localhost:8080/api/v0/oxidized