[Samba] Re: Samba 3.0.20a
pchesnut at cox.net
Wed Oct 12 20:35:05 GMT 2005
Michael Andrewjeski <mandrewjeski <at> zonelabs.com> writes:
> You've got a pid file somewhere that your start script is reading. Open
> the start script and find the location of the pid file then delete the
> file and start again.
> -----Original Message-----
> From: samba-bounces+mandrewjeski=zonelabs.com <at> lists.samba.org
> [mailto:samba-bounces+mandrewjeski=zonelabs.com <at> lists.samba.org] On
> Behalf Of PC
> Sent: Tuesday, October 11, 2005 6:59 AM
> To: samba <at> lists.samba.org
> Subject: [Samba] Samba 3.0.20a "Winbind Dead but subsys locked"
> Last week I downloaded and installed the 3.0.20a-23 release on Redhat ES
> 4 x86_64bit and noticed that I am getting the "Winbind Dead but subsys
> status on winbind service. The service seems to start corectly but
> immediately get "Winbind Dead but subsys locked" status message.
> I had been running version 3.0.20-22 64 bit version which was also
> downloaded from sambaenterprise.org
> I just noticed that this site has a 20a-24 release, I'll install it to
> see if it corrects the issue.
> Any other ideas?
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/listinfo/samba
1) I looked for the script you mentioned but no luck. Please let me know where
the script is typically located.
2) I found the fol[2005/10/12 09:20:59, 0] passdb/secrets.c:secrets_init(64)
Failed to open /etc/samba/secrets.tdb
[2005/10/12 09:20:59, 0] nsswitch/winbindd.c:main(952)
Could not initialize domain trust account secrets. Giving up
lowing errors in the /var/log/samba/winbindd.log file:
The log.winbind file look fine:
[2005/10/12 09:20:59, 1] nsswitch/winbindd.c:main(935)
winbindd version 3.0.20-SerNet-RedHat started.
Copyright The Samba Team 2000-2004
Any idea what is causing the "Failed to open /etc/samba/secrets.tdb" error?
More information about the samba