You run into an issue where Nastel MQ agents are displayed as being down or in an unknown state, but the agent processes are actually running fine. For example, in UNIX you see the following commands:
- ps -ef|grep nsq: shows nsqmq, nsqpub and nsqmsg processes are running
- netstat -an|grep 5010: shows that the agent listens on port 5010 as an example
It is suggested to perform connectivity tests between the agent and the workgroup server. Listed below are tests you can perform. As an example, "wgshost" is used as the name of the workgroup server host and "mqhost" is the name of the agent host.
On the wgshost machine
Run the following using a command line:
1 nslookup mqhost<
Returns IP address of the agent box.
Use resulting IP of agent machine or the "mqIP" for next test.
2 tracert mqIP (Windows version)
traceroute mqIP (UNIX)
Confirm that traffic can be routed from one node to the other.
3 ping mqIP
This can sometimes be unsuccessful because the ping service/port is disabled or closed on the target machine.
4 telnet mqIP 5010
Where 5010 is default port used by the MQ agent.
If the telnet client does not respond or says "Connection refused" there could be a firewall issue and network engineers and/or network administrators should troubleshoot.
If telnet connects then user can press the key combination "Ctrl+]" to get to the telnet prompt.
In the telnet prompt, type "status" to see connection status.
User can type "close" to close connection of the telnet client and Nastel MQ agent.
On the mqhost machine
Run a similar set of tests using a command line:
1 nslookup wgshost
2 tracert wgsIP
3 ping wgsIP
4 telnet wgsIP 4010
Where 4010 is default port used by the workgroup server.
Please note that secure shell 'ssh' can be used instead of telnet as in: ssh -p 4010 wgsIP
-bash-4.1$ ssh -p 4217 188.8.131.52
ssh: connect to host 184.108.40.206 port 4217: Connection timed out
You can also use the client test utility, nsqcl. See the following guides for more information: