NetXMS Support Forum

Seems that actual conversion was already done. Execute the following SQL statement:
UPDATE metadata SET var_value='' WHERE var_name='PendingOnlineUpgrades';

This will inform nxdbmgr that all pending background updates are completed.

Yes, it should be safe to upgrade to 4.3.6.

Best regards,
Victor

Could you also provide server log file with debug level 6 for the duration of topology poll on that switch (i.e. set debug level to 6, go to Poll -> Topology on the switch node, set debug back)?

Also, don't forget about our  questionnaire! We'd really appreciate your input.

Direct link: https://survey.alchemer.com/s3/7316052/NetXMS?uid=live

Hello NetXMS community,

We just published patch release 6 for version 4.3. Changes since previous patch release:

- Correctly handle FDB record type "secure"
- Improved driver for Cambium devices
- Fixed bug in handling /32 addresses during network discovery
- Fixed bug in flood notification processing in Telegram driver
- Fixed server crash caused by timeout during file transfer to agent
- Fixed bug in SNMP codepage handling
- Fixed bar gauge dashboard element drawing issue
- Small fixes and improvements in new management client application

Hi,

I've found a bug introduced in 4.3 which may cause incorrect decoding of strings received via SNMP (SNMP codepage was ignored in some cases). Fix will be included into upcoming patch release 4.3.6.

Best regards,
Victor

Yes, it actually could be related to codepage. Depending on entry type, NetXMS server may require to search for peers using texts (interface descriptions for example), and if it is received incorrectly search will fail. To be able to diagnose it I likely will need exact walk outputs though. We can move discussion to private messages or Telegram if you don't like to share such data publicly.

Best regards,
Victor

Hi,

I will take a look at it in the next few days. Will you be able to run test build to verify changes to Jira connector?

Best regards,
Victor

I've added processing of FDB record status 6 - next patch release should process them in a same way as status 3 (dynamic).

Best regards,
Victor

I probably do not completely understand what the issue is. Configuration looks correct, you set "Name" column as instance column, not an "Index". But it should work both ways.

You should create local SQL account. It should be also possible to login with the same AD user NetXMS agent runs under (in that case you should specify * as login name and password is not needed). 

Best regards,
Victor

Hi,

can you show exact errors you are getting?

Best regards,
Victor

Can 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

Hi,

are you using TimescaleDB?

Best regards,
Victor

We just published patch release 5 for version 4.3! Changes since previous patch release:

- Fixed bug in X.509 certificate subject and issuer decoding
- Agent tunnel listener will not start if server certificate is not loaded
- Fixed WEB service configuration import with multiple headers
- Fixed login issues in new web UI
- Small fixes and improvements in new management client application
Fixed issues:
   - NX-2272 (Session is not closed if user cancel 2FA auth initialization)
   - NX-2276 (Warn user when adding too wide mask to active discovery)
   - NX-2388 (Modify default templates - filesystem with type "ahafs" should be excluded from discovery)
   - NX-2404 (Integer division by zero in NXSL crashes server)
   - NX-2406 (Entering maintenance mode on cluster does not trigger maintenance mode on nodes within cluster)

I just fixed certificate subject parsing, fix will be included into next release.

Best regards,
Victor