<?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[Commnunication error NetXMS Server Version 3.6.300]]></title><description><![CDATA[<p dir="auto">Hey, there. Unexpected communication error NetXMS Server Version 3.6.300. I attach a screenshot of the popup window.</p>
<p dir="auto">Any idea how to fix this communication issue?</p>
<p dir="auto">ping command output between netxms client and server:</p>
<p dir="auto">icmp_seq=1 ttl=63 time=0.492 ms<br />
icmp_seq=2 ttl=63 time=0.314 ms<br />
icmp_seq=3 ttl=63 time=0.331 ms<br />
icmp_seq=4 ttl=63 time=0.217 ms</p>
<p dir="auto">Thanks in Advance</p>
<hr />
<p dir="auto"><img src="/assets/uploads/files/smf/0000000005356-netxmscommunicationerror.png" alt="netxmscommunicationerror.png" class="img-markdown  img-fluid" width="610" height="175" /></p>
]]></description><link>https://forum.netxms.org/topic/6812/commnunication-error-netxms-server-version-3.6.300</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 15:21:40 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/6812.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 12 Dec 2020 20:10:13 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Commnunication error NetXMS Server Version 3.6.300 on Wed, 23 Dec 2020 07:28:43 GMT]]></title><description><![CDATA[<p dir="auto">Most likely it is caused by bug we have fixed recently in development branch. Fix should be included into upcoming 3.7 release.</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/29118</link><guid isPermaLink="true">https://forum.netxms.org/post/29118</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Wed, 23 Dec 2020 07:28:43 GMT</pubDate></item><item><title><![CDATA[Reply to Commnunication error NetXMS Server Version 3.6.300 on Wed, 16 Dec 2020 16:23:12 GMT]]></title><description><![CDATA[<p dir="auto">10 lines of log are not enough - they span for less then 0.1 seconds. Let's improve the process:</p>
<p dir="auto">nxadm -c "debug client.* 6"<br />
nxadm -c "logmark"<br />
&lt;replicate the error&gt;<br />
nxadm -c "debug client.* -1"</p>
<p dir="auto">This will produce<br />
2020.12.16 18:20:52.119 *D* [                   ] ******* MARK *******<br />
line to server log. We need the log file from that mark to the end of the file.</p>
]]></description><link>https://forum.netxms.org/post/29080</link><guid isPermaLink="true">https://forum.netxms.org/post/29080</guid><dc:creator><![CDATA[Filipp Sudanov]]></dc:creator><pubDate>Wed, 16 Dec 2020 16:23:12 GMT</pubDate></item><item><title><![CDATA[Reply to Commnunication error NetXMS Server Version 3.6.300 on Wed, 16 Dec 2020 14:52:50 GMT]]></title><description><![CDATA[<p dir="auto">Hi, Fillip. I followed your directions. Note: I had to put &lt;ip address&gt; instead our ip address for security reasons.</p>
<p dir="auto">josemb@hpserver1:~$ nxadm -c "debug client.* 6"<br />
Debug level for tag "client.*" set to 6</p>
<p dir="auto">osemb@hpserver1:~$ tail -n 10 /var/log/netxmsd<br />
2020.12.16 14:45:41.555 *D* [client.session.0   ] Sending compressed message CMD_OBJECT_UPDATE (560 bytes)<br />
2020.12.16 14:45:41.556 *D* [client.session.0   ] Scheduling update for object &lt;ip address&gt; [23185]<br />
2020.12.16 14:45:41.556 *D* [client.session.0   ] Scheduling update for object &lt;ip address&gt; [25341]<br />
2020.12.16 14:45:41.556 *D* [client.session.0   ] Sending update for object &lt;ip address&gt; [23185]<br />
2020.12.16 14:45:41.557 *D* [client.session.0   ] Sending compressed message CMD_OBJECT_UPDATE (584 bytes)<br />
2020.12.16 14:45:41.557 *D* [client.session.0   ] Sending update for object &lt;ip address&gt; [25341]<br />
2020.12.16 14:45:41.558 *D* [client.session.0   ] Sending compressed message CMD_OBJECT_UPDATE (584 bytes)<br />
2020.12.16 14:45:41.620 *D* [client.session.0   ] Scheduling update for object &lt;ip address&gt; [33950]<br />
2020.12.16 14:45:41.620 *D* [client.session.0   ] Sending update for object &lt;ip address&gt; [33950]<br />
2020.12.16 14:45:41.623 *D* [client.session.0   ] Sending compressed message CMD_OBJECT_UPDATE (1448 bytes)</p>
<p dir="auto">josemb@hpserver1:~$ nxadm -c "debug client.* -1"<br />
Debug level for tag "client.*" set to default</p>
<p dir="auto">Thanks in advance.</p>
]]></description><link>https://forum.netxms.org/post/29077</link><guid isPermaLink="true">https://forum.netxms.org/post/29077</guid><dc:creator><![CDATA[jbriseno]]></dc:creator><pubDate>Wed, 16 Dec 2020 14:52:50 GMT</pubDate></item><item><title><![CDATA[Reply to Commnunication error NetXMS Server Version 3.6.300 on Wed, 16 Dec 2020 12:00:30 GMT]]></title><description><![CDATA[<p dir="auto">Let's try to get some more debug information. Can you please run the following command in the command line on the server:</p>
<pre><code>nxadm -c "debug client.* 6"
</code></pre>
<p dir="auto">This will increase debug level for log messages related to communication with the console.<br />
Then try to open IP neighbors window and wait for the error.<br />
When the error shows, turn off the additional debugging</p>
<pre><code>nxadm -c "debug client.* -1"
</code></pre>
<p dir="auto">and send us server log file</p>
]]></description><link>https://forum.netxms.org/post/29069</link><guid isPermaLink="true">https://forum.netxms.org/post/29069</guid><dc:creator><![CDATA[Filipp Sudanov]]></dc:creator><pubDate>Wed, 16 Dec 2020 12:00:30 GMT</pubDate></item><item><title><![CDATA[Reply to Commnunication error NetXMS Server Version 3.6.300 on Mon, 14 Dec 2020 16:35:24 GMT]]></title><description><![CDATA[<p dir="auto">Hi, Filipp. First thanks for your help. Second, the Desktop Managment tool works fine until I want to open the Neighbors IP window of one our major network routers. Then the SWT software get freezed. After few seconds appeared a popup window with the following message: SWT is not responding. I attached a screenshot of it. I checked the netXMS server log out. I pasted the latest 10 lines of this file. I pasted the latest ten lines of the SWT log file, as well. Finally, the netXMS  server did not restart in that moment.</p>
<p dir="auto">josemb@hpserver1:/var/log$ tail -n 10 netxmsd<br />
2020.12.14 14:31:05.347 *E* [watchdog           ] Thread "Syncer Thread" does not respond to watchdog thread<br />
2020.12.14 14:31:23.209 *I* [watchdog           ] Thread "Syncer Thread" returned to running state<br />
2020.12.14 14:33:05.348 *E* [watchdog           ] Thread "Syncer Thread" does not respond to watchdog thread<br />
2020.12.14 14:33:25.513 *I* [watchdog           ] Thread "Syncer Thread" returned to running state<br />
2020.12.14 14:55:25.354 *E* [watchdog           ] Thread "Syncer Thread" does not respond to watchdog thread<br />
2020.12.14 14:55:39.732 *I* [watchdog           ] Thread "Syncer Thread" returned to running state<br />
2020.12.14 15:33:45.365 *E* [watchdog           ] Thread "Syncer Thread" does not respond to watchdog thread<br />
2020.12.14 15:34:06.304 *I* [watchdog           ] Thread "Syncer Thread" returned to running state<br />
2020.12.14 16:04:25.376 *E* [watchdog           ] Thread "Syncer Thread" does not respond to watchdog thread<br />
2020.12.14 16:04:25.968 *I* [watchdog           ] Thread "Syncer Thread" returned to running state</p>
<p dir="auto">########################</p>
<p dir="auto">Desktop Manager tool log file</p>
<p dir="auto">!MESSAGE Creating keepalive timer</p>
<p dir="auto">!ENTRY org.netxms.ui.eclipse.console 1 0 2020-12-14 10:14:45.541<br />
!MESSAGE Login job completed</p>
<p dir="auto">!ENTRY org.netxms.ui.eclipse.alarmviewer 1 0 2020-12-14 10:17:45.105<br />
!MESSAGE Skipping alarm tray popup creation - too many consecutive alarms</p>
<p dir="auto">!ENTRY org.netxms.ui.eclipse.alarmviewer 1 0 2020-12-14 10:23:13.550<br />
!MESSAGE Skipping alarm tray popup creation - too many consecutive alarms</p>
<p dir="auto">I hope these help.</p>
<p dir="auto">Best regards.</p>
<p dir="auto">Jose</p>
<hr />
<p dir="auto"><img src="/assets/uploads/files/smf/0000000005357-swtnotresponding1.png" alt="swtnotresponding1.png" class="img-markdown  img-fluid" width="563" height="179" /></p>
]]></description><link>https://forum.netxms.org/post/29053</link><guid isPermaLink="true">https://forum.netxms.org/post/29053</guid><dc:creator><![CDATA[jbriseno]]></dc:creator><pubDate>Mon, 14 Dec 2020 16:35:24 GMT</pubDate></item><item><title><![CDATA[Reply to Commnunication error NetXMS Server Version 3.6.300 on Mon, 14 Dec 2020 09:42:16 GMT]]></title><description><![CDATA[<p dir="auto">Was it one-time occurence or it happens often? Currently the probocol between management console and server is not tolerant to interruptions and console needs to be restarted.<br />
Is there anything is netxms server log at that moment? Did server restart that moment?</p>
]]></description><link>https://forum.netxms.org/post/29038</link><guid isPermaLink="true">https://forum.netxms.org/post/29038</guid><dc:creator><![CDATA[Filipp Sudanov]]></dc:creator><pubDate>Mon, 14 Dec 2020 09:42:16 GMT</pubDate></item></channel></rss>