NetXMS Support Forum

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.

I've noticed that the same trap has been thrown at extreme devices. Analyzing the logs of this device the following message appears:

Login failed through SNMPv3 - not in life time

According to extreme documentation this seems to be a problem on the NMS server, as per the following link:

https://extremeportal.force.com/ExtrArticleDetail?an=000077945

Any hints on what could be done?

Thanks,

Hi Victor,

Thanks for uploading files. I realized however that maybe there are some terms where there are no matching keys in the files. Probably from the latest updates. Wouldn't there be a way to include the missing keys with standard text to add them to the translation?

As for the changes, could they be adopted in the legacy version and also in the new UI in the future?

Hello,

Analyzing the packages I got the error as shown in the attached image:
The SNMP credentials are correct, on the devices the SNMP server address was pointed to an SNMP proxy.


Thanks,

Hi,

I would like to help with the Portuguese translation, since I see there are many terms that no longer have translation in the tool.

If someone sends the current version of the files that haven't been completely translated I can start this work.

Hello,
I only managed to make the errors stop on the device by checking the option to disable the use of SNMP for all polls. However, this makes it difficult to poll the device and look up status.
The option to prevent SNMP configuration change is also checked.

Could anyone help? thanks

Hey guys,

On a Huawei switch we configure snmpv3 for polling and sending traps, the polling and sending traps normally occurs except that the switch sends from time to time a series of traps related to authentication failure, approximately every 10 min.

SNMP_AUTH_FAILURE .1.3.6.1.6.3.1.1.5.5
The switch is in a zone and the snmp trap configuration on the equipment points to the proxy.

I believe some of the switc polls are causing this issue, probably with some invalid credential.

Thank you for your help,

A great improvement will make it easy. Thanks for the answer.

How to initialize subgent for mongodb? Documentation is unclear.
The agent was installed via the repository, but the subagent does not appear to be present. Is it necessary to compile it manually?

Thanks,