Bug 158802 - service smb start fails to start smbd
service smb start fails to start smbd
Product: Fedora
Classification: Fedora
Component: samba (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jay Fenlason
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2005-05-25 16:50 EDT by Stéphane Moinard
Modified: 2014-08-31 19:27 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-05-26 10:09:47 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Stéphane Moinard 2005-05-25 16:50:58 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr-FR; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

Description of problem:

Under FC4-Test3, the script smb fails to start smbd (there is no problem with nmbd).

the error is : /etc/init.d/functions: line 83: 29607 Abort          $nice $*

If i try to start /usr/sbin/smbd -D manually, it works.

If i try to start "/usr/sbin/smbd -D" into another script than /etc/rc.d/init.d/smb, it fails (just a message that it is aborted).

Any idea ?


Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. service smb start fails only on the startup of smbd
2. under the shell, /usr/sbin/smbd -D works

Additional info:
Comment 1 Jay Fenlason 2005-05-25 17:02:03 EDT
WORKSFORME on my rawhide box, and I haven't changed anything in that area of 
the code in a long time.  Can you attach your /etc/samba/smb.conf to this bug 
so I can try to reproduce it? 
What does "strace -f -o <some log file> /sbin/service smb start" put in that 
log file.  It's going to be large, and the interesting part is probably at the 
Comment 2 Stéphane Moinard 2005-05-26 10:09:47 EDT
Hi Jey,

I found a solution. As i had the same problem to start dovecot, i searched 
thought that the problem was not involving samba.

Selinux was activated with "enforcing" policy. Desactivating selinux solved 
the problem.

I'm still interested to have a solution with selinux activated.

Best regards.

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