Page tree
Skip to end of metadata
Go to start of metadata

If Uptime Infrastructure Monitor cannot bind to a specific port, it will write an error to the uptime.log file and you will not be able to connect to the Uptime Infrastructure Monitor web interface.  This exception (see example below) appears when starting the Uptime Infrastructure Monitor data collector service under the following scenarios:

  1. The Uptime Infrastructure Monitor data collector is already running or is using the wrong port.  In this case, open the httpd.conf file in a text editor, find the Listen xxxx line and set xxxx to the appropriate port number.
  2. Another service is using the Uptime Infrastructure Monitor data collector port (9995 default).  In this case, determine which service is using the same port and adjust port settings to resolve the conflict.

Example Exception:

2014-11-28 13:29:54,467 FATAL (Uptime:277) - Uptime Infrastructure Monitor cannot run, exiting... Address already in use at Method) at Source) at Source) at (Unknown Source) at (Unknown Source) at com.uptimesoftware.uptime.dataservice.ProtocolListener. ( at com.uptimesoftware.uptime.base.UptimeThreadManager.startDataService(UptimeThread at com.uptimesoftware.uptime.base.UptimeThreadManager.startBasicThreadsOnly(UptimeT at com.uptimesoftware.uptime.base.UptimeInstance.runUptime( at com.uptimesoftware.uptime.base.Uptime.main( at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.zerog.lax.LAX.launch(DashoA8113) at com.zerog.lax.LAX.main(DashoA8113)