Related to:

INFO: CONMGR Details: tryListen(); None; 98; -856; bind() failed on fd 4, port 7032; 

FATAL: NETOBJECTS ConManager : non recoverable error, exiting

Problem:

The FATAL entry appearing in the netprobe log indicates that the netprobe cannot be restarted. To understand why this is the case, the adjacent entry above provides information that the netprobe failed to connect to port 7032

Possible cause(s):

This error occurred, when the netprobe that is being attempted to start up, is using the same port that has already been assigned to another process.

Possible solution(s):

In order to resolve this the netprobe will need to run on a different port number. Using the below command on Linux can help locate and verify the process that is using the same port number.

netstat -tulpn | grep <portnumber>

Once the amendment to the port number has been made, the netprobe will startup as normal.

If you need further help:

• Please contact our support team via the chat service box on any of our websites or raise a support request.
  
• Make sure you provide us with:
  • Background of the issue or request.
  • Use cases, requirements, business impact, etc.
  • Encountered error messages.
  • Log files or diagnostic files.
  • Screenshots.
  • And other important information relevant to your inquiry.