The debug info I get is as follows:
In the top menu area, Overview/graph etc (unsure if these are at all related to the problem): Warning : count(): Parameter must be an array or an object that implements Countable in /opt/librenms/includes/html/pages/device.inc.php on line 146 (this message is displayed two times) Warning : in_array() expects parameter 2 to be array, null given in /opt/librenms/includes/html/pages/device.inc.php on line 379
This message is shown in the area where the actual configuration should be visible: Warning : file_get_contents(http://10.9.1.14:8888/node/fetch/-------/10.19.6.4): failed to open stream: HTTP request failed! HTTP/1.0 500 Internal Server Error in /opt/librenms/includes/html/pages/device/showconfig.inc.php on line 225
Hmm, I think the problem is that the device names does not match in LibreNMS and Oxidized, I’ve added the devices through IP addresses in Libre, but the devices seem to be the hostnames in the Oxidized server (I personally have not setup the Oxidized server). I can confirm this via this simple test:
This is a little unfortunate, since it is a bit of a bother to add the devices via hostnames in LibreNMS for me. Sure I can add the devices in the hostfile of the LibreNMS server, but that is a manual task which easily can be messed up. And I’ve no other easy way to add the device through hostnames. Maybe I need to consider feeding Oxidized from LibreNMS.
@Chas You suggested the right thing for me to start figuring things out, so thank you!
Already doing the force ip to sysnem for better understanding which device it actually is in the webinterface, will try and turn it off to see if anything changes. And report back.
Although i think sysname and hostname are two different things.
Disabling $config['force_ip_to_sysname'] = true; did not solve my problem.
Removing a device from LibreNMS (IP address added), and adding it via the actual hostname of the device (putting the hostname to IP mapping in the hostfile on the LibreNMS server first) did fix the problem.
Actually had this same problem when i tried to integrate Graylog.
Hi @Tobias_Larsson we are experiencing this now, unsure if it related, but it seems that when the device attribute gets into the database with false the logic it is not working as it should
So if you delete the entries in the database the tab for config starts showing again in the devices.
DELETE FROM devices_attribs WHERE attrib_type=‘override_Oxidized_disable’ AND attrib_value=‘false’;
Okay, thanks for adding to the conversation, I havent had any more time to put into the NMS the last few months, but I think I’ll be setting another server up at the start of next year, Ill be sure to keep this in mind.
