Description of problem: Yum update today included samba packages:
Sep 25 10:13:21 Updated: samba-winbind-3.4.1-0.41.fc11.x86_64
Sep 25 10:13:24 Updated: samba-common-3.4.1-0.41.fc11.x86_64
Sep 25 10:13:26 Updated: samba-3.4.1-0.41.fc11.x86_64
Sep 25 10:13:29 Updated: samba-client-3.4.1-0.41.fc11.x86_64
Sep 25 10:13:30 Updated: libsmbclient-3.4.1-0.41.fc11.x86_64
After this update was installed no users can access shares. Access denied for all users. Webmin is telling me there ARE NO USERS, but a check of /var/lib/samba/private/smbpasswd shows they are still there. Webmin is expecting the users file to be in /etc/samba/smbpasswd but this file is missing. Restarting smb/nmb has no effect.
I have the same.
Removing all my site-configuration and reinstalling these RPMs didn't help (ie: 100% stock configuration doesn't work). Clients are another F11 machine, and a mac desktop.
Rolling back to Samba 3.3.2-0.33 fixed problem.
Yeah, rolling back fixed it for me too..
I am having the same problem.
My /var/log/messages says:
smbd: [2009/09/27 21:59:55, 0] smbd/server.c:457(smbd_open_one_socket)
smbd: smbd_open_once_socket: open_socket_in: Address already in use
And /var/log/samba/smbd.log says:
[2009/09/27 21:59:55, 0] mbd/server.c:457(smbd_open_one_socket)
smbd_open_onc _socket: open_socket_in: Address already in use
fwiw, the i586 packages do not seem to be affected.
*** This bug has been marked as a duplicate of bug 525861 ***
This bug and 525861 don't seem to be related to me. I am having the problem on an x86_64 system with an "passdb backend = ldapsam:ldap:... blah blah" backend.
(In reply to comment #7)
> This bug and 525861 don't seem to be related to me. I am having the problem
> on an x86_64 system with an "passdb backend = ldapsam:ldap:... blah blah"
Forgot to mention that rolling back to 3.3.2-0.33 corrected the problem for me also.
I'm hitting this same error after upgrading from samba-3.4.5-55.fc12.x86_64 to samba-3.4.7-58.fc12.x86_64. I also see no connection to bug #525861. I think the duplicate status was a mistake; do you mind if I switch it to assigned?
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.