NetXMS Support Forum

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

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.

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

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

Hey,

I take it back. I noticed, that UI didn't change at all and it seems, like in tomcat8 was cached old version of netxms.

For future reference - removing content of tomcat/work/ resolved issue

Hello,

I can't get working newest web management console ( nxmc-3.5.90.war ).
Everything is fine ( tomcat starts, site loads ) but when I log in, I get error message

Server uses incompatible version of communication protocol (server=[52, 4, 1, 1, 1, 28, 1, 2] client=[52, 4, 1, 1, 1, 27, 1, 2])


Any ideas, what could be problem or what did you do on your end to get this working?

Thank you very much

In shortcut ... We have 3 identical servers. 2 of them show unsupported DCI's and 3rd one is completely OK. All use same templates.

It's very strange and semi-random I'd say.

Hello,

thank you for update! Do you have any timeframe, when will you be able to fix DCI status changed to Unsupported?

Hello, this problem for us persists in bigger scale after upgrade to netxms 3.

Do you have any suggestion?


Minor Outstanding Status of DCI 442 (Internal: PingTime) changed to UNSUPPORTED     1 0 30.09.19 12:31:09 30.09.19 12:31:09
Minor Outstanding Status of DCI 409 (Internal: PingTime) changed to UNSUPPORTED   1 0 30.09.19 12:31:09 30.09.19 12:31:09
Minor Outstanding Status of DCI 842 (Internal: PingTime) changed to UNSUPPORTED   1 0 30.09.19 12:31:09 30.09.19 12:31:09
Minor Outstanding Status of DCI 1043 (Internal: PingTime) changed to UNSUPPORTED   1 0 30.09.19 12:31:09 30.09.19 12:31:09
Minor Outstanding Status of DCI 846 (Internal: PingTime) changed to UNSUPPORTED   1 0 30.09.19 12:31:09 30.09.19 12:31:09
Minor Outstanding Status of DCI 834 (Internal: PingTime) changed to UNSUPPORTED   1 0 30.09.19 12:31:09 30.09.19 12:31:09
Minor Outstanding Status of DCI 829 (Internal: PingTime) changed to UNSUPPORTED   1 0 30.09.19 12:31:09 30.09.19 12:31:09
Minor Outstanding Status of DCI 826 (Internal: PingTime) changed to UNSUPPORTED   1 0 30.09.19 12:31:09 30.09.19 12:31:09
Minor Outstanding Status of DCI 831 (Internal: PingTime) changed to UNSUPPORTED   1 0 30.09.19 12:31:09 30.09.19 12:31:09
Minor Outstanding Status of DCI 550 (Internal: PingTime) changed to UNSUPPORTED   1 0 30.09.19 12:31:09 30.09.19 12:31:09
Minor Outstanding Status of DCI 568 (Internal: PingTime) changed to UNSUPPORTED   1 0 30.09.19 12:31:09 30.09.19 12:31:09


Hello,

has been this fixed? I have 2.2.13 and the problem is still persisting.

Hey Peter,

no we haven't found any solution. Still waiting for Victor or someone with much bigger insight to advice or check if there is bug.
We can only always after cleanup delete those UNSUPPORTED alarms and go with the rest as usual.

Hello and sorry for a bit late answer. We have been trying to figure this out over the last days.

So it has definitely something to do with housekeeper. It was set at 2am, when we changed it to different time, all those warning arose about that new time.

So after that I was able to easy backup logs
So this are some of those SNMP errors from log. If it will be more helpful, I can attach you whole log file.
We even updated to version 2.2.12, but still this is happening. If you need some more information let me know.


2019.01.18 11:02:43.357 *D* Node::connectToAgent(TLA-RPi-agent [1283]): already connected
2019.01.18 11:02:43.358 *D* [agent.conn.113     ] Sending message CMD_DATA_COLLECTION_CONFIG (1304) to agent at 87.197.117.89
2019.01.18 11:02:43.359 *D* [db.cpool           ] Handle 0x7f9bfae45e60 released
2019.01.18 11:02:43.359 *D* [db.cpool           ] Handle 0x7f9bfae46220 acquired (call from dbwrite.cpp:250)
2019.01.18 11:02:43.359 *D* [db.cpool           ] Handle 0x7f9bfae46040 released
2019.01.18 11:02:43.359 *D* [event.proc         ] Event 9218196 with code 53 passed event processing policy
2019.01.18 11:02:43.359 *D* [event.corr         ] CorrelateEvent: event SYS_DCI_UNSUPPORTED id 9218197 source GIM-CCTV-UPS1 [1365]
2019.01.18 11:02:43.359 *D* [event.corr         ] CorrelateEvent: finished, rootId=0
2019.01.18 11:02:43.359 *D* [event.proc         ] EVENT SYS_DCI_UNSUPPORTED [53] (ID:9218197 F:0x0001 S:2 TAG:"") FROM GIM-CCTV-UPS1: Status of DCI 9009 (SNMP: .1.3.6.1.4.1.935.1.1.1.3.2.1.0) changed to UNSUPPORTED
2019.01.18 11:02:43.359 *D* [event.policy       ] EPP: processing event 9218197
2019.01.18 11:02:43.359 *D* [event.policy       ] Event 9218197 match EPP rule 22
2019.01.18 11:02:43.359 *D* AlarmManager: adding new active alarm, current alarm count 18



2019.01.18 11:02:43.330 *D* [agent.conn.174     ] Sending message CMD_SNMP_REQUEST (43037) to agent at 212.55.237.190
2019.01.18 11:02:43.335 *D* [db.cpool           ] Handle 0x7f9bfae45aa0 released
2019.01.18 11:02:43.335 *D* [db.cpool           ] Handle 0x7f9bfae45e60 acquired (call from dbwrite.cpp:250)
2019.01.18 11:02:43.335 *D* [db.cpool           ] Handle 0x7f9bfae45c80 released
2019.01.18 11:02:43.335 *D* [event.proc         ] Event 9218195 with code 53 passed event processing policy
2019.01.18 11:02:43.335 *D* [event.corr         ] CorrelateEvent: event SYS_DCI_UNSUPPORTED id 9218196 source GIM-GXSW26-IVZ-EKON RIADITEL [1393]
2019.01.18 11:02:43.335 *D* [event.corr         ] CorrelateEvent: finished, rootId=0
2019.01.18 11:02:43.335 *D* [event.proc         ] EVENT SYS_DCI_UNSUPPORTED [53] (ID:9218196 F:0x0001 S:2 TAG:"") FROM GIM-GXSW26-IVZ-EKON RIADITEL: Status of DCI 11388 (SNMP: .1.3.6.1.4.1.25506.2.6.1.1.1.1.12.12) changed to UNSUPPORTED
2019.01.18 11:02:43.336 *D* [event.policy       ] EPP: processing event 9218196
2019.01.18 11:02:43.336 *D* [event.policy       ] Event 9218196 match EPP rule 22
2019.01.18 11:02:43.336 *D* AlarmManager: adding new active alarm, current alarm count 17


Thank you,
Michal

Hello,

we recently upgraded to version 2.2.11 and after we are getting at night (around 1:30am) massive amount of warning (see attached picture).
Devices are mainly UPS but there are servers as well - different hardware with different versions of Windows.

Weird thing is, we have 3 same servers (hardware and software) but this alarm comes only from one of them. We tried to update agents to most recent version, but that did not helped.
All database upgrades, checks and fixes were applied.

Any tips or hints, where to look for problem or solution?

Thank you!

Thank worked...

Just to be clear, I run command sudo find /usr/local/lib -name "*ne*" -exec rm rf {} \; && sudo find /usr/local/lib -name "*nx*" -exec rm rf {} \; ...

Don't do that without checking what you delete

Thanks for pointing out by Victor Kirhenshtein

yes,

sorry for late reply

sudo ldd /usr/bin/nxagentd
        linux-vdso.so.1 (0x00007ffff21d9000)
        libappagent.so.2 => /usr/local/lib/libappagent.so.2 (0x00007f218d4e4000)
        libnxagent.so.2 => /usr/local/lib/libnxagent.so.2 (0x00007f218d2dd000)
        libnxdb.so.2 => /usr/local/lib/libnxdb.so.2 (0x00007f218d0cd000)
        libnetxms.so.2 => /usr/local/lib/libnetxms.so.2 (0x00007f218ce44000)
        libnxsnmp.so.2 => /usr/local/lib/libnxsnmp.so.2 (0x00007f218cc2f000)
        libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007f218ca03000)
        libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f218c7e9000)
        libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007f218c5d2000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f218c3ce000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f218c1b1000)
        libssl.so.1.0.2 => /usr/lib/x86_64-linux-gnu/libssl.so.1.0.2 (0x00007f218bf48000)
        libcrypto.so.1.0.2 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.2 (0x00007f218bae2000)
        libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f218b760000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f218b45c000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f218b245000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f218aea6000)
        libnxexpat.so.2 => /usr/local/lib/libnxexpat.so.2 (0x00007f218ac82000)
        libnxtre.so.5 => /usr/local/lib/libnxtre.so.5 (0x00007f218aa70000)
        libnxjansson.so.4 => /usr/local/lib/libnxjansson.so.4 (0x00007f218a864000)
        /lib64/ld-linux-x86-64.so.2 (0x000055aabb747000)