Bug 182468
Summary: | Winbind fails to start via /etc/init.d/winbind script | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Eugenio Jordán González <ejordan> |
Component: | samba | Assignee: | Jay Fenlason <fenlason> |
Status: | CLOSED NOTABUG | QA Contact: | David Lawrence <dkl> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | dwalsh, jfeeney, nalin |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-23 15:04:00 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Eugenio Jordán González
2006-02-22 19:29:55 UTC
Can you add the version of the selinux-policy-targeted package which you have installed, and the output of 'restorecon -v /etc/samba/secrets.tdb' in case there's a labeling problem involved? Sorry, had already checked as per other related bugs but forgot to provide:
[root@mtvisadorh01 ~]# rpm -qa | grep policy
checkpolicy-1.17.5-1
selinux-policy-targeted-1.17.30-2.110
policycoreutils-1.18.1-4.7
[root@mtvisadorh01 ~]# restorecon -v /etc/samba/secrets.tdb
restorecon reset context /etc/samba/secrets.tdb:root:object_r:samba_etc_t-
>system_u:object_r:samba_secrets_t
After doing this, according to your instructions, problems's solved:
[root@mtvisadorh01 ~]# /etc/init.d/winbind start
Starting Winbind services: [ OK ]
[root@mtvisadorh01 ~]# /etc/init.d/winbind status
winbindd (pid 21433 21432) is running...
[root@mtvisadorh01 ~]# /etc/init.d/winbind stop
Shutting down Winbind services: [ OK ]
[root@mtvisadorh01 ~]# /etc/init.d/winbind start
Starting Winbind services: [ OK ]
[root@mtvisadorh01 ~]# /etc/init.d/winbind status
winbindd (pid 21456 21455) is running...
Thank you so much for your help, and sorry for wasting your time, as it's
clearly not a bug.
It may still be a bug if the file was created while SELinux was in use, but somehow didn't get the correct label applied right then, but I'll leave that for Jay to decide. Thanks! |