Red Hat Bugzilla – Bug 832732
smbd fails to start on F17 x86_64 after downgrade from samba4
Last modified: 2013-01-30 04:17:47 EST
Description of problem:
smbd fails to start on F17 x86_64
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Enable the service - systemctl enable smb.service
2. Reboot System
3. Check the status - systemctl status smb.service
Output form "systemctl status smb.service":
smb.service - Samba SMB Daemon
Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled)
Active: failed (Result: exit-code) since Sat, 16 Jun 2012 11:29:38 -0500; 5h 18min ago
Process: 1060 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=exited, status=0/SUCCESS)
Main PID: 1107 (code=exited, status=1/FAILURE)
Jun 16 11:29:38 mypc1 smbd: [2012/06/16 11:29:38.641351, 0] smbd/server.c:1107(main)
Jun 16 11:29:38 mypc1 smbd: [2012/06/16 11:29:38.966179, 0] registry/reg_init_basic...mon)
Jun 16 11:29:38 mypc1 smbd: Failed to initialize the registry: WERR_CAN_NOT_COMPLETE
Expect smbd to be running and status to show Active instead of failed.
Just confirmed that it works fine on identical F17 i686 system - same kernel/samba versions.
Resolved. I believe this may have occurred as a result of me initially installing samba4, then removing that and installing samba. The error I received in debug indicated invalid tdb version.
Steps to resolve:
- yum remove samba samba-common
- rm -rf /var/lib/samba
- yum install samba
If you have installed samba4 and then downgraded to samba3, see bug 829694 comment 8.
Please keep this bug open as we'll use it to provide README.Samba4-Samba3.downgrade with instructions on how to behave in such cases.
I'm changing bug title to reflect documentation fix.
I suppose this affects not only x86_64, but i686 downgrades as well. Although I can't confirm that, since I never downgraded there.
Alexander, we NEVER supported downgrades in Samba! The same applies here.