NetXMS Support Forum

I think so but I'm not 100% certain (95 :-)

I didn't saw any file locks on NetXMS files. But when I set "EnableWatchdog = no" the update works!
Maybe the watchdog process is not already stopped when files should be replaced. Is the second process in the attached printscreen the watchdog process? When I check the running processes when update failed, none of these two processes are still running.

Thanks for the explanations.

Agent Configuration File on Server:
But I saw in my tests, agent downloads config from server at each agent startup (not like Tatjana wrote) and overwrites local Master Config file completely. That would overwrite all changed local config files on other nodes! I also saw it is also possible with forced encryption and authentication on the node object (so the download of for example "shared secret" is unencryted?)
What is allowed in filter script? I tried object $node but got error (is not object). I also tried example from AdminGuide, but it doesn't work. I didn't found anything in documentation.

Agent Policies:
Is it also possible for SubAgent Config Sections?
In my tests I saw if there is something configured in policy which was also configured in Master Config File, Master Config File has priority. Is that correct?
For what is the tab 'policy' in Policies? The title is there 'Description', is it the same as 'Comments'?
Is it possible to use comments in the XML?
Is it correct, you need to restart agent manually after reinstall changed agent policy ?

thanks for the fast reply. I will correct the existing agents.

try in 'Object Tools' new Tool type 'Action':
Agent's action = test_action
Command generates ouput = ON

Try to set the data type of the DCI to "Integer 64 bit" and use this transformation script:
return (int64($1) * 1024);

I saw the command line of the NetXMS-windows-service is like:
"C:\Program Files\NetXMS\bin\nxagentd.exe" -d -c "C:\Program Files\NetXMS\etc\nxagentd.conf" -n "NetXMSAgentdW32" -e "NetXMS Win32 Agent" -D 0

So the DebugLevel is already defined in the command line ("-D 0") and "DebugLevel = 9" in agent configuration file is useless. When I delete the "-D 0" in the windows registry (value "ImagePath") the "DebugLevel"-setting in the configuration file works.

(tested with NetXMS-Agent V1.2.16 on Win2012R2)

are these two new features documented somewhere? Sound very interesting.

• Instance display name for DCIs created via instance discovery
• DCIs created via instance discovery can be combined by instance into one chart on performance tab

Till now we have all agent configs locally on each node. For better management I want to transfer them to a server based approach. In Admin guide I see two possibilities:

• Agent Policies
• Agent Configuration Files on Server (Agent Config manager)

Now my questions:

• what are the advantages and disadvantages of both functions?
• Which is the better way for the future?

I also tried with deactivated virus scan, same result.
With Sysinternals ProcessMonitor I can see the update process starts (nxagent-1.2.16-x64.exe and nxagent-1.2.16-x64.tmp).
Maybe the attachted ProcessMonitor trace can help you with troubleshooting (in csv format).

I see maybe the same problem on Windows 64bit nodes (Win2012 R2, Win7, Win8.1):
When I start agent upgrade from the NetXMS console in package manager (V1.2.15 to V1.2.16):

• agent is stopped on node
• New install package is uploaded to the node
• Windows Eventlog: Source RestartManger, ID 10006: Application or service 'nxagentd' could not be shut down
• Package Deployment Monitor (after a few minutes): Cannot start package deployment: Request timed out
• Agent is not updated and not started again
• On WinXP 32bit no problem

In agent event-log (DebugLevel=9):
[INFO ] Watchdog process stopped
[WARN ] Communication session broken: A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call.
[INFO ] WINPERF: Collector thread for counter set B terminated
[INFO ] WINPERF: Collector thread for counter set C terminated
[INFO ] WINPERF: Collector thread for counter set A terminated
[INFO ] NetXMS Agent stopped


Now I have to update the agents manually

I still see the same error too. The same as I described in my first post. Which information do you need for further troubleshooting? I also see a lot of SYS_IF_PEER_CHANGED events from different nodes but nothing has changed in topology.

will this be fixed in V1.2.16? I can't delete all affected nodes.

I installed the windows agent by the 'nxagent-1.2.15-x64.exe' but there is no File Management Subagent in the subagent selection list of the installer (only ecs.nsm, ping.nsm, logwatch.nsm, portcheck.nsm, winperf.nsm, wmi.nsm, ups.nsm) and there is no 'filemgr.nsm' file in the 'bin'-directory after installation.
In log file I get:
Error loading subagent module "filemgr.nsm": The specified module could not be found.

Thank you. I was looking in the wiki.
Is the file management subagent only available on linux agents?