linux at kukkukk.com
Sat Feb 25 18:14:45 MST 2012
On Sunday 26 February 2012 00:35:47 Jason Carlson wrote:
> Is it normal to receive this warning when running just samba binary?
> [2012/02/25 16:25:46, 0] ../source4/smbd/server.c:366(binary_smbd_main)
> samba version 4.0.0alpha19-GIT-341bd82 started.
> Copyright Andrew Tridgell and the Samba Team 1992-2012
> [2012/02/25 16:25:47, 0] ../source4/smbd/server.c:461(binary_smbd_main)
> samba: using 'standard' process model
> WARNING: no socket to connect to
are you running opensuse 12.1 ?
Until now i only noticed "WARNING: no socket to connect to" on that distro.
It is _not_ samba4 related and results from GNOME-keyring usage.
/usr/lib/pkcs11/gnome-keyring-pkcs11.so contains that string
Note that this can also be seen when KDE is the used desktop.
Weeks ago i was hunting this problem on opensuse 12.1 for many days:
Samba4 was started as
./sbin/samba -i -M single -d3
after some initial messages
"WARNING: no socket to connect to"
was displayed and shortly later samba was hanging for about 3 to 5 minutes (!) in
( see http://gmplib.org/ )
possibly computing some infamous large numbers (GnuTLS ) ...
I de-installed all PKCS11 and gnome-keyring related stuff - and then
samba4 was running as expected.
"WARNING: no socket to connect to" was gone - and no hang anymore.
Lateron i re-installed the PKCS11 and gnome-keyring packages again.
Strangely enough all was still working and all my later samba4 builds
(from git) were also working.
So unfortunately i cannot really tell the difference between the initial
pkcs11 and gnome-keyring install and the de-install/re-install case.
> On Sat, Feb 25, 2012 at 2:26 AM, Andrew Bartlett <abartlet at samba.org> wrote:
> > On Fri, 2012-02-24 at 23:04 -0700, Jason Carlson wrote:
> > > When I run smdb while using Samba 4 I receive the following error: (Any
> > > Ideas?)
> > This is perfectly normal and expected. You do not need to run smbd,
> > Samba4 already includes a file server in the 'samba' binary.
> > We have plans to swap over the file server implementation there, but the
> > current plan is that it will still be started by 'samba', and so running
> > smbd additionally will indeed fail, due to being unable to bind to the
> > sockets.
> > What we do need to do is make this more clear, so our administrators can
> > better understand the different modal for starting services and easily
> > diagnose failures when they occur.
> > Andrew Bartlett
> > --
> > Andrew Bartlett
> > http://samba.org/~abartlet/ Authentication Developer, Samba Team
> > http://samba.org
More information about the samba-technical