John M. Purser
2003-Aug-17 22:08 UTC
[Samba] smbd won't run - Error message says port 139 in use
Samba was working well but I changed the host allow section of smb.conf and it stopped. I changed it back and restarted and got this error message in log.smbd [2003/08/17 12:15:26, 0] lib/util_sock.c:open_socket_in(789) bind failed on port 139 socket_addr = 0.0.0.0. Error = Address already in use I have a really simple smb.conf: # Samba config file created using SWAT # from localhost (127.0.0.1) # Date: 2003/08/17 11:50:06 # Global parameters [global] workgroup = JMPURSER.NET interfaces = eth0 192.168.1.40/24 encrypt passwords = Yes os level = 65 preferred master = True domain master = False hosts allow = 192.168.1.10 [test] comment = for testing only, please path = /home/samba/browse read only = No guest ok = Yes I'm running samba on Debian woody. Can anyone tell me what happened or give some trouble shooting tips on how to figure out what's going on? Thanks, John Purser
Gémes Géza
2003-Aug-17 22:14 UTC
[Samba] smbd won't run - Error message says port 139 in use
John M. Purser ?rta:>Samba was working well but I changed the host allow section of smb.conf and >it stopped. I changed it back and restarted and got this error message in >log.smbd > >[2003/08/17 12:15:26, 0] lib/util_sock.c:open_socket_in(789) > bind failed on port 139 socket_addr = 0.0.0.0. > Error = Address already in use > >I have a really simple smb.conf: > ># Samba config file created using SWAT ># from localhost (127.0.0.1) ># Date: 2003/08/17 11:50:06 > ># Global parameters >[global] > workgroup = JMPURSER.NET > interfaces = eth0 192.168.1.40/24 > encrypt passwords = Yes > os level = 65 > preferred master = True > domain master = False > hosts allow = 192.168.1.10 > >[test] > comment = for testing only, please > path = /home/samba/browse > read only = No > guest ok = Yes > >I'm running samba on Debian woody. Can anyone tell me what happened or give >some trouble shooting tips on how to figure out what's going on? > >Thanks, > >John Purser > > > > >Most probably your old samba instance is still runing, I've got somehing similar with apache. Try ps auxw | grep smbd | grep -v grep and ps auxw | grep nmbd | grep -v grep it will show you if is there any instances runing, kill them and start samba again. Good Luck! Geza Gemes
Joel Hammer
2003-Aug-18 00:40 UTC
[Samba] smbd won't run - Error message says port 139 in use
Or, inetd is starting samba for you. Joel rOn Sun, Aug 17, 2003 at 04:08:04PM -0600, John M. Purser wrote:> Samba was working well but I changed the host allow section of smb.conf and > it stopped. I changed it back and restarted and got this error message in > log.smbd > > [2003/08/17 12:15:26, 0] lib/util_sock.c:open_socket_in(789) > bind failed on port 139 socket_addr = 0.0.0.0. > Error = Address already in use > > I have a really simple smb.conf: > > # Samba config file created using SWAT > # from localhost (127.0.0.1) > # Date: 2003/08/17 11:50:06 > > # Global parameters > [global] > workgroup = JMPURSER.NET > interfaces = eth0 192.168.1.40/24 > encrypt passwords = Yes > os level = 65 > preferred master = True > domain master = False > hosts allow = 192.168.1.10 > > [test] > comment = for testing only, please > path = /home/samba/browse > read only = No > guest ok = Yes > > I'm running samba on Debian woody. Can anyone tell me what happened or give > some trouble shooting tips on how to figure out what's going on? > > Thanks, > > John Purser > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba