Support Centre

Find articles, help and advice.

Welcome, Guest Login

Support Center

BES - AlertServer Connection Failing

Last Updated: Apr 12, 2018 10:23AM UTC
If trying to telnet to port 40000, you may come across and error that looks something like this:

"# telnet localhost 40000
telnet: connect to address Connection refused
Trying ::1...
telnet: Unable to connect to remote host: Network is unreachable"

This error can appear due to multitude of reasons. The most common ones are:
  • Only one connection can be active at once, having any more that 1 will cause any further connections to fail.
  • The last person to connect to the AlertServer didn’t close the connection properly
  • Issue with AlertServer itself
  • First thing to try is to see if it is an issue with AlertServer/the port. To do this, try to telnet to the Event daemon on port 35000. This will not have the same options as AlertServer but you should still be able to connect.
telnet localhost 35000
  • Check to see if anyone else has an open connection to the port/AlertServer at the current time
  • Next we want to see if AlertServer is actually listening on port 40000. To check this run the command:
Netstat -anp | grep 40000

Doing this will return a PID. Once you have the PID, run the command:

Ps -ef | grep <PID>

This will then provide the process. If for any reason this fails, continue to next step. If you obtain the process, sent the results over to Interlink Software Support with steps on what you have done.
  • If none of the above work, then it might be a good idea to recycle AlertServer. This should only be done if all other steps have failed to work. Recycling AlertServer will cause BES to go down for a short while, so proceed with caution.
ppStop -n AlertServer
ppStart -n AlertServer

Contact Us
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found