Agents on linux and windows doesnt work and "unable to parse drbd"

Started by matikken, August 11, 2021, 09:07:01 PM

Previous topic - Next topic

matikken

Hello
I tried to install linux agents on a few (fresh) linux distros - and everywhere i got errors with "unable to parse drbd".
Arbitrary command execution disabled
2021.08.11 18:42:34.301 *I* [linux              ] Unable to parse /proc/drbd, DRBD data collector will not start
2021.08.11 18:42:34.302 *I* [subagents          ] Subagent "Linux" (linux.nsm) loaded successfully (version 3.9.176)
2021.08.11 18:42:34.302 *I* [                   ] System hardware ID is 209593F17FA1A65E2A0CAF94C9C444A3
2021.08.11 18:42:35.304 *I* [                   ] Control connector is disabled
2021.08.11 18:42:35.305 *I* [                   ] Listening on socket 0.0.0.0:4700
2021.08.11 18:42:35.305 *I* [                   ] Listening on socket :::4700
2021.08.11 18:42:36.306 *I* [                   ] NetXMS Agent started


netXMS server (also fresh install) shows always "isAgent No" on such devices with installed agents and status of all devices interface are always "unknown".
On fresh windows 10 client installation (virtual machines) agent instalation results in a lot of library errors. So linux agents doesnt worsk, windows agents doesnt works....

In netXMS' documentation (official netxms-admin.pdf) there is NO informations regarding to typical errors/troouble shootings.

I would like to mention that i dont have any connection issues between xms server, and agents (pings, port 4700 etc are ok, no firewall between them. windows firewall turned off, no iptables on linux).
Config for agents is fromxms  manual mentioned above:
# Log File
LogFile=/var/log/nxagentd

# IP white list, can contain multiple records separated by comma.
# CIDR notation supported for subnets.
MasterServers= my IP address of XMS server


Do you have also problems with linux and windows agents installed  from scratch?






Filipp Sudanov

DRBD collector is for https://en.wikipedia.org/wiki/Distributed_Replicated_Block_Device , this may not be present on a system. So this is not an error that would be preventing server connecting to agent.

check output of
netstat -lptn
on agent's system. It should show something like
tcp        0      0 0.0.0.0:4700            0.0.0.0:*               LISTEN      6347/nxagentd       
that would mean that NetXMS agent is listening on port 4700.

From another machine you can try
telnet agent_machine_ip 4700
to see if it's possible to establisth network connection to agent.

In netxms console try right-clicking the node and performing Configuration Poll (full).