NetXMS Support Forum

I have fixed it. Agent now will correctly handle rename of monitored file (which usually happens during log rotation). I plan to release version 0.2.31 in a few days, it will contain this fix.

Best regards,
Victor

Спасибо за trace, решил проблему. В течении нескольких дней выложу версию 0.2.31, которая будет корректно работать с трапами версии 3.

Я в ближайшие дни выложу версию 0.2.31 с исправлениями последних багов. Эта проблема тоже должна быть решена.

Yes, it's looks like a bug. I'll check it in a few days.

Best regards,
Victor

Hello!

This may happen when communication session that was inactive for long period (controlled by agent's parameter SessionIdleTimeout) forcibly closed by watchdog thread. You can safely ignore these messages.

Best regards,
Victor

Hi!

Looks like sockets opened by agent closing slower than agent restarts. You can try to add agent startup delay by adding parameter to configuration file:


StartupDelay = <seconds>


and try different delay values. However, it will still be possible that NetXMS server will detect non-responding agent and generate appropriate event.

But why you are need to restart agent after log rotation? Is it stop working, or prevents log rotation? It is supposed to detect log rotation and handle it, and if it doesn't, then it's a bug which needs to be fixed.

Best regards,
Victor

I was able to reproduce this problem on my machine. Please replace file src/server/core/userdb_objects.cpp and recompile server - problem should be fixed.

Best regards,
Victor

Just tested on my Ubuntu machine with PostgreSQL - I got failed SQL query, but no crash. Could you please run netxmsd under gdb and when it crashes get stack trace with bt command?

To run under gdb:

# gdb netxmsd
(gdb) run

when crashes
(gdb) bt

Best regards,
Victor

Hi!

Yes, it's a bug - there should be

DELETE FROM user_groups WHERE id=%d

However, failed SQL query should not cause server to crash anyway. Could you try to replace groups to user_groups in this query, recompile server and try delete group again?

Best regards,
Victor

Vilozil obnovlennij User Manual, tam dobavleno opisanie monitoringa sysloga.

Dlja sysloga znavhenija severity sledujuschie:

1   Emergency
2   Alert
4   Critical
8   Error
16 Warning
32 Notice
64 Informational
128 Debug

T.e. dlja fil'tracii informational, notice, and warning nado pisat' <level>112</level>

Please direct netxmsd output to file by replacing

LogFile = {syslog}

to

LogFile = some_file_name

in netxmsd.conf, then to start it from command line in debug mode:

netxmsd -D 9

and post debug output here or send it to [email protected].

Best regards,
Victor

Hello all!

NetXMS version 0.2.30 released. It fixes upgrade problems discovered in 0.2.29, mostly related to installations with MS SQL or Oracle as backend database. If you are already upgraded to 0.2.29 and does not experience any problems, upgrade to 0.2.30 is not necessary.

Best regards,
Victor

Please try to replace nxdbmgr.exe with attached one and run upgrade process again.

Best regards,
Victor

Spasibo, ispravil.