NetXMS Support Forum

Does it happen with some remote agent, or also with agent that runs along with the server?

For now the reason is not clear. Can you enable DebugLevel 8 on the server and that agent and share their logs?

Any chances we can remote access to this Windows system?

The crash collector service seems to be running fine, so seems that server is nor really crashing.

Can you stop netxms core service and run it from command line:

C:\NetXMS\bin\netxmsd -D 6

and once the issue occurs, pls share the screenshot of whole cmd window.

NetXMS has automatic event correlation based on topology. For this to work, NetXMS server should have snmp access to all routers between itself and your APs, then it would have full topology picture.

You can check by right-clicking on an AP, Route from... and choosing NetXMS server node. The other way to check is probably an automatic L3 network map.

I might be wrong about peculiarities of how all this works, would be good to hear if this works on your system.

Note that there are two options:

NetworkService.Status(smtp://domain.org:port)
NetworkService.Status(smtps://domain.org:port)

Try specifying port in the metric, e.g. NetworkService.Status(smtps://domain.org:465), make sure you can connect to that port using telnet from your netxms server's command line, e.g.:

telnet domain.org 465

Log file in C:\NetXMS\crash ?
Pls share it

Looks like DumpDirectory should be specified for dump collection to work. Pls create C:\NetXMS\crash
 folder and try the following in netxmsd.conf:

CreateCrashDumps=yes
DumpDirectory=C:\NetXMS\crash

Well, could be that something related to crash dumps is broken.

As additional check, can you stop NetXMS Core service and run server manually from Windows command line:

c:\NetXMS\bin\netxmsd -D 6

pls show last line of output, when it crashes.

Please enable

CreateCrashDumps

in server config file and specify folder to store them by DumpDirectory parameter in config (Default is C:\)

Share the file somewhere and send me link to in in private message (or I can provide a place to upload it if needed)

Ok, just in case, set debug level for these tags:

debug ncd.* 7
debug ncd 7
debug nc.* 7
debug nc 7

they issue

debug

command and check that debug levels were actually set.

QueryTemplate is the actual sql query, where ? sign works as macro, it's first occurrence is replaced by recipient and second by message body. E.g.:

QueryTemplate=insert into notifications values (?, ?);

It should be in log file, /var/log/netxmsd on Linux and C:\NetXMS\log\netxmsd.log on Windows

Ok, but what about message field, it also should be empty?

Anyways, let's add some debug. In Tools -> Server debug console issue

debug ncd.* 7

this will set debug level 7 for notification channel driver related debug. Then check server log file

I wonder that Recipient column in the log is empty. How is your action configured, recipient is specified in it.

If you can close this error message and it does not occur again when using the console, you can disregard this error message.

The version that you are using (2.0.1) is very old and not supported any more. But, as I remember, there was a checkbox "slow connection" on login screen of the console. Checking it skipped downloading mib file to client, so you can check if that is unchecked.

You can create nxreportd.properties file in C:\NetXMS\etc\nxreportd folder. In this file you can specify bind address:

nxreportd.bindAddress=1.2.3.4

setting it to * or 0.0.0.0 will bind to all available interfaces.