I think smbd is running. The STATUS..LCK file is not used with samba when
you compile from sources, so, it much be something in the samba startup
script.
Everything you show:
1. Address in use
2. netstat -a
3. messages
4. log.smb
All indicate that samba is running.
Try netstat -ap | grep bios
and see if you get:
tcp 0 0 *:netbios-ssn *:* LISTEN 1458/smbd
^^^^
Joel
On Tue, Jan 01, 2002 at 08:32:05PM -0800, Gerry Snyder
wrote:> I need help. For over a year I have been running SAMBA 2.05a under
> RedHat 6.1 (kernel 2.2.x) without problem. Then a couple days ago a
> power glitch crashed my system (UPS not powerful enough any more). Now
> SAMBA is not running. Here are the symptoms:
>
> As RedHat is starting up, both smbd and nmbd are listed as successful.
>
> /var/log/messages indicates:
>
> Dec 30 13:19:45 we-24-126-201-41 smb: smbd startup succeeded
> Dec 30 13:19:45 we-24-126-201-41 smb: nmbd startup succeeded
>
> The Samba web administration tool shows that Samba could not open the
> STATUS..LCK file. I touched that file and made it world everything. The
> error message went away the next time I hit the Start smbd button, but
> it didn't start.
>
> /var/log/samba/log.smb shows:
>
> [2001/12/30 13:19:44, 1] smbd/server.c:main(628)
> smbd version 2.0.5a started.
> Copyright Andrew Tridgell 1992-1998
> [2001/12/30 13:19:44, 1] smbd/files.c:file_init(216)
> file_init: Information only: requested 10000 open files, 1014 are
> available.
> [2001/12/30 13:19:45, 0] lib/util_sock.c:open_socket_in(886)
> bind failed on port 139 socket_addr=0.0.0.0 (Address already in use)
>
> I suspect that this is the real problem, but I don't know what to do
> about it. I keep getting the same address in use error with all further
> tries to start. I tried netstat.
>
> netstat -a does not show anything else listening on port 139
> specifically, and looking for netbios connections gave:
>
> # netstat -a | grep netbios
> tcp 0 0 192.168.40.:netbios-ssn *:*
> LISTEN
> udp 0 0 192.168.1.1:netbios-dgm
> *:*
> udp 0 0 192.168.1.11:netbios-ns
> *:*
> udp 0 0 *:netbios-dgm
> *:*
> udp 0 0 *:netbios-ns
> *:*
> udp 0 0 192.168.40.:netbios-dgm
> *:*
> udp 0 0 192.168.40.1:netbios-ns
> *:*
> udp 0 0 *:netbios-dgm
> *:*
> udp 0 0 *:netbios-ns
> *:*
>
> Anyone have a guess as to what a system crash could have done to cause
> these symptoms, and what I can do to recover?
>
_______________________________________________
Linux-users mailing list
Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
----- End forwarded message -----