NetXMS Forum

Hi Alex, thank you for the detailed analysis. We checked our current NetXMS 6.2.5 installation. Both Dell drivers are present: dell.ndd 426K dell-pwc.ndd 168K Old NetXMS libraries are still present in /usr/local/lib: We found both .so.50 and .so.61 versions, including the libraries you mentioned: libnxsrv.so.61 libnxsl.so.61 libnetxms.so.61 .. The old Dell driver is actively loaded under NetXMS 6.2.5. Our server log contains several entries such as: Network device driver DELL-PWC loaded successfully This confirms that the old driver is still being loaded in our current 6.2.5 installation. We have not removed or modified any files yet, as the current production server is still running 6.2.5. Your explanation sounds very plausible and matches what we found. We will prepare a clean upgrade to 7.0.2, removing the obsolete driver and libraries as suggested. Thanks again for investigating this issue! Best regards Alwin

I've created tickets covering above-mentioned issues: https://github.com/netxms/netxms/issues/3278 https://github.com/netxms/netxms/issues/3277 https://github.com/netxms/netxms/issues/3276

Hi, try just 59 * * * 6-7 for second schedule - it should have same effect. Best regards, Victor

If you have that node under some other container or template, you can remove it from cluster and then you can add it to another cluster (all done from cluster context menu). By the way, how many clusters do you have in your system (just to understand the scale how people use clusters)

Hi, this is very strange. I just compared process execution and external parameter handling code in 3.9 and 4.1 and the only difference is that in 4.x agent replaces null characters with spaces in received command output. Theoretically if script returns null character in first line that could cause such difference in behavior. Best regards, Victor