Clovertech

Reply To: Unable to bind tcp/ip socket: Address already in use

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › Unable to bind tcp/ip socket: Address already in use › Reply To: Unable to bind tcp/ip socket: Address already in use

April 10, 2006 at 8:25 pm #58689
Traci Zee
Participant

    I had this problem last week on my Dev system.  I’m running 3.7.1 on Sun Solaris.

    If I tried to start the offending thread it would fail with ‘Address already in use’ AND the process would die, taking all my other connections in the process down with it.

    netstat -a | grep

    returned ESTABLISHED for the VPN Client IP that happened to be running the NetMonitor application.  If I brought the NetMonitor GUI down, verified the port wasn’t in use, I could bring up the thread using the command line.  

    Neither Cloverleaf Tech Support or my corporate network Ops could explain what/why this happened.  

    I changed the port to resolve.  BTW – the port that I was using was 44140.  I’d be interested if yours was the same or similar range.

    The instructions to look at port ranges that Steve provided didn’t work for Solaris.

    Traci Zee

    770.844.9242