NetXMS Support Forum

Hi,

Everything is OK.

Thanks!

Hi,

Everything ok with the display.

Thank you very much!

Hi,

An object tool's access control list does not correctly display objects in the new client when there are two or more users/groups in the list.


Thanks

Hello,

When configuring a DCI as uptime in the unit parameters, the web version of the netxms console displays {0} instead of the number of days. This problem does not happen on the desktop console.

Hi,

I noticed that the error appeared again, but observing the repetition of the event I understood that when NetXMS adds a new node through network discovery, this node would later generate the error in the database.
I'm not sure what the reason is, but it seems to me that if the node is not compatible with the agent, simply check the option to disable the use of the NetXMS agent in the status poll and the error would disappear.

It seems to be some bug.

length are above 1796 characters and the size in the database is a varchar of 1700

Hey,

Saving ssh keys on the platform appears not to be possible when it exceeds the character length for both key types. Is manually increasing the size of columns in the database a safe procedure or could it impact new updates?


Thank you

Hi,

I believe it is some incorrect configuration. NetXMS is capable of receiving SNMPv3 traps. NetXMS supports only DES or AES128 encryption, if I'm not wrong.

Hi,


In my case, I set all nodes as unmanaged and changed them to managed little by little until I found the node that caused the error. Then I noticed that the node crashes the system in the configuration poll.

Can anyone explain this error, problem with the NetXMS source code?


Thanks,

Tested several times using debug which shows an error but unfortunately it is not clear to me:


*D* [ndd.common         ] NetworkDeviceDriver::getInterfaces(0x7f60e65fcec0): completed, ifList=0x7f60e65ba100
*** stack smashing detected ***: terminated



Thanks,

The server started crashing. The netxms process starts and stops shortly after. For users the message connection refused appears. 
Using nxdbmgr check no longer shows errors, however there are SQL errors in the log file with lines similar to this:

SQL query failed (Query = "SELECT tdata_value,tdata_timestamp FROM tdata_25925 WHERE item_id=9696 ORDER BY tdata_timestamp DESC LIMIT 1"): 42P01 ERROR: relation "tdata_25925" does not exist
LINE 1: SELECT tdata_value,tdata_timestamp FROM tdata_25925 WHERE it...

Could this be the cause of the service execution crash?
It's in the latest version.


Thanks,

Solved in 4.4.1!

Quote from: Meandmybrain on July 16, 2023, 11:21:25 PM

Quote from: lhpaladin on July 16, 2023, 10:38:46 PMHello,
The latest version of the client requires Java 17, maybe it's the 404 error failure.

Hi,
I'll give it a try. Could you please tell me where you found this information? In the admin guide it says ,,Supported Java version is 11 or 15."
Edit: found it.
Thanks
M.

You can see this link:
https://www.netxms.org/forum/announcements/netxms-4-4-released/

I believe the documentation needs to reflect this change.

Hello,
The latest version of the client requires Java 17, maybe it's the 404 error failure.