<?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[Unable to check open ports - Unable to check service status due to agent or comm]]></title><description><![CDATA[<p dir="auto">I am currently having problems checking open ports with the Network Service Object.</p>
<p dir="auto">OS: Ubuntu 16.04.5 LTS<br />
NetXMS: 2.2.10<br />
NxAgent: 2.2.10<br />
CPU: 4 Cores<br />
RAM: 4GB</p>
<p dir="auto">I have installed the SubAgent PORTCHECK and it loads successfully. But every device the port check returns with the error "Unable to check service status due to agent or communication error".</p>
<p dir="auto">I have checked,</p>
<ul>
<li>Agent is running</li>
<li>Firewall</li>
<li>NMAP on server returns open ports</li>
<li>Reboot Server</li>
<li>Restart NetXMS and NXAgent service</li>
</ul>
<p dir="auto"> </p>
<p dir="auto">NxAgent Output</p>
<blockquote>
<p dir="auto">2018.12.18 10:42:09.195 Log file opened (rotation policy 2, max size 4194304)<br />
2018.12.18 10:42:09.196 *D* Log rotation policy set to 2 (size=16777216, count=4)<br />
2018.12.18 10:42:09.196 *I* Core agent version 2.2.10<br />
2018.12.18 10:42:09.196 *I* Additional configs was loaded from /etc/nxagentd.conf.d<br />
2018.12.18 10:42:09.196 *I* Debug level set to 0<br />
2018.12.18 10:42:09.196 *I* Data directory: /var/lib/netxms<br />
2018.12.18 10:42:09.196 *I* File store: /tmp<br />
2018.12.18 10:42:09.212 *I* DB Library: Database driver "sqlite.ddr" loaded and initialized successfully<br />
2018.12.18 10:42:09.349 *I* Agent ID is 0e337872-fd79-45a7-9d3c-af97e58362e6<br />
2018.12.18 10:42:09.358 *I* Local host name is "<a href="http://NetXMS.office.pocketinet.com" rel="nofollow ugc">NetXMS.office.pocketinet.com</a>"<br />
2018.12.18 10:42:09.358 *I* Using system name "NetXMS"<br />
2018.12.18 10:42:10.375 *I* Subagent "Linux" (linux.nsm) loaded successfully (version 2.2.10)<br />
2018.12.18 10:42:10.377 *I* Subagent "PORTCHECK" (portcheck.nsm) loaded successfully (version 2.2.10)<br />
2018.12.18 10:42:11.382 *I* Listening on socket 0.0.0.0:4700<br />
2018.12.18 10:42:11.382 *I* Listening on socket [::]:4700<br />
2018.12.18 10:42:12.383 *I* NetXMS Agent started<br />
2018.12.18 11:12:02.051 *I* NetXMS Agent stopped</p>
</blockquote>
<p dir="auto">Node Status Poll</p>
<blockquote>
<p dir="auto">[20.12.2018 08:44:57] **** Poll request sent to server ****<br />
[20.12.2018 08:44:57] Poll request accepted<br />
[20.12.2018 08:44:57] Starting status poll for node Unifi Controller<br />
[20.12.2018 08:44:57]    Starting status poll on interface unknown<br />
[20.12.2018 08:44:57]       Current interface status is NORMAL<br />
[20.12.2018 08:44:57]       Starting ICMP ping<br />
[20.12.2018 08:44:57]       Interface is NORMAL for 2421 polls (1 poll required for status change)<br />
[20.12.2018 08:44:57]       Interface status after poll is NORMAL<br />
[20.12.2018 08:44:57]    Finished status poll on interface unknown<br />
[20.12.2018 08:44:57]    Starting status poll on network service Port 8080<br />
[20.12.2018 08:44:57]       Current service status is UNKNOWN<br />
[20.12.2018 08:44:57]       Polling service from node NetXMS [IP REDACTED]<br />
[20.12.2018 08:44:57]       Unable to check service status due to agent or communication error<br />
[20.12.2018 08:44:57]    Finished status poll on network service Port 8080<br />
[20.12.2018 08:44:57]    Starting status poll on network service HTTP<br />
[20.12.2018 08:44:57]       Current service status is UNKNOWN<br />
[20.12.2018 08:44:57]       Polling service from node NetXMS [IP REDACTED]<br />
[20.12.2018 08:44:57]       Unable to check service status due to agent or communication error<br />
[20.12.2018 08:44:57]    Finished status poll on network service HTTP<br />
[20.12.2018 08:44:57]    Starting status poll on network service test 10001<br />
[20.12.2018 08:44:57]       Current service status is UNKNOWN<br />
[20.12.2018 08:44:57]       Polling service from node NetXMS [IP REDACTED]<br />
[20.12.2018 08:44:57]       Unable to check service status due to agent or communication error<br />
[20.12.2018 08:44:57]    Finished status poll on network service test 10001<br />
[20.12.2018 08:44:57]    Starting status poll on network service ssh<br />
[20.12.2018 08:44:57]       Current service status is UNKNOWN<br />
[20.12.2018 08:44:57]       Polling service from node NetXMS [IP REDACTED]<br />
[20.12.2018 08:44:57]       Unable to check service status due to agent or communication error<br />
[20.12.2018 08:44:57]    Finished status poll on network service ssh<br />
[20.12.2018 08:44:57] Node is connected<br />
[20.12.2018 08:45:01] Finished status poll for node Unifi Controller<br />
[20.12.2018 08:45:01] Node status after poll is NORMAL<br />
[20.12.2018 08:45:01] **** Poll completed successfully ****</p>
</blockquote>
<p dir="auto">I have checked these forum posts and either its about checking web pages or I have already done all the things.<br />
<a href="https://www.netxms.org/forum/configuration/network-service/msg9702/#msg9702" rel="nofollow ugc">https://www.netxms.org/forum/configuration/network-service/msg9702/#msg9702</a><br />
<a href="https://www.netxms.org/forum/configuration/website-monitoring-using-network-service/msg16373/#msg16373" rel="nofollow ugc">https://www.netxms.org/forum/configuration/website-monitoring-using-network-service/msg16373/#msg16373</a><br />
<a href="/post/7382">https://www.netxms.org/forum/general-support/cannot-figure-web-site-monitor/msg7382/#msg7382</a></p>
<p dir="auto">Any help would be appreciated.<br />
Jarred</p>
]]></description><link>https://forum.netxms.org/topic/5772/unable-to-check-open-ports-unable-to-check-service-status-due-to-agent-or-comm</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 17:55:04 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/5772.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 20 Dec 2018 17:20:30 GMT</pubDate><ttl>60</ttl></channel></rss>