NetXMS Support Forum

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.

Hello everybody:

Netxms is showing an error in the INSERT of the object_properties table with the following message:
22P02 ERROR: invalid input syntax for type integer: \"-(\"

Is there any way to find the object that is generating this error?

Thanks!

Quote from: Victor Kirhenshtein on April 26, 2023, 02:50:09 PMCan you check if you actually have tables maintenance_journal and maintenance_journal_v43_9, and if table maintenance_journal is a hypertable?

If you are not using maintenance journal functionality you can safely ignore this error, just make sure that hypertable maintenance_journal exists.

Best regards,
Victor

I'm sorry for the late reply,
There is only maintenance_journal which is a hypertable. Is it possible to manually adjust this situation? Would it be safe to upgrade to new versions?

Thanks,

Quote from: Victor Kirhenshtein on April 24, 2023, 01:53:19 PMHi,

are you using TimescaleDB?

Best regards,
Victor

Yes,

It works normally now, thanks

Hi Victor, good work.

Upgrading from 4.3.4 to 4.3.5 I had the following problem:

QuoteRunning background upgrade procedure for version 43.9
Converting table maintenance_journal
Running background upgrade procedure for version 43.9
Converting table maintenance_journal
SQL query failed (42P01 ERROR:  relation "maintenance_journal_v43_9" does not exist
LINE 1: ...eation_time),to_timestamp(modification_time) FROM maintenanc...
                                                            ^):
...

Running nxdbmgr background-upgrade

QuoteConverting table maintenance_journal
SQL query failed (42P01 ERROR:  relation "maintenance_journal_v43_9" does not exist

Thanks in advance

Hi, 

The "Find switch port" option shows results with the wrong column order and does not show whether the connection is direct or indirect in the list. Are there any open issues?
Version: Desktop Management Console - Legacy UI

Thanks

Hi, 

Link?

Quote from: Filipp Sudanov on January 30, 2023, 05:21:02 PMWas unable to replicate this.
Is this background image configured as rack Passive Element? Can you show properties of that passive elements?
Do you also have some other nodes that are present in this rack? Do they useHi, default images or custom? Can you also show screenshots of their rack properties?

Hi,

I have also seen similar bug adding passive elements. The images do not appear according to the orientation of these elements.

Hi,

I believe you can put the netxms-websvc-x.x.xx.war file in your Tomcat server webapps folder.

Maybe this thread will help you about properties file: https://www.netxms.org/forum/general-support/setup-webapi-seperated-with-netxms-server/

Hi,

The error appears in later versions. Could it be added to be fixed in later versions?


Thanks!

Hi Victor,


Thank you very much for your attention. I believe it will help other users as well.

When it's ok, I'll test and come back here.