Bug #2063
SAMBA won't start after fresh install of F23 and Amahi 9
0%
Description
I installed from a full install (minimal installation) DVD of fedora 23 per the instructions on the full install page and when the system came online, I noticed that samba wasn't running. Per another post in the forum, I changed my router specifications per the out of the box instructions and rebooted both the server and my pc. I can see the server and my amahi account sees the server without issue.
However, the samba service is still not listed as running.
I ran the following command with these result: systemctl status smb
[root@localhost ~]# systemctl status smb ● smb.service - Samba SMB Daemon Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Mon 2016-05-30 01:37:27 CDT; 25s ago Process: 1597 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=exited, status=127) Main PID: 1597 (code=exited, status=127) May 30 01:37:27 localhost.localdomain systemd[1]: Starting Samba SMB Daemon... May 30 01:37:27 localhost.localdomain systemd[1]: smb.service: Main process exited, code=exited, status=127/n/a May 30 01:37:27 localhost.localdomain systemd[1]: Failed to start Samba SMB Daemon. May 30 01:37:27 localhost.localdomain systemd[1]: smb.service: Unit entered failed state. May 30 01:37:27 localhost.localdomain systemd[1]: smb.service: Failed with result 'exit-code'. May 30 01:37:27 localhost.localdomain smbd[1597]: /usr/sbin/smbd: relocation error: /lib64/libsamba-credentials.so.0: symbol GSS_...erence Hint: Some lines were ellipsized, use -l to show in full.
There was no log file in /var/log/samba/smbd.log
I checked the monit.log and found many entries like below:
[CDT May 30 01:40:27] error : 'smb' process is not running [CDT May 30 01:40:27] info : 'smb' trying to restart [CDT May 30 01:40:27] info : 'smb' start: /usr/bin/systemctl [CDT May 30 01:40:58] error : 'smb' failed to start (exit status 1) -- /usr/bin/systemctl: Job for smb.service failed because the control process exited with error code. See "systemctl status smb.service" and "journalctl -xe" for details.
I then ran the suggested command journalctl -xe and the following results were displayed repeatedly:
May 30 01:42:28 localhost.localdomain systemd[1]: Starting Samba SMB Daemon... -- Subject: Unit smb.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit smb.service has begun starting up. May 30 01:42:28 localhost.localdomain smbd[1750]: /usr/sbin/smbd: relocation error: /lib64/libsamba-credentials.so. May 30 01:42:28 localhost.localdomain systemd[1]: smb.service: Main process exited, code=exited, status=127/n/a May 30 01:42:28 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit= May 30 01:42:28 localhost.localdomain systemd[1]: Failed to start Samba SMB Daemon. -- Subject: Unit smb.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit smb.service has failed. -- -- The result is failed. May 30 01:42:28 localhost.localdomain systemd[1]: smb.service: Unit entered failed state. May 30 01:42:28 localhost.localdomain systemd[1]: smb.service: Failed with result 'exit-code'.
Hardware:
Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz 4GB RAM / 400G 1.6G 399G 1% /tmp 10G 33M 10G 1% /boot 976M 74M 836M 9%
History
#1 Updated by cpg about 6 years ago
- Description updated (diff)
#2 Updated by powderburned about 6 years ago
I was able to resolve by ensuring that all samba dependencies were installed or up to date by executing the following:
yum install libacl-devel libblkid-devel gnutls-devel \ readline-devel python-devel gdb pkgconfig libattr-devel \ krb5-workstation python-crypto docbook-style-xsl openldap-devel
#3 Updated by bigfoot65 about 6 years ago
- Status changed from New to Feedback
- Assignee set to powderburned
Update from powderburned:
Just an FYI. After getting samba to work, share permissions didn't appear to be managed by amahi. Although I could see the samba shares listed in \\hda\ I could not access them with any of the accounts in amahi. I also reassigned the owner:group the same as all of the out of the box shares but this didn't resolve the issue. I decided to start over and went to the fedora site to download the netinstaller directly and burned it to a dvd instead of a cd per that site's instructions. This worked. I was able to install via the netinstaller and now my amahi server is up and running with all of the functions I had with my older 7 install previously.
May need to test this install to replicate the issues and a potential solution.
Also available in: Atom