Still getting binding socket already in use

[Rish i D Mack]

So  after I Connected with My client, I got this.

 

Dec 30 09:10:26: LISTEN: #0 now listening on port 1234                         

Dec 30 09:10:26: LISTEN: #241 now listening on port 3000                       

Dec 30 09:10:26: *** Binding listening socket: Address already in use          

Dec 30 09:14:14: ACCEPT: #-2 on port 1234 from 186-45-184-36.dynamic.tstt.net.tt

, port 64199                                                                   

Dec 30 09:14:24: CONNECTED: Wizard (#2) on port 1234 from 186-45-184-36.dynamic.

tstt.net.tt, port 64199                                                        

Killed                                                                         

Why was it killed? This is weard.

 

[Loufah]

Look at the system logs - they may have info about why the process was killed. Most likely reason on a Linux system is that there's too much virtual memory in use by this or other processes and the "OOM killer" picks a process to kill.

To see why it can't bind to port 3000, run "sudo netstat -t -p|grep 3000" and see what process is using that port.