Bug 919333 - Unable to start smbd, /run/samba don't exist
Summary: Unable to start smbd, /run/samba don't exist
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: samba
Version: 18
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Guenther Deschner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-08 07:12 UTC by Jan ONDREJ
Modified: 2013-03-25 22:54 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-03-25 22:54:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jan ONDREJ 2013-03-08 07:12:03 UTC
Description of problem:
Unable to start smbd, because /run/samba was not created by tmpfiles.

Version-Release number of selected component (if applicable):
samba-4.0.3-2.fc18.i686

How reproducible:
always

Steps to Reproduce:
1.systemctl start smbd.service

Actual results:
mar 08 08:07:25 work.bart.sk systemd[1]: PID 6665 read from file /run/smbd.pid

Expected results:
running samba

Additional info:
[root@work ~]# cat /etc/tmpfiles.d/samba.conf 
d /var/run/samba  755 root root
[root@work ~]# 

Please update tmpfiles.d file to create /run/samba instead of /var/run/samba
in Fedora 18.

Comment 1 Andreas Schneider 2013-03-08 10:01:30 UTC
Thanks for taking the time to report an issue.


However I don't see any bug here /var/run/samba is a symlink to /run so they are the same directory. Everything works just fine here on my F18.

What is the error you see?

Comment 2 Jan ONDREJ 2013-03-08 10:04:24 UTC
But because there is no /run/samba, then /var/run/samba is an symlink to nonexistent directory.

Or how do you think your /run/samba was created?

Comment 3 Andreas Schneider 2013-03-08 14:03:53 UTC
cat /etc/tmpfiles.d/samba.conf 
d /var/run/samba  755 root root

mkdir /var/run/samba

is the same as

mkdir /run/samba

cause /var/run is a symlink to /run. If you don't have this synlink something is broken on your system.

I've just rebooted my machine and /run/samba (/var/run/samba) has been automatically created by systemd.

So /etc/tmpfiles.d/samba.conf should probably be changed but it is valid to use /var/run/samba.

Comment 4 Jan ONDREJ 2013-03-08 15:01:09 UTC
Hmm, then I don't know why my /var/run/samba was a directory.
This command helped to temporarily fix my problem:

  mv /var/run/samba /run

My system was upgraded from Fedora 16 -> 18, may be this upgrade caused this.
Anyway, it will be better to make tmpfiles.d and systemd config scripts consistent in future.

Another PC:
[root@work ~]# ls -lad /var/run/samba
drwxr-xr-x 2 root root 40 mar  8  2013 /var/run/samba

I don't know, why you have a symlink.
Curious, that this another PC has also an /run/samba.

Comment 5 Andreas Schneider 2013-03-11 11:04:01 UTC
I think it is a problem from the upgrade. However I will add /run/samba too.

Comment 6 Fedora Update System 2013-03-20 16:12:25 UTC
samba-4.0.4-2.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/samba-4.0.4-2.fc18

Comment 7 Fedora Update System 2013-03-21 23:58:38 UTC
Package samba-4.0.4-2.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing samba-4.0.4-2.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-4125/samba-4.0.4-2.fc18
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2013-03-22 10:11:51 UTC
samba-4.0.4-3.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/samba-4.0.4-3.fc18

Comment 9 Fedora Update System 2013-03-25 22:54:08 UTC
samba-4.0.4-3.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.