SOLVED: Samba Service won't start

zac851
Posts: 31
Joined: Tue Aug 26, 2014 7:58 pm

SOLVED: Samba Service won't start

Postby zac851 » Wed Jan 21, 2015 5:11 pm

Can anyone tell me why my Samba service won't start? I've tried to stop it, start it, and restart it with no luck. The server has been running perfect for the last 80 days so as a last resort, I just restarted the server but it still wouldn't start up. The most recent changes that I attempted to install VNC yesterday which failed. Next I installed Sick Beard, and Couch Potato but everything worked fine after that until a few hours ago.

Here is the logs

Code: Select all

[root@localhost samba]# nano smbd.log GNU nano 2.3.1 File: smbd.log [2015/01/18 03:48:48.638177, 0] ../source3/printing/print_cups.c:151(cups_connect) Unable to connect to CUPS server localhost:631 - Transport endpoint is not connected [2015/01/18 03:48:48.638427, 0] ../source3/printing/print_cups.c:528(cups_async_callback) failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL [2015/01/18 04:01:49.131828, 0] ../source3/printing/print_cups.c:151(cups_connect) Unable to connect to CUPS server localhost:631 - Transport endpoint is not connected [2015/01/18 04:01:49.132008, 0] ../source3/printing/print_cups.c:528(cups_async_callback) failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL [2015/01/18 04:14:49.529941, 0] ../source3/printing/print_cups.c:151(cups_connect) Unable to connect to CUPS server localhost:631 - Transport endpoint is not connected [2015/01/18 04:14:49.530129, 0] ../source3/printing/print_cups.c:528(cups_async_callback) failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL [2015/01/18 04:27:50.078706, 0] ../source3/printing/print_cups.c:151(cups_connect) Unable to connect to CUPS server localhost:631 - Transport endpoint is not connected [2015/01/18 04:27:50.078929, 0] ../source3/printing/print_cups.c:528(cups_async_callback) failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL [2015/01/18 04:40:50.731916, 0] ../source3/printing/print_cups.c:151(cups_connect) Unable to connect to CUPS server localhost:631 - Transport endpoint is not connected [2015/01/18 04:40:50.732103, 0] ../source3/printing/print_cups.c:528(cups_async_callback) failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL [2015/01/18 04:53:51.349448, 0] ../source3/printing/print_cups.c:151(cups_connect) Unable to connect to CUPS server localhost:631 - Transport endpoint is not connected [2015/01/18 04:53:51.349673, 0] ../source3/printing/print_cups.c:528(cups_async_callback) failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL [2015/01/18 05:06:51.946300, 0] ../source3/printing/print_cups.c:151(cups_connect) Unable to connect to CUPS server localhost:631 - Transport endpoint is not connected [2015/01/18 05:06:51.946503, 0] ../source3/printing/print_cups.c:528(cups_async_callback) failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL [2015/01/18 05:19:52.440954, 0] ../source3/printing/print_cups.c:151(cups_connect) Unable to connect to CUPS server localhost:631 - Transport endpoint is not connected [2015/01/18 05:19:52.441152, 0] ../source3/printing/print_cups.c:528(cups_async_callback) failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL [2015/01/18 05:32:52.836900, 0] ../source3/printing/print_cups.c:151(cups_connect) Unable to connect to CUPS server localhost:631 - Transport endpoint is not connected [2015/01/18 05:32:52.837128, 0] ../source3/printing/print_cups.c:528(cups_async_callback) failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL [2015/01/18 05:45:53.321828, 0] ../source3/printing/print_cups.c:151(cups_connect) Unable to connect to CUPS server localhost:631 - Transport endpoint is not connected [2015/01/18 05:45:53.322018, 0] ../source3/printing/print_cups.c:528(cups_async_callback) failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL [2015/01/18 05:58:53.849884, 0] ../source3/printing/print_cups.c:151(cups_connect) Unable to connect to CUPS server localhost:631 - Transport endpoint is not connected [2015/01/18 05:58:53.850087, 0] ../source3/printing/print_cups.c:528(cups_async_callback) failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL [2015/01/18 06:11:54.354903, 0] ../source3/printing/print_cups.c:151(cups_connect) Unable to connect to CUPS server localhost:631 - Transport endpoint is not connected [2015/01/18 06:11:54.355102, 0] ../source3/printing/print_cups.c:528(cups_async_callback) failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL [2015/01/18 06:24:54.776983, 0] ../source3/printing/print_cups.c:151(cups_connect) Unable to connect to CUPS server localhost:631 - Transport endpoint is not connected [2015/01/18 06:24:54.777192, 0] ../source3/printing/print_cups.c:528(cups_async_callback) failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL [2015/01/18 06:37:55.256868, 0] ../source3/printing/print_cups.c:151(cups_connect) Unable to connect to CUPS server localhost:631 - Transport endpoint is not connected [2015/01/18 06:37:55.257080, 0] ../source3/printing/print_cups.c:528(cups_async_callback)
Last edited by zac851 on Wed Jan 21, 2015 5:15 pm, edited 1 time in total.

User avatar
bigfoot65
Project Manager
Posts: 11924
Joined: Mon May 25, 2009 4:31 pm

Re: Samba Service won't start

Postby bigfoot65 » Wed Jan 21, 2015 5:15 pm

Try to uninstall cups then restart samba.

Code: Select all

yum erase cups
Unless you have a printer connected to the HDA it's not needed.
ßîgƒσστ65
Applications Manager

My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2

zac851
Posts: 31
Joined: Tue Aug 26, 2014 7:58 pm

Re: Samba Service won't start

Postby zac851 » Wed Jan 21, 2015 5:30 pm

Nope, no printer. It says there is no CUPS package to remove. Below is what I get when I run systemctl status smb.service. Looks like some files are missing/got corrupted?

Code: Select all

[root@localhost /]# systemctl restart smb.service Job for smb.service failed. See 'systemctl status smb.service' and 'journalctl -xn' for details. [root@localhost /]# systemctl status smb.service smb.service - Samba SMB Daemon Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled) Active: failed (Result: exit-code) since Wed 2015-01-21 18:28:08 CST; 18s ago Process: 4814 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=exited, status=1/FAILURE) Jan 21 18:28:08 localhost.localdomain smbd[4814]: /usr/sbin/smbd: /usr/lib64/samba/libsmbd_shim.so: version `SAMBA_4.0.8' not found (required by /usr/sbin/smbd) Jan 21 18:28:08 localhost.localdomain smbd[4814]: /usr/sbin/smbd: /usr/lib64/samba/liberrors.so: version `SAMBA_4.0.8' not found (required by /usr/sbin/smbd) Jan 21 18:28:08 localhost.localdomain smbd[4814]: /usr/sbin/smbd: /usr/lib64/samba/libsecrets3.so: version `SAMBA_4.0.8' not found (required by /usr/sbin/smbd) Jan 21 18:28:08 localhost.localdomain smbd[4814]: /usr/sbin/smbd: /usr/lib64/samba/libpopt_samba3.so: version `SAMBA_4.0.8' not found (required by /usr/sbin/smbd) Jan 21 18:28:08 localhost.localdomain smbd[4814]: /usr/sbin/smbd: /usr/lib64/samba/libcliauth.so: version `SAMBA_4.0.8' not found (required by /usr/sbin/smbd) Jan 21 18:28:08 localhost.localdomain smbd[4814]: /usr/sbin/smbd: /usr/lib64/samba/libsamba3-util.so: version `SAMBA_4.0.8' not found (required by /usr/sbin/smbd) Jan 21 18:28:08 localhost.localdomain smbd[4814]: /usr/sbin/smbd: /usr/lib64/samba/libsmbd_base.so: version `SAMBA_4.0.8' not found (required by /usr/sbin/smbd) Jan 21 18:28:08 localhost.localdomain systemd[1]: smb.service: control process exited, code=exited status=1 Jan 21 18:28:08 localhost.localdomain systemd[1]: Failed to start Samba SMB Daemon. Jan 21 18:28:08 localhost.localdomain systemd[1]: Unit smb.service entered failed state.

zac851
Posts: 31
Joined: Tue Aug 26, 2014 7:58 pm

Re: Samba Service won't start

Postby zac851 » Wed Jan 21, 2015 5:36 pm

Should I just run "yum install samba" and see if reinstalling fixes it and will that wipe out my current smb.conf in doing so?

zac851
Posts: 31
Joined: Tue Aug 26, 2014 7:58 pm

Re: Samba Service won't start

Postby zac851 » Wed Jan 21, 2015 5:45 pm

I was reading this thread below

viewtopic.php?f=8&t=5538&start=20

And it looks like one of the users had nearly the same issue I'm having which started after he tried to install VNC and it broke samba.

As I said in my first post, I originally tried to install the VNC amahi app, and it gave an error after about 2 minutes and didn't install. I've got a 100 megabit connection so not sure what happen.. Everything seemed find afterwards though and I went on to install couch potato and sick beard and configure and test them but i'm guessing it had something to do with my current issues.
Last edited by zac851 on Wed Jan 21, 2015 5:48 pm, edited 1 time in total.

User avatar
bigfoot65
Project Manager
Posts: 11924
Joined: Mon May 25, 2009 4:31 pm

Re: Samba Service won't start

Postby bigfoot65 » Wed Jan 21, 2015 5:47 pm

Ok missed that. Try installing VNC app again.
ßîgƒσστ65
Applications Manager

My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2

zac851
Posts: 31
Joined: Tue Aug 26, 2014 7:58 pm

Re: Samba Service won't start

Postby zac851 » Wed Jan 21, 2015 6:03 pm

Alright, VNC installed this time and I was able to log into it and all that so that's good.

Samba is still have the same issue though. I'm going to do another quick reboot of the entire server

User avatar
bigfoot65
Project Manager
Posts: 11924
Joined: Mon May 25, 2009 4:31 pm

Re: Samba Service won't start

Postby bigfoot65 » Wed Jan 21, 2015 6:09 pm

That same process has worked for others. Seems if the install fails the first time, the second go around works. Not sure if this is due to connectivity or the dependencies just take too long.

Hope everything is working now.
ßîgƒσστ65
Applications Manager

My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2

zac851
Posts: 31
Joined: Tue Aug 26, 2014 7:58 pm

Re: Samba Service won't start

Postby zac851 » Wed Jan 21, 2015 6:42 pm

Even after a second reboot, samba is the only service not coming back online. What should I do from here? Still get pretty much the same thing as before

Code: Select all

[root@localhost samba]# systemctl stop smb.service [root@localhost samba]# systemctl start smb.service Job for smb.service failed. See 'systemctl status smb.service' and 'journalctl -xn' for details. [root@localhost samba]# systemctl status smb.service smb.service - Samba SMB Daemon Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled) Active: failed (Result: exit-code) since Wed 2015-01-21 19:42:02 CST; 5s ago Process: 5632 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=exited, status=1/FAILURE) Jan 21 19:42:02 localhost.localdomain smbd[5632]: /usr/sbin/smbd: /usr/lib64/samba/libsmbd_shim.so: version `SAMBA_4.0.8' not found (required by /usr/sbin/smbd) Jan 21 19:42:02 localhost.localdomain smbd[5632]: /usr/sbin/smbd: /usr/lib64/samba/liberrors.so: version `SAMBA_4.0.8' not found (required by /usr/sbin/smbd) Jan 21 19:42:02 localhost.localdomain smbd[5632]: /usr/sbin/smbd: /usr/lib64/samba/libsecrets3.so: version `SAMBA_4.0.8' not found (required by /usr/sbin/smbd) Jan 21 19:42:02 localhost.localdomain smbd[5632]: /usr/sbin/smbd: /usr/lib64/samba/libpopt_samba3.so: version `SAMBA_4.0.8' not found (required by /usr/sbin/smbd) Jan 21 19:42:02 localhost.localdomain smbd[5632]: /usr/sbin/smbd: /usr/lib64/samba/libcliauth.so: version `SAMBA_4.0.8' not found (required by /usr/sbin/smbd) Jan 21 19:42:02 localhost.localdomain smbd[5632]: /usr/sbin/smbd: /usr/lib64/samba/libsamba3-util.so: version `SAMBA_4.0.8' not found (required by /usr/sbin/smbd) Jan 21 19:42:02 localhost.localdomain smbd[5632]: /usr/sbin/smbd: /usr/lib64/samba/libsmbd_base.so: version `SAMBA_4.0.8' not found (required by /usr/sbin/smbd) Jan 21 19:42:02 localhost.localdomain systemd[1]: smb.service: control process exited, code=exited status=1 Jan 21 19:42:02 localhost.localdomain systemd[1]: Failed to start Samba SMB Daemon. Jan 21 19:42:02 localhost.localdomain systemd[1]: Unit smb.service entered failed state.

User avatar
bigfoot65
Project Manager
Posts: 11924
Joined: Mon May 25, 2009 4:31 pm

Re: Samba Service won't start

Postby bigfoot65 » Wed Jan 21, 2015 6:52 pm

Have you done an OS update? You could reinstall Samba, but it's important that you don't overwrite any of the configuration files.

I would recommend the OS update first to see if that fixes the problem.
ßîgƒσστ65
Applications Manager

My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2

Who is online

Users browsing this forum: No registered users and 73 guests