1 |
Hi Pandu, |
2 |
|
3 |
Thanks for the response. What kind of permissions / privileges issues |
4 |
would cause this sort of behavior. |
5 |
|
6 |
~ % ps aux | grep -i apache |
7 |
root 2421 1.1 0.3 224928 12312 ? Ss 09:53 0:00 |
8 |
/usr/sbin/apache2 -D DEFAULT_VHOST -D INFO -D SSL -D SSL_DEFAULT_VHOST |
9 |
-D LANGUAGE -D PHP5 -d /usr/lib64/apache2 -f /etc/apache2/httpd.conf |
10 |
-k start |
11 |
apache 2423 0.0 0.1 209904 3884 ? S 09:53 0:00 |
12 |
/usr/sbin/apache2 -D DEFAULT_VHOST -D INFO -D SSL -D SSL_DEFAULT_VHOST |
13 |
-D LANGUAGE -D PHP5 -d /usr/lib64/apache2 -f /etc/apache2/httpd.conf |
14 |
-k start |
15 |
apache 2428 0.0 0.2 438024 8152 ? Sl 09:53 0:00 |
16 |
/usr/sbin/apache2 -D DEFAULT_VHOST -D INFO -D SSL -D SSL_DEFAULT_VHOST |
17 |
-D LANGUAGE -D PHP5 -d /usr/lib64/apache2 -f /etc/apache2/httpd.conf |
18 |
-k start |
19 |
apache 2429 0.0 0.2 438024 8148 ? Sl 09:53 0:00 |
20 |
/usr/sbin/apache2 -D DEFAULT_VHOST -D INFO -D SSL -D SSL_DEFAULT_VHOST |
21 |
-D LANGUAGE -D PHP5 -d /usr/lib64/apache2 -f /etc/apache2/httpd.conf |
22 |
-k start |
23 |
|
24 |
Looks like there's one process running as root, and the rest are |
25 |
running as Apache. /stuff/web/app is also apache:apache. |
26 |
|
27 |
Cherokee has a bug that creeps up on you when you're using SSL. PHP |
28 |
pages will half-load, sometimes completely load. The developers have |
29 |
NO idea what causes the problem. They've got a bug open but apparently |
30 |
they can't find root cause. While I love Cherokee, until this is fixed |
31 |
simple things like a wiki page loading will present the issue when |
32 |
there are graphics involved. |
33 |
|
34 |
-james |
35 |
|
36 |
|
37 |
On Mon, Apr 4, 2011 at 13:15, Pandu Poluan <pandu@××××××.info> wrote: |
38 |
> Based on the symptoms, i.e., works from CLI but fails during boot, I |
39 |
> suspect a problem with privileges/attributes. What UID is Apache |
40 |
> running as? |
41 |
> |
42 |
> Anyways, what's wrong with Cherokee? I really like to know because I |
43 |
> am currently considering deploying Cherokee. |
44 |
> |
45 |
> Rgds, |
46 |
> |
47 |
> |
48 |
> On 2011-04-04, James <jtp@×××××.com> wrote: |
49 |
>> It's also worth noting that I have *no* "/usr/htdocs" line in any of |
50 |
>> my configuration file(s). |
51 |
>> |
52 |
>> -james |
53 |
>> |
54 |
>> |
55 |
>> On Mon, Apr 4, 2011 at 11:22, James <jtp@×××××.com> wrote: |
56 |
>>> I'm a long-time Cherokee user that is switching to Apache due to a |
57 |
>>> nasty Cherokee bug that I can't seem to work around. |
58 |
>>> |
59 |
>>> I've configured Apache many times (albeit a long time ago), and can't |
60 |
>>> seem to figure out what's going on here. |
61 |
>>> |
62 |
>>> I have a simple PHP app running that lives in some directory, say |
63 |
>>> /stuff/web/app. |
64 |
>>> |
65 |
>>> I then have a vhost configuration that looks like this: |
66 |
>>> |
67 |
>>> <Directory "/stuff/web/app"> |
68 |
>>> Options Indexes FollowSymLinks |
69 |
>>> AllowOverride All |
70 |
>>> Order allow,deny |
71 |
>>> Allow from all |
72 |
>>> </Directory> |
73 |
>>> |
74 |
>>> The vhost looks like this: |
75 |
>>> |
76 |
>>> <VirtualHost app.server.com:80> |
77 |
>>> ServerName app.server.com |
78 |
>>> DocumentRoot "/stuff/web/app" |
79 |
>>> ErrorLog /var/log/apache2/app.error |
80 |
>>> </VirtualHost> |
81 |
>>> |
82 |
>>> When the server reboots, Apache refuses to serve me anything, giving |
83 |
>>> the following error: |
84 |
>>> |
85 |
>>> ==> error_log <== |
86 |
>>> [Mon Apr 04 07:17:59 2011] [error] [client 10.35.22.81] client denied |
87 |
>>> by server configuration: /usr/htdocs |
88 |
>>> |
89 |
>>> ==> access_log <== |
90 |
>>> 10.35.22.81 - - [04/Apr/2011:07:17:59 -0400] "\x16\x03\x01\x01\x98\x01" |
91 |
>>> 403 273 |
92 |
>>> |
93 |
>>> I'm well aware of the default apache configuration (defined in |
94 |
>>> /etc/apache2/modules.d/00_default_settings.conf), and that the default |
95 |
>>> directory directive has a "Deny from all" default. |
96 |
>>> |
97 |
>>> However, if I *restart* my daemon with NO configuration changes after |
98 |
>>> seeing these errors, the page comes up beautifully. Also worth noting |
99 |
>>> is that rebooting the server again will put Apache back into a |
100 |
>>> "broken" state and only after restarting the daemon will things |
101 |
>>> function correctly. |
102 |
>>> |
103 |
>>> Thoughts on how to fix this would be much, MUCH appreciated. I am |
104 |
>>> running out of hair to pull out of my head. :) |
105 |
>>> |
106 |
>>> -james |
107 |
>>> |
108 |
>> |
109 |
>> |
110 |
> |
111 |
> |
112 |
> -- |
113 |
> -- |
114 |
> Pandu E Poluan - IT Optimizer |
115 |
> My website: http://pandu.poluan.info/ |
116 |
> |
117 |
> |