|
|
|
|
|
|
| Author |
Message |
Oliver Marshall
*nix forums beginner
Joined: 18 Apr 2005
Posts: 33
|
 Posted: Wed Jul 19, 2006 6:08 pm Post subject:
Apache 2.2 and Joomla
|
|
|
Anyone know of any issues with Joomla on Apache 2.2 ?
I've managed to get the windows 2003 server up and working, and apache
is serving up pages just fine. I thought it wasn't working at first
until I realised that all the joomla oriented pages are just bringing up
either a blank page or a "page cannot be displayed". Point it at a
straight .html or .php page and it works fine.
I know this isn't a joomla list, but I thought I would ask people who
look after apache servers if they have seen any issues.
Olly
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org |
|
| Back to top |
|
 |
Joshua Slive
*nix forums Guru
Joined: 07 Feb 2005
Posts: 1647
|
| Posted: Wed Jul 19, 2006 4:13 pm Post subject:
Re: Excessive memory consumption
|
|
|
On 7/19/06, John Morrissey <jwm@horde.net> wrote:
| Quote: | On Tue, Jul 18, 2006 at 08:53:51PM -0400, Joshua Slive wrote:
On 7/14/06, John Morrissey <jwm@horde.net> wrote:
On Tue, Jun 06, 2006 at 11:12:17AM -0400, Joshua Slive wrote:
On 6/6/06, John Morrissey <jwm@horde.net> wrote:
I'm having a problem with Apache 2.0.54 (we're running the Debian
packages for 2.0.54-5). Periodically, a single Apache child will
rapidly consume all available memory on the machine - once the
memory consumption starts, it only takes five or ten minutes (at
most) for it to exhaust available memory.
Are any of the requests byte-ranges (response code 206). If so, see:
http://issues.apache.org/bugzilla/show_bug.cgi?id=29962
Some are, yes. It looks like the Debian 2.0.54-5 packages already include
the patch attached to that bug (the one in the source package is identical
to the one posted in the bug).
I also looked at bug 23567 (and 34589, which is a duplicate) but the only
filter we have enabled is INCLUDES (mod_include). None of the suspect
requests was for server-parsed HTML *and* a byte-range request (206
response).
|
Well, you should really upgrade to the most recent version to make
sure you have the official patch. You can also do the
RequestHeader unset Range
Header unset Accept-Ranges
hack.
Joshua.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org |
|
| Back to top |
|
|
John Morrissey
*nix forums beginner
Joined: 06 Jun 2006
Posts: 3
|
| Posted: Wed Jul 19, 2006 4:04 pm Post subject:
Re: Excessive memory consumption
|
|
|
On Tue, Jul 18, 2006 at 08:53:51PM -0400, Joshua Slive wrote:
| Quote: | On 7/14/06, John Morrissey <jwm@horde.net> wrote:
On Tue, Jun 06, 2006 at 11:12:17AM -0400, Joshua Slive wrote:
On 6/6/06, John Morrissey <jwm@horde.net> wrote:
I'm having a problem with Apache 2.0.54 (we're running the Debian
packages for 2.0.54-5). Periodically, a single Apache child will
rapidly consume all available memory on the machine - once the
memory consumption starts, it only takes five or ten minutes (at
most) for it to exhaust available memory.
Are any of the requests byte-ranges (response code 206). If so, see:
http://issues.apache.org/bugzilla/show_bug.cgi?id=29962
|
Some are, yes. It looks like the Debian 2.0.54-5 packages already include
the patch attached to that bug (the one in the source package is identical
to the one posted in the bug).
I also looked at bug 23567 (and 34589, which is a duplicate) but the only
filter we have enabled is INCLUDES (mod_include). None of the suspect
requests was for server-parsed HTML *and* a byte-range request (206
response).
john
--
John Morrissey _o /\ ---- __o
jwm@horde.net _-< \_ / \ ---- < \,
www.horde.net/ __(_)/_(_)________/ \_______(_) /_(_)__
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org |
|
| Back to top |
|
|
Joshua Slive
*nix forums Guru
Joined: 07 Feb 2005
Posts: 1647
|
| Posted: Wed Jul 19, 2006 12:53 am Post subject:
Re: Excessive memory consumption
|
|
|
On 7/14/06, John Morrissey <jwm@horde.net> wrote:
| Quote: | Hi Joshua--
On Tue, Jun 06, 2006 at 11:12:17AM -0400, Joshua Slive wrote:
On 6/6/06, John Morrissey <jwm@horde.net> wrote:
I'm having a problem with Apache 2.0.54 (we're running the Debian
packages for 2.0.54-5). Periodically, a single Apache child will rapidly
consume all available memory on the machine - once the memory
consumption starts, it only takes five or ten minutes (at most) for it
to exhaust available memory.
Change your LogFormat to include the PID of the serving process. Then
you can go back and correlate teh PID of the memory hog with the
requests it recently served. (See also mod_log_forensic, which will
be necessary if the bad request never finishes.)
Thanks for your help. I've tried both, and it seems the errant children are
only serving static content and mod_rewrite-generated redirects (returning
302s). The forensic logs back this up; there are only a handful of
uncompleted requests each day, all for static content.
Interestingly, it seems some children continue to serve requests while
leaking huge amounts of RAM. Here's a recent example. Our errant process
killer activated at 23:36:24. sar(1) says:
time kbramused %swpused
22:45:04 645516 0.48
22:55:05 2010532 0.48
23:05:04 2025148 50.44
23:15:02 2025696 55.02
23:36:26 769572 3.58
So sometime between 22:45 and 22:55, this child began leaking. The access
logs indicate this child continued to serve static content (except for one
exception, see below) during this period, ~375 requests more or less evenly
spaced over time.
The only exception to this even spacing is thus: at 23:25:41, it served a
redirect, then at 23:36:20 apparently served its last request (484 bytes of
static HTML) before being killed. I suspect this gap is because the machine
became so RAM-tight that it was swapping heavily.
The only dynamic content served by this child during this time period is a
call to wwwcount (http://www.muquit.com/muquit/software/Count/Count.html) at
22:46:46, but I'm inclined to discount this as coincidence since the same
child served identical wwwcount requests at 22:25:35, 22:23:52, 22:03:40,
22:01:21 (... ad infinitum). Also, wwwcount requests account for a
nontrivial amount of these machines' traffic, but we're only seeing a couple
errant processes a day, at most.
I'm at a loss. FWIW, here's a link to my original post, since it's been
about a month:
http://marc.theaimsgroup.com/?l=apache-httpd-users&m=114960657316006&w=2
Any other ideas, or things I can try?
|
Are any of the requests byte-ranges (response code 206). If so, see:
http://issues.apache.org/bugzilla/show_bug.cgi?id=29962
Joshua.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org |
|
| Back to top |
|
|
John Morrissey
*nix forums beginner
Joined: 06 Jun 2006
Posts: 3
|
| Posted: Fri Jul 14, 2006 12:09 pm Post subject:
Re: Excessive memory consumption
|
|
|
Hi Joshua--
On Tue, Jun 06, 2006 at 11:12:17AM -0400, Joshua Slive wrote:
| Quote: | On 6/6/06, John Morrissey <jwm@horde.net> wrote:
I'm having a problem with Apache 2.0.54 (we're running the Debian
packages for 2.0.54-5). Periodically, a single Apache child will rapidly
consume all available memory on the machine - once the memory
consumption starts, it only takes five or ten minutes (at most) for it
to exhaust available memory.
Change your LogFormat to include the PID of the serving process. Then
you can go back and correlate teh PID of the memory hog with the
requests it recently served. (See also mod_log_forensic, which will
be necessary if the bad request never finishes.)
|
Thanks for your help. I've tried both, and it seems the errant children are
only serving static content and mod_rewrite-generated redirects (returning
302s). The forensic logs back this up; there are only a handful of
uncompleted requests each day, all for static content.
Interestingly, it seems some children continue to serve requests while
leaking huge amounts of RAM. Here's a recent example. Our errant process
killer activated at 23:36:24. sar(1) says:
time kbramused %swpused
22:45:04 645516 0.48
22:55:05 2010532 0.48
23:05:04 2025148 50.44
23:15:02 2025696 55.02
23:36:26 769572 3.58
So sometime between 22:45 and 22:55, this child began leaking. The access
logs indicate this child continued to serve static content (except for one
exception, see below) during this period, ~375 requests more or less evenly
spaced over time.
The only exception to this even spacing is thus: at 23:25:41, it served a
redirect, then at 23:36:20 apparently served its last request (484 bytes of
static HTML) before being killed. I suspect this gap is because the machine
became so RAM-tight that it was swapping heavily.
The only dynamic content served by this child during this time period is a
call to wwwcount (http://www.muquit.com/muquit/software/Count/Count.html) at
22:46:46, but I'm inclined to discount this as coincidence since the same
child served identical wwwcount requests at 22:25:35, 22:23:52, 22:03:40,
22:01:21 (... ad infinitum). Also, wwwcount requests account for a
nontrivial amount of these machines' traffic, but we're only seeing a couple
errant processes a day, at most.
I'm at a loss. FWIW, here's a link to my original post, since it's been
about a month:
http://marc.theaimsgroup.com/?l=apache-httpd-users&m=114960657316006&w=2
Any other ideas, or things I can try?
thanks,
john
--
John Morrissey _o /\ ---- __o
jwm@horde.net _-< \_ / \ ---- < \,
www.horde.net/ __(_)/_(_)________/ \_______(_) /_(_)__
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org |
|
| Back to top |
|
|
Joshua Slive
*nix forums Guru
Joined: 07 Feb 2005
Posts: 1647
|
| Posted: Tue Jun 06, 2006 3:12 pm Post subject:
Re: Excessive memory consumption
|
|
|
On 6/6/06, John Morrissey <jwm@horde.net> wrote:
| Quote: | I'm having a problem with Apache 2.0.54 (we're running the Debian packages
for 2.0.54-5). Periodically, a single Apache child will rapidly consume all
available memory on the machine - once the memory consumption starts, it
only takes five or ten minutes (at most) for it to exhaust available memory.
We're running it on a cluster of four identical machines (hardware, OS,
configuration, etc.) and are seeing this problem across all of them.
Right now, we have a cron job that spawns every five minutes to kill off
errant children, and it's triggered a handful of times per day on these
machines.
Some configuration details:
- Prefork MPM
- Modules: cgi headers include ldap_userdir mime_magic php4 rewrite userdir
Most content is static (HTML pages, images, etc.). This cluster takes fairly
little PHP traffic, but what PHP it does do is important, so I can't disable
PHP for testing. We have another cluster that takes heavy PHP traffic (~95%
of its total hits) on identical hard/software versions that run with no
problem, so I'm inclined to rule PHP out.
Here's an example of an errant process before it was killed by our cron job:
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
www-data 10354 0.0 88.5 2861024 1839504 ? D 14:06 0:37 /usr/sbin/apache2+-k start -DSSL
|
Change your LogFormat to include the PID of the serving process. Then
you can go back and correlate teh PID of the memory hog with the
requests it recently served. (See also mod_log_forensic, which will
be necessary if the bad request never finishes.)
Joshua.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org |
|
| Back to top |
|
|
John Morrissey
*nix forums beginner
Joined: 06 Jun 2006
Posts: 3
|
| Posted: Tue Jun 06, 2006 3:09 pm Post subject:
Excessive memory consumption
|
|
|
I'm having a problem with Apache 2.0.54 (we're running the Debian packages
for 2.0.54-5). Periodically, a single Apache child will rapidly consume all
available memory on the machine - once the memory consumption starts, it
only takes five or ten minutes (at most) for it to exhaust available memory.
We're running it on a cluster of four identical machines (hardware, OS,
configuration, etc.) and are seeing this problem across all of them.
Right now, we have a cron job that spawns every five minutes to kill off
errant children, and it's triggered a handful of times per day on these
machines.
Some configuration details:
- Prefork MPM
- Modules: cgi headers include ldap_userdir mime_magic php4 rewrite userdir
Most content is static (HTML pages, images, etc.). This cluster takes fairly
little PHP traffic, but what PHP it does do is important, so I can't disable
PHP for testing. We have another cluster that takes heavy PHP traffic (~95%
of its total hits) on identical hard/software versions that run with no
problem, so I'm inclined to rule PHP out.
Here's an example of an errant process before it was killed by our cron job:
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
www-data 10354 0.0 88.5 2861024 1839504 ? D 14:06 0:37 /usr/sbin/apache2+-k start -DSSL
The machine is actively swapping by this point, so I presume that's why it's
in disk wait. Backtraces for some recently killed processes are below; I'm
unsure of how many of them to trust, since some have sections like:
#30 0x0837d970 in ?? ()
#31 0x00000004 in ?? ()
#32 0x0837d970 in ?? ()
I checked the changelog for 2.0.58 as well as issues.a.o/bugzilla/, and
nothing pops out as a likely fix. If the Apache configuration on these
machines would be useful, I can also provide that. Any thoughts?
thanks!
john
#0 0x401a6599 in apr_brigade_cleanup () from /usr/lib/libaprutil-0.so.0
#1 0x401a660a in apr_brigade_destroy () from /usr/lib/libaprutil-0.so.0
#2 0x0808ee3b in ap_core_translate ()
#3 0x08086111 in ap_pass_brigade ()
#4 0x08086111 in ap_pass_brigade ()
#5 0x080676d1 in ap_http_header_filter ()
#6 0x08086111 in ap_pass_brigade ()
#7 0x08088bae in ap_content_length_filter ()
#8 0x08086111 in ap_pass_brigade ()
#9 0x08069128 in ap_byterange_filter ()
#10 0x08086111 in ap_pass_brigade ()
#11 0x4058bd05 in ?? () from /usr/lib/apache2/modules/mod_headers.so
#12 0x083683f8 in ?? ()
#13 0x0837c5d0 in ?? ()
#14 0x0837c1b0 in ?? ()
#15 0x00000000 in ?? ()
#16 0x081ad860 in ?? ()
#17 0x4058c360 in ?? () from /usr/lib/apache2/modules/mod_headers.so
#18 0xbfffe1f8 in ?? ()
#19 0x0837c5d4 in ?? ()
#20 0x08366368 in ?? ()
#21 0x083677a8 in ?? ()
#22 0xbfffe1f8 in ?? ()
#23 0x08086111 in ap_pass_brigade ()
#24 0x08086111 in ap_pass_brigade ()
#25 0x0808e387 in ap_core_translate ()
#26 0x08078375 in ap_run_handler ()
#27 0x08078980 in ap_invoke_handler ()
#28 0x08069c6a in ap_process_request ()
#29 0x0806512d in _start ()
#30 0x083677a8 in ?? ()
#31 0x00000004 in ?? ()
#32 0x083677a8 in ?? ()
#33 0x0808370c in ap_run_pre_connection ()
#34 0x080835c5 in ap_run_process_connection ()
#35 0x08076974 in ap_graceful_stop_signalled ()
#36 0x08076ac7 in ap_graceful_stop_signalled ()
#37 0x08076d59 in ap_graceful_stop_signalled ()
#38 0x08077445 in ap_mpm_run ()
#39 0x0807da8d in main ()
#0 0x4030afc0 in apr_allocator_set_mutex () from /usr/lib/libapr-0.so.0
#1 0x401a72f9 in apr_brigade_vprintf () from /usr/lib/libaprutil-0.so.0
#2 0x4030a76d in apr_pool_cleanup_run () from /usr/lib/libapr-0.so.0
#3 0x40309ead in apr_pool_destroy () from /usr/lib/libapr-0.so.0
#4 0x08075fc9 in ap_run_status_hook ()
#5 0x080768a5 in ap_graceful_stop_signalled ()
#6 0x08076ac7 in ap_graceful_stop_signalled ()
#7 0x08076d59 in ap_graceful_stop_signalled ()
#8 0x08077445 in ap_mpm_run ()
#9 0x0807da8d in main ()
#0 0x4035688c in accept () from /lib/tls/libpthread.so.0
#1 0x40302d29 in apr_socket_accept () from /usr/lib/libapr-0.so.0
#2 0x403033fd in apr_accept () from /usr/lib/libapr-0.so.0
#3 0x0809449e in unixd_accept ()
#4 0x080768f6 in ap_graceful_stop_signalled ()
#5 0x08076ac7 in ap_graceful_stop_signalled ()
#6 0x08076d59 in ap_graceful_stop_signalled ()
#7 0x08077445 in ap_mpm_run ()
#8 0x0807da8d in main ()
#0 0x4030afc0 in apr_allocator_set_mutex () from /usr/lib/libapr-0.so.0
#1 0x401a72f9 in apr_brigade_vprintf () from /usr/lib/libaprutil-0.so.0
#2 0x4030a76d in apr_pool_cleanup_run () from /usr/lib/libapr-0.so.0
#3 0x40309ead in apr_pool_destroy () from /usr/lib/libapr-0.so.0
#4 0x08075fc9 in ap_run_status_hook ()
#5 0x080768a5 in ap_graceful_stop_signalled ()
#6 0x08076ac7 in ap_graceful_stop_signalled ()
#7 0x08076d59 in ap_graceful_stop_signalled ()
#8 0x08077445 in ap_mpm_run ()
#9 0x0807da8d in main ()
--
John Morrissey _o /\ ---- __o
jwm@horde.net _-< \_ / \ ---- < \,
www.horde.net/ __(_)/_(_)________/ \_______(_) /_(_)__
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org |
|
| Back to top |
|
|
Google
|
|
| Back to top |
|
|
|
|
The time now is Wed Dec 03, 2008 7:32 pm | All times are GMT
|
|
Internet Advertising | Internet Advertising | Free Advertising | Loans | Myspace Proxy
|
|
Copyright © 2004-2005 DeniX Solutions SRL
|
|
|
|
Other DeniX Solutions sites:
Unix/Linux blog |
electronics forum |
medicine forum |
science forum |
|
|
Privacy Policy
|
Powered by phpBB © 2001, 2005 phpBB Group
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
Forum index
»
Apps
»
Apache
