<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Problem with centralized agent upgrade]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">We are having problems with centralized agent upgrade (NetXMS Package Manager and deploy to managed nodes option) for all agents.<br />
NetXMS server is running on 2012 R2 standard edition, agents are running on various versions of windows server.<br />
Our NetXMS server was running on NetXMS version 1.2.13 and it was upgraded to version 1.2.14.<br />
All agent are on version 1.2.13.<br />
We have the correct agent package and .NPI file.<br />
I’ve noticed when I run the option “deploy to managed nodes” the file is uploaded to the agent, installation status is holding on and after 10 minutes the upgrade process fails with the following error:<br />
Deploy agent package has encountered a problem.<br />
Cannot start package deployment: Request timed out</p>
<p dir="auto">Agent is stopped and it has to be started manually to work.<br />
We tried out in our test environment with same upgrading scenario and it works fine.<br />
When I try to upgrade them manually there is no problem.<br />
Could someone advise me what is the best way to troubleshoot this issue?</p>
<p dir="auto">Thanks for the help<br />
Nikola</p>
]]></description><link>https://forum.netxms.org/topic/3242/problem-with-centralized-agent-upgrade</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 14:10:28 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/3242.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 26 Jun 2014 13:09:42 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Problem with centralized agent upgrade on Thu, 14 Aug 2014 18:52:46 GMT]]></title><description><![CDATA[<p dir="auto">I think so but I'm not 100% certain (95 <img src="https://forum.netxms.org/assets/plugins/nodebb-plugin-emoji/emoji/android/1f642.png?v=72b86a538fc" class="not-responsive emoji emoji-android emoji--slightly_smiling_face" style="height:1.4em;width:auto;vertical-align:middle" title=":-)" alt="🙂" /></p>
]]></description><link>https://forum.netxms.org/post/14686</link><guid isPermaLink="true">https://forum.netxms.org/post/14686</guid><dc:creator><![CDATA[user54119]]></dc:creator><pubDate>Thu, 14 Aug 2014 18:52:46 GMT</pubDate></item><item><title><![CDATA[Reply to Problem with centralized agent upgrade on Thu, 14 Aug 2014 18:37:22 GMT]]></title><description><![CDATA[<p dir="auto">It makes sense. Theoretically it is possible that main process terminates before watchdog process completely stopped, and so files are still locked when installer start copying new files. I've changed agent so main process waits until watchdog process terminates and only then exits.</p>
<p dir="auto">Was watchdog enabled in all cases of failed upgrades?</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/14685</link><guid isPermaLink="true">https://forum.netxms.org/post/14685</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Thu, 14 Aug 2014 18:37:22 GMT</pubDate></item><item><title><![CDATA[Reply to Problem with centralized agent upgrade on Thu, 14 Aug 2014 14:39:51 GMT]]></title><description><![CDATA[<p dir="auto">I didn't saw any file locks on NetXMS files. But when I set "EnableWatchdog = no" the update works!<br />
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.</p>
<hr />
<p dir="auto"><img src="/assets/uploads/files/smf/0000000001934-nxagentd-processes.png" alt="nxagentd-processes.png" class="img-markdown  img-fluid" width="1376" height="40" /></p>
]]></description><link>https://forum.netxms.org/post/14683</link><guid isPermaLink="true">https://forum.netxms.org/post/14683</guid><dc:creator><![CDATA[user54119]]></dc:creator><pubDate>Thu, 14 Aug 2014 14:39:51 GMT</pubDate></item><item><title><![CDATA[Reply to Problem with centralized agent upgrade on Thu, 14 Aug 2014 10:52:34 GMT]]></title><description><![CDATA[<p dir="auto">According to trace, installer was unable to rewrite some files because of sharing violation - system didn't allow rewriting them as they was already open (presumably by some process). Looks like nxagentd.exe didn't exit before upgrade. I'll try to simulate this in my network.</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/14678</link><guid isPermaLink="true">https://forum.netxms.org/post/14678</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Thu, 14 Aug 2014 10:52:34 GMT</pubDate></item><item><title><![CDATA[Reply to Problem with centralized agent upgrade on Mon, 11 Aug 2014 10:35:21 GMT]]></title><description><![CDATA[<p dir="auto">I also tried with deactivated virus scan, same result.<br />
With Sysinternals ProcessMonitor I can see the update process starts (nxagent-1.2.16-x64.exe and nxagent-1.2.16-x64.tmp).<br />
Maybe the attachted ProcessMonitor trace can help you with troubleshooting (in csv format).</p>
<hr />
<p dir="auto"><a href="/assets/uploads/files/smf/0000000001905-Logfile.CSV">Logfile.CSV</a></p>
]]></description><link>https://forum.netxms.org/post/14644</link><guid isPermaLink="true">https://forum.netxms.org/post/14644</guid><dc:creator><![CDATA[user54119]]></dc:creator><pubDate>Mon, 11 Aug 2014 10:35:21 GMT</pubDate></item><item><title><![CDATA[Reply to Problem with centralized agent upgrade on Sun, 10 Aug 2014 20:31:26 GMT]]></title><description><![CDATA[<p dir="auto">Hi Victor,</p>
<p dir="auto">they have the same problem that i have for the past versions.<br />
the agent is downloading the respected agent, stops the current agent but the installation fails.<br />
here is my post:<br />
<a href="/post/13347">https://www.netxms.org/forum/general-support/agent-deployment-2948/msg13347/#msg13347</a></p>
<p dir="auto">Best Regards,<br />
Lindeamon</p>
]]></description><link>https://forum.netxms.org/post/14639</link><guid isPermaLink="true">https://forum.netxms.org/post/14639</guid><dc:creator><![CDATA[lindeamon]]></dc:creator><pubDate>Sun, 10 Aug 2014 20:31:26 GMT</pubDate></item><item><title><![CDATA[Reply to Problem with centralized agent upgrade on Sun, 10 Aug 2014 13:09:05 GMT]]></title><description><![CDATA[<p dir="auto">I see maybe the same problem on Windows 64bit nodes (Win2012 R2, Win7, Win8.1):<br />
When I start agent upgrade from the NetXMS console in package manager (V1.2.15 to V1.2.16):</p>
<ul>
<li>agent is stopped on node</li>
<li>New install package is uploaded to the node</li>
<li>Windows Eventlog: Source RestartManger, ID 10006: Application or service ‘nxagentd’ could not be shut down</li>
<li>Package Deployment Monitor (after a few minutes): Cannot start package deployment: Request timed out</li>
<li>Agent is not updated and not started again</li>
<li>On WinXP 32bit no problem</li>
</ul>
<p dir="auto">In agent event-log (DebugLevel=9):</p>
<pre><code>[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
</code></pre>
<p dir="auto">Now I have to update the agents manually</p>
]]></description><link>https://forum.netxms.org/post/14638</link><guid isPermaLink="true">https://forum.netxms.org/post/14638</guid><dc:creator><![CDATA[user54119]]></dc:creator><pubDate>Sun, 10 Aug 2014 13:09:05 GMT</pubDate></item></channel></rss>