Are you querying the agent from the same computer it’s running on or is it elsewhere on the network?
If it’s on another machine then you’ll need to make sure the firewall on the machine running the agent isn’t blocking the port. Assuming you’re using the oS firewall run “yast firewall”.
Otherwise, speaking very generally, it’s possible the reason the port isn’t open is because the agent simply failed to start. I’d look at the agent configuration or earlier in the log files for indications that that may be what happened.
It may be worthwhile here to mention the option to use netcat as a
troubleshooting tool in this case to ensure routes, netmasks to some
extent, and most-oftn, firewalls. For example to setup a listening TCP
port on port 9998:
netcat -l 9998
To connect to that port on that remote box use the following to verify a
connection is possible:
netcat -zv <remoteBoxIPOrDNSName> 9998
If it works properly you should see the following or something similar
with ‘open’ there:
mybox:~> netcat -zv remotebox 9998
remotebox [188.8.131.52] 9998 (?) open
If you were to run the second netcat command on the box with the port
open it should connect unless your firewall is REALLY restrictive, where
using it on a remote box will not connect with most firewalls by default
because that is a bigger security risk.
| I was trying to install a monitoring agent and I got this error …
| – Sleeping for 3 seconds
| 4 - Verifying Agent Installation
| - Checking communications
| Port 9998 is closed the agent will not work
| - Checking file dependencies
| How do I open port 9998?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org