Project

General

Profile

Bug #2063

Updated by cpg over 5 years ago

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
<pre>
[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.
</pre>


There was no log file in /var/log/samba/smbd.log

I checked the monit.log and found many entries like below:

<pre>

[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.
</pre>



I then ran the suggested command journalctl -xe and the following results were displayed repeatedly:

<pre>

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'.
</pre>



Hardware:
<pre>
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%
</pre>


http://paste.fedoraproject.org/372533/64574369

Back