NetXMS Support Forum

Hi!

You can use situations in conjunction with dummy DCI. For example, you can update situation object each time you got line from a log, setting situation's attribute to current time stamp. Then, create dummy DCI with transformation script, check situation's attribute, and return different values depending on how long time was passed since last situation update, and set thresholds as usual. And starting from 1.0.8, you will be able to generate new event directly from transformation script.

Best regards,
Victor

Hi!

It's a bug in a server. I have fixed it, and version 1.0.8 should work fine. If you are running server on UNIX, I can post a patch. Also, as a workaround, you can use function GetSituationAttribute to get attribute's value instead of directly accessing it.

Btw, you should specify attribute name without quotes in configuration dialog.

Best regards,
Victor

Da, v min i max bila oshibka pri rabote s raznimi tipami dannih. Ispravil, v 1.0.8 etoj problemi ne budet.

Hi!

Please replace file dbinit_mssql.sql with attached one and run nxconfig.exe again. It should initialize database properly.

Best regards,
Victor

Hi!

Fixed that, thank you!

Best regards,
Victor

Hi!

I have updated NetXMS user manual. Now it contains up-to-date information about all available NXSL functions and classes (Event, Node, and DCI). Also I have implemented NXSL function PostEvent (will be included in 1.0.8 release) which could be used to generate events on behalf of any node (according to security settings, as with FindNodeObject).

Best regards,
Victor

Hi!

Parser file should be placed on the agent.

Best regards,
Victor

Hi!

Last special build uses SO_REUSEADDR option - it makes no difference. As for MaxUserPort, things are different on Windows 2008 - http://support.microsoft.com/kb/929851. So by default we should have about 16000 ports for outgoing connections, which is much more then required.

Best regards,
Victor

It also could be Windows 2008 issue. We have installation in Riga with 700+ agents - and I never seen issues like that. They are running on Windows Server 2003 x86.

Best regards,
Victor

Hi!

I'm still unable to reproduce this issue or find any clue to the source of the problem. Please try to replace libnetxms.dll to attached one - it has another changes in communication code. At least, it may give more meaningful error codes in "agent unreachable" messages in the log.

Also, do you experience this issue from the beginning, or it appears after latest upgrades?

Best regards,
Victor

Could you please try to install updated build: https://www.netxms.org/download/rc/netxms-1.0.8-rc2.exe. If it will not solve the problem, please set logging to file (by setting LogFile = some_file in netxmsd.conf) and run netxmsd.exe with -D 6 command line option (this will enable debug output). It will generate a lot of messages in the log file - I'm interested in messages containing words "agent unreachable, error=".

Best regards,
Victor

Hi!

I plan 1.0.8 to be mostly a bugfix release (plus custom SNMP port feature), and if everything will go as expected, I'll will release it in a week.

Best regards,
Victor

Few additional questions:

Do you have a Windows firewall running on server machine?
Is there any error messages in netxmsd log?

Best regards,
Victor

I suspect that it may hit some limits for open connections. There was a limit of around 4000 outgoing TCP connections in Windows 2003, I'm not sure how it is in Windows 2008. Could you please run netstat -n and count connections to external IPs on port 4700? And how many of them are not in ESTABLISHED state?

Best regards,
Victor

Hi!

Unfortunately I cannot reproduce this on my system. Could you please run nxagentd under gdb and send me a backtrace after crash?

To run agent under gdb:

1. Run command
gdb /opt/netxms/bin/nxagentd

You will get gdb prompt:
(gdb)

Type command:
run -f

Agent will run in foreground. After crash, gdb prompt will appear:
(gdb)

Type command
bt

and send it's output to me.

Best regards,
Victor