1 |
Way to go Travis thank you for the link and advice, this fixed my issue! |
2 |
As a follow up, the compilation gave me a warning about lazy bindings, and |
3 |
suggested I compile with these additional options: |
4 |
|
5 |
CFLAGS="-Wl,-z,now" |
6 |
|
7 |
I did so and it compiled OK. |
8 |
|
9 |
Cheers! |
10 |
|
11 |
Albert |
12 |
|
13 |
On Thu, 6 Oct 2005, Travis Fraser wrote: |
14 |
|
15 |
> On Thu, 2005-10-06 at 22:00 -0400, Chris PeBenito wrote: |
16 |
> > On Thu, 2005-10-06 at 14:18 -0400, Albert Lash wrote: |
17 |
> > > The problem I am experiencing is when I restart apache. I do this as root, |
18 |
> > > su'd from a user with SELinux role staff_r and sysadm_r. I first login via |
19 |
> > > ssh as a normal user, then I newrole -r sysadm_r, then I su, and then I |
20 |
> > > /etc/init.d/apache2 restart. I get a warning that there is not pid. So |
21 |
> > > then I have to kill the process identified by ps -A, and then |
22 |
> > > /etc/init.d/apache start. (Whenever I run an init script, I have to |
23 |
> > > authenticate as the original user who has the sysadm_r role). The server |
24 |
> > > starts fine, but seems to have a delay before I can access the server via |
25 |
> > > a browser. Even when the server starts responding to browser requests, no |
26 |
> > > pid file is written to /var/run. There aren't even any denials in the |
27 |
> > > /var/log/messages files, which still wouldnt' prevent a pid file from |
28 |
> > > getting written, as I am in permissive mode. |
29 |
> > |
30 |
> It seems to have something to do with entropy?. See this thread: |
31 |
> http://forums.gentoo.org/viewtopic-t-384660-highlight-apache+pid.html |
32 |
> |
33 |
> specifically this part: |
34 |
> MY_BUILTINS="--with-devrandom=/dev/urandom" emerge apache |
35 |
> |
36 |
> This solved the exact problem for me even though I had no problems on |
37 |
> other servers (no selinux on any of them though). |
38 |
> |
39 |
> > If this doesn't work in permissive, then it points to something not |
40 |
> > SELinux related being wrong. I suggest looking at the apache logs for |
41 |
> > errors, and also check DAC perms. |
42 |
> > |
43 |
> > > I have also tried the SELinux run_init command before the ini script with |
44 |
> > > the same results. |
45 |
> > |
46 |
> > This won't help because Gentoo already has run_init integrated into the |
47 |
> > init script system. |
48 |
> > |
49 |
> > > Is this standard behavior for Apache2 on SELinux? |
50 |
> > |
51 |
> > No, I can't reproduce it on my enforcing systems. |
52 |
> > |
53 |
> -- |
54 |
> Travis Fraser <travis@×××××××××.net> |
55 |
> |
56 |
> -- |
57 |
> gentoo-hardened@g.o mailing list |
58 |
> |
59 |
-- |
60 |
gentoo-hardened@g.o mailing list |