NetXMS Support Forum

Restarting the Core-service at the NetXMS server made the alarm go away. This time it was easy. :-)

A server was shut down when a customer moved from one place to another, and an expected "Node down" alarm turned up in the NetXMS Management Console.

When the server got back up at another place it had its IP address changed, and for unrelated reasons we have decided not to monitor this server anymore.

The problem now is that we are unable to terminate or in any other way get rid of the alarm. When we try to terminate it (or manage it in any other way), there's an error message:

Title: "Probelm Occurred"
Message: "'Terminate alarms' has encountered a problem. Cannot terminate alarm: Invalid alarm ID" (The Details section only repeats the last sentence.)

(I've found two threads on this problem, one from 2008 and one from 2013, but neither discloses the solution.)

The annoying SYS_AGENT_UNREACHABLE seems to have disappeared after the SessionIdleTimout configuration. Thank you very much, Victor.

Thank you. I'll do that and report back later.

Thank you for taking time, Victor Kirhenshtein, I really appreciate it. Sorry to have to respond to every suggestion with a question, but where would that parameter be? - There's no such parameter in the agent's config file, and I can't find it in the object's Properties either.

Personally I can't find anything consistent with the alarms in the logs. There are "Session diconnected by timeout", but these are quite frequent and not necessarily at the same minutes that we get the alarms.

If anybody finds anything or has any idea of a next step, please don't hesitate to let me know. :-)

I'm attaching an hour's worth of the log file, between 09:00 and 10:00. During that time there were five alarms, approximately 09:17, 09:21, 09:23, 09:32, 09:42, and 09:48. Thanks for taking time!

That did the trick, Victor. Now there's a lot of logging going on. I'll get back tomorrow with the result.

That folder is empty.

Am I missing something obvious or is this the Twilight Zone. I once more opened the nxagentd.conf file, ensured that DebugLevel is 6, saved and closed, restarted the Agent, and the log file once again says "0". This is the content of the conf-file:

Quote#
# NetXMS agent configuration file
# Created by agent installer at Thu Sep 29 15:41:41 2011
#

MasterServers = 192.168.25.17

FileStore = F:\Program\NetXMS\var\
LogFile = F:\Program\NetXMS\etc\nxagentd.log
DebugLevel = 6
SubAgent = ecs.nsm
SubAgent = ping.nsm
SubAgent = logwatch.nsm
SubAgent = portcheck.nsm
SubAgent = winperf.nsm
SubAgent = wmi.nsm
SubAgent = ups.nsm

Yes, "DebugLevel = 6".

Nothing seems to get logged except the start of the service. Since then there have been several "Native agent is not responding" alarms, but nothing the logging picked up on.

Quote
[25-Jan-2016 11:52:02.347] Log file opened
[25-Jan-2016 11:52:02.347] [INFO ] Additional configs was loaded from F:\Program\NetXMS\etc\nxagentd.conf.d
[25-Jan-2016 11:52:02.347] [INFO ] Debug level set to 0
[25-Jan-2016 11:52:02.550] [INFO ] DB Library: Database driver "sqlite.ddr" loaded and initialized successfully
[25-Jan-2016 11:52:02.659] [INFO ] Subagent "WINNT.NSM" loaded successfully
[25-Jan-2016 11:52:02.659] [INFO ] Subagent "ecs.nsm" loaded successfully
[25-Jan-2016 11:52:02.659] [INFO ] Subagent "ping.nsm" loaded successfully
[25-Jan-2016 11:52:02.659] [INFO ] Subagent "logwatch.nsm" loaded successfully
[25-Jan-2016 11:52:02.659] [INFO ] Subagent "portcheck.nsm" loaded successfully
[25-Jan-2016 11:52:07.573] [INFO ] Subagent "winperf.nsm" loaded successfully
[25-Jan-2016 11:52:07.573] [INFO ] Subagent "wmi.nsm" loaded successfully
[25-Jan-2016 11:52:07.573] [INFO ] Subagent "ups.nsm" loaded successfully
[25-Jan-2016 11:52:08.587] [INFO ] Listening on socket 0.0.0.0:4700
[25-Jan-2016 11:52:08.587] [INFO ] Listening on socket [::]:4700
[25-Jan-2016 11:52:09.601] [INFO ] NetXMS Agent started

Thank you, tomaskir. When I at first wrote [Path]\logfile.txt, NetXMS created a folder called logfile.txt, so I assumed that that last part should be a folder, but obviously the file extension .log is the key. -- I'll get back with the log file contents!

Hm. This is quite weird. If I add the line "LogFile = C:\Program\NetXMS\etc\" (without quotation marks, and there's nothing wrong with the path), I am unable to restart the NetXMS service, or start it when it is stopped. If I delete the line, I can restart/start the service.

I came to this in my fruitless attempts to generate a log file, I assumed that the service needed a restart to have the file created after the parameter was added.

Thank you. I did as you suggested. Where will the log file end up?