Re: How to start dictd?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2007-11-13 01:06 +0000, Leo wrote:
> Dear All,
>
> After installing F8, i try to start dictd server with `/etc/init.d/dictd
> start' but failed with the following error:
>
> ,----
> | Starting dictd: :E: cannot open pid file '/var/run/dictd.pid'
> | :E:    err msg: Permission denied
> | dictd (pid_file_create): :E: terminating due to errors. See log file
> | :E: terminating due to errors. See log file
> |                                                            [FAILED]
> `----
>
> Any fix?

More info:

SummarySELinux is preventing /usr/sbin/dictd (dictd_t) "write" to
(var_run_t).

Detailed Description

SELinux is preventing /usr/sbin/dictd (dictd_t) "write" to
(var_run_t). The SELinux type var_run_t, is a generic type for all files
in the directory and very few processes (SELinux Domains) are allowed to
write to this SELinux type. This type of denial usual indicates a
mislabeled file. By default a file created in a directory has the gets
the context of the parent directory, but SELinux policy has rules about
the creation of directories, that say if a process running in one
SELinux Domain (D1) creates a file in a directory with a particular
SELinux File Context (F1) the file gets a different File Context
(F2). The policy usually allows the SELinux Domain (D1) the ability to
write or append on (F2). But if for some reason a file () was created
with the wrong context, this domain will be denied. The usual solution
to this problem is to reset the file context on the target file,
restorecon -v . If the file context does not change from var_run_t, then
this is probably a bug in policy. Please file a bug report against the
selinux-policy package. If it does change, you can try your application
again to see if it works. The file context could have been mislabeled by
editing the file or moving the file from a different directory, if the
file keeps getting mislabeled, check the init scripts to see if they are
doing something to mislabel the file.

Allowing Access

You can attempt to fix file context by executing restorecon -v The
following command will allow this access:restorecon

Additional Information

Source Context:  system_u:system_r:dictd_t:s0
Target Context:  system_u:object_r:var_run_t:s0
Target Objects:  None [ dir]
Affected RPM Packages:  dictd-1.10.9-1 [application]
Policy RPM:  selinux-policy-3.0.8-47.fc8Selinux
Enabled:  TruePolicy
Type:  targetedMLS
Enabled:  TrueEnforcing
Mode:  EnforcingPlugin
Name:  plugins.mislabeled_fileHost
Name:  sl392.st-edmunds.cam.ac.uk
Platform:  Linux
EST 2007 i686 i686Alert Count:  6First Seen:  Sun 11 Nov 2007 04:03:22
PM GMT

-- 
.:  Leo  :.  [ sdl.web AT gmail.com ]  .:  [ GPG Key: 9283AA3F ]  :.

          Use the best OS -- http://www.fedoraproject.org/


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux