1 |
On Thu, 2005-10-06 at 14:18 -0400, Albert Lash wrote: |
2 |
> The problem I am experiencing is when I restart apache. I do this as root, |
3 |
> su'd from a user with SELinux role staff_r and sysadm_r. I first login via |
4 |
> ssh as a normal user, then I newrole -r sysadm_r, then I su, and then I |
5 |
> /etc/init.d/apache2 restart. I get a warning that there is not pid. So |
6 |
> then I have to kill the process identified by ps -A, and then |
7 |
> /etc/init.d/apache start. (Whenever I run an init script, I have to |
8 |
> authenticate as the original user who has the sysadm_r role). The server |
9 |
> starts fine, but seems to have a delay before I can access the server via |
10 |
> a browser. Even when the server starts responding to browser requests, no |
11 |
> pid file is written to /var/run. There aren't even any denials in the |
12 |
> /var/log/messages files, which still wouldnt' prevent a pid file from |
13 |
> getting written, as I am in permissive mode. |
14 |
|
15 |
If this doesn't work in permissive, then it points to something not |
16 |
SELinux related being wrong. I suggest looking at the apache logs for |
17 |
errors, and also check DAC perms. |
18 |
|
19 |
> I have also tried the SELinux run_init command before the ini script with |
20 |
> the same results. |
21 |
|
22 |
This won't help because Gentoo already has run_init integrated into the |
23 |
init script system. |
24 |
|
25 |
> Is this standard behavior for Apache2 on SELinux? |
26 |
|
27 |
No, I can't reproduce it on my enforcing systems. |
28 |
|
29 |
-- |
30 |
Chris PeBenito |
31 |
<pebenito@g.o> |
32 |
Developer, |
33 |
Hardened Gentoo Linux |
34 |
Embedded Gentoo Linux |
35 |
|
36 |
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE6AF9243 |
37 |
Key fingerprint = B0E6 877A 883F A57A 8E6A CB00 BC8E E42D E6AF 9243 |