Hi all: Just rolled 11.4 (x64) out to my hove server. Copied over all my samba config files and started up samba - nothing. Manually started samba (/etc/init.d/smb start) and samba appears to start but checking the status does not show it running. Actually checking the status returns nothing. Stopping samba returns “unused”.
Can someone help me out here? I have never had issues with opensuse and samba before.
Chris,
did the same, upgraded my file-server and lost the clients connected with samba, thought it was because of updating and reinstalled fresh OS11.4, did not do the trick, sorry I can´t help you, besides shouting with you, PLEASE HELP!
After updating from OS 11.3 to OS 11.4 on a test node, I had the same trouble. And the funny joke was that Webmin saw Samba in running status. FYI I saw that OS 11.4 auto disable CIFS as it is ON with OS 11.3. And the NetBIOS Server service is now automatically add when we allow opening ports on firewall during Samba setup. So in fact it is right a trouble with AppArmor profile as said above. Thanks for the report. And Blotz’s setup works fine. FYI you can also setup complain status in Yast / Novell AppArmor / AppArmor setup panel / profiles setup button / change mode button.
Unable to setup corepath for smbd: Permission denied
smbd version 3.5.7-1.17.1-2505-SUSE-SL11.4-i386 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010
Failed to open /etc/samba/secrets.tdb
Failed to open /etc/samba/secrets.tdb
ERROR: smbd can not open secrets.tdb
I also saw "failed to open /etc/samba/dhcp.conf in the samba log files.
Turned out I had 2 copies of Yast running, one of which was in the “middle” of configuring the samba server.
I was alternately trying to start the smb daemon from the command line and the 2nd copy of Yast.
I think the “other” copy of Yast had locked the dhcp.conf file, preventing samba from reading it. Once I shutdown both copies of Yast, and then retried starting it from the command line it reported it was already running (started when I exited the copy of Yast which was editing the config) - all good from here on.