NetXMS Support Forum

Hello,

I did upgrade yesterday netxms to 3.6.252. After upgrade, I started seeing some problems with getting configuration from agents behind proxy agent.

I do get error in configuration poll Cannot connect to NetXMS agent (Connection broken) and in agent output with debug lvl 9 on windows I see

2020.11.24 08:25:25.715 *D* [comm.cs.3          ] Message dump:
  ** 000000 | 00 B6 00 20 00 00 00 10 00 00 00 00 00 00 00 00 | ... ............
  ** code=0x00B6 (CMD_GET_NXCP_CAPS) version=0 flags=0x0020 id=0 size=16 numFields=0
  ** control message

2020.11.24 08:25:25.716 *D* [comm.cs.3          ] Received control message CMD_GET_NXCP_CAPS
2020.11.24 08:25:25.716 *D* [comm.cs.3          ] Using protocol version 4
2020.11.24 08:25:25.716 *D* [comm.cs.3          ] Sending message CMD_NXCP_CAPS (ID 0; size 16; uncompressed)
2020.11.24 08:25:25.716 *D* [comm.cs.3          ] Outgoing message dump:
  ** 000000 | 00 B7 40 20 00 00 00 10 00 00 00 00 04 00 00 00 | ..@ ............
  ** code=0x00B7 (CMD_NXCP_CAPS) version=4 flags=0x0020 id=0 size=16 numFields=67108864
  ** control message

2020.11.24 08:25:25.744 *D* [comm.cs.3          ] Communication channel closed by peer


When I'm looking into logs, I can see, that on windows agent there is protocol version 4 but on proxy agent is used protocol version 5.

I tried to downgrade windows agent to version 3.5, but with the same result, can't connect to it.

versions of netxms on nodes

netxms server	3.6.252	( linux )
proxy agent	3.6.252	( linux)
agent	3.6.252	windows

Hi,

it is server bug, we just fixed it (server version 3.6.262). Source and Windows packages already available, and deb repositories will be updated in a few hours.

Best regards,
Victor

Hello Viktor,

thank you for reply, unfortunately, after upgrading netxmsd to 3.6.262, I'm still getting different protocol versions. This problems seems related to "proxy agent" -> agent connection, because I can without problems get all information from devices connected directly to netxmsd.

Best regards
Michal

Sorry, read to fast - didn't notice that it is about proxy agent. Can you show logs from both proxy and target agents for period during connection setup?
Also, did you try to downgrade proxy agent?

Best regards,
Victor

We had version 3.5 before and later today rolled out updated for agent to 3.6.262.
Both agents on 3.6.262 can't connect properly.
On some machines, there is no problem with polling configuration through proxy agent.

I did my best to clean output, but agent kept querying everything, so might be some extra logs ( dumps ).

If you need anything more, let me know.

Getting the same problem with upgrade from latest 3.5 to 3.6 today.
Agents behind proxy stopped working.
We had to rollback

I was able to reproduce this issue. We are working on fix now.

Best regards,
Victor

This issue should be fixed by server 3.6.264. Source and Windows packages already updated, deb packages are building right now and should be in repository in few hours.

Best regards,
Victor

Working like a charm, thank you very much. 🥳🥳🥳🥳