If up.time can not 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 up.time web interface. This exception (see example below) appears when starting the up.time data collector service under the following scenarios:
Example Exception:
2007-11-28 13:29:54,467 FATAL (Uptime:277) - up.time can not run, exiting... java.net.BindException: Address already in use at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(Unknown Source) at java.net.ServerSocket.bind(Unknown Source) at java.net.ServerSocket. (Unknown Source) at java.net.ServerSocket. (Unknown Source) at com.uptimesoftware.uptime.dataservice.ProtocolListener. (ProtocolListener.java:35) at com.uptimesoftware.uptime.base.UptimeThreadManager.startDataService(UptimeThread Manager.java:142) at com.uptimesoftware.uptime.base.UptimeThreadManager.startBasicThreadsOnly(UptimeT hreadManager.java:71) at com.uptimesoftware.uptime.base.UptimeInstance.runUptime(UptimeInstance.java:89) at com.uptimesoftware.uptime.base.Uptime.main(Uptime.java:275) 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) |