bind failed

bind failed

Post by Julian Harr » Thu, 23 Feb 1995 09:16:50



Hi all.

I've got this server running on DEC Ultrix 4.3A and occasionally when I
call bind, it fails (port already bound).

I do a netstat -a and sure enough, there are a couple of listens:

tcp        0      0  csbk.421               dstaff07.1553          FIN_WAIT_1
tcp        0      0  csbk.421               dstaff07.1553          FIN_WAIT_1

At this point, I have no live processes that bound to that port.

What do these mean? I thought that as soon as a process that called bind
died, the bind would be unbound. It seems to just 'time out' after a while
sometimes instead.

Thanks for any advice anyone can offer!
.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .
Microsoft is not the answer.                    >  Julian Harris, Programmer   >
Microsoft is the question.                     >  Comp. Sci. Dept.     x8915  >
                                              >  The University of Auckland  >

 
 
 

bind failed

Post by Matthew Robins » Sat, 04 Mar 1995 15:51:57


: I've got this server running on DEC Ultrix 4.3A and occasionally when I
: call bind, it fails (port already bound).

: tcp        0      0  csbk.421               dstaff07.1553     FIN_WAIT_1
: tcp        0      0  csbk.421               dstaff07.1553     FIN_WAIT_1

The problem is the FIN_WAIT_1 status.  This is due an 'untidy' shutdown of the
previous connections on thos ports.  The DEC has sent a FINISH packet to the
other host, but has received no acknowledge back, probably because the other
host has shutdown the connection and terminated the client program before
finishing the shutdown process.

--
------------------------------------------------------------------------------
Matthew Robinson                                                         "OT!"
Senior Customer Service Rep.

                  "Never,.. NEVER... quit" (Winston Churchill)
---------------------------------o O O O o------------------------------------

 
 
 

1. samba error: bind failed on port 139 socket_addr=0.0.0.0 (address already in use)

hello,

when starting samba i receive the following error in

/var/log/log.smb

bind failed on port 139 socket_addr=0.0.0.0 (address already in use)

smbclient on my own and other machines work fine, but using w95 and wfw to
access the bsd server failed .

hope you can help.

greetings from germany

uwe fechner


2. Help me with my OPL3 sound card configuartion

3. bind() fails when running program second time

4. Need help with AIX and Apache

5. bind() failed: address already in use

6. Linux setup with SMC EtherPower 8432

7. bind fail

8. Newbie questions

9. HELP: bind() failed; Address already in use

10. #main ncftpd :: bind failed -- waiting 10 : Address already in use.

11. bind() fails with errno == EAGAIN

12. Help: why bind() failed by my socket program?

13. bind() failed!