Network Port conflicts

Identifying potential port conflicts Port 8080,8005, 48081 and 48082 are the default ports used by the Address Book Server to listen for incoming connections. If you encounter problems with either Address Book Server or other services not starting, you can identify the problems via the following com- mands List all the processes listening on TCP/IP connections as shown here using netstat.

polaris:~ alex$ sudo bash
Password:
bash-3.2# netstat -an |grep LISTEN
tcp6       0      0  *.3689                 *.*                    LISTEN     
tcp4       0      0  *.3689                 *.*                    LISTEN     
tcp4       0      0  127.0.0.1.8005         *.*                    LISTEN     
tcp46      0      0  *.48082                *.*                    LISTEN     
tcp46      0      0  *.48081                *.*                    LISTEN     
tcp46      0      0  *.8080                 *.*                    LISTEN     
tcp4       0      0  127.0.0.1.49156        *.*                    LISTEN     
tcp4       0      0  127.0.0.1.49155        *.*                    LISTEN     
tcp46      0      0  *.49154                *.*                    LISTEN     
tcp4       0      0  *.22                   *.*                    LISTEN     
tcp6       0      0  *.22                   *.*                    LISTEN     
tcp4       0      0  127.0.0.1.631          *.*                    LISTEN     
tcp6       0      0  ::1.631                *.*                    LISTEN     
bash-3.2#

To identify which process is listening on a particular port, you can use the lsof command. Please note the lsof command should be used from a root shell. The example below shows typical output expected for Address Book Server.

polaris:~ alex$ sudo bash
Password:
bash-3.2# lsof -i :8080
COMMAND PID USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME
java     82 root   55u  IPv6 0xffffff800c5c9600      0t0  TCP *:http-alt (LISTEN)
bash-3.2# 

The same commands can be used to identify processes which are using the same ports as Address Book Server. In this case, Address Book Server should be reconfigured to use alternate ports. Once a conflict has been identified there are two options. Either change the offending application to use an alternate port, or reconfigure Address Book Server to do the same. Instruction on how to get Address Book Server to use an alternate port are available here : Network Port Conflicts