Ok, here is what happens after I removed the files from the directory and
left a dhandler there with a inherit => undef in the <%flags>. I also
tweaked apache as suggested (with the IfModule section), and restarted. I
called my home page and it took a couple of minutes to load. I ran strace -p
on the pid, with this repeating result
select(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
waitpid(-1, 0xbf8c8694, WNOHANG|WSTOPPED) = 0
select(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
waitpid(-1, 0xbf8c8694, WNOHANG|WSTOPPED) = 0
select(0, NULL, NULL, NULL, {1, 0}
The home page continued to hang, until it finally appeared. When I called a
file in the directory with the dhandler, the hang is longer, then finally a
blank page. Running the command
dmesg | tail -30 | grep killer
produces nothing.
When I run top as directed, apache2 is not at the top, and it shows no
memory increase when I call the web pages.
When I put the files back into the directoy and restart apache, the whole
things works fine again.
I have tried removed the obj files, but no luck. Just in case it might be of
interest, I used the directory as a repository for some basic html pages
that htdig was run over to create its database. My web pages are dynamically
created, but the text I want to be searchable is only the plain html pages.
I then wanted to removed the files and let the dhandler handle the request
for the files, but I can't remove the html files from the directory without
creating this strange hang.
Alfie-3 wrote:
>
> On Thu, Oct 07, 2010 at 11:11:13AM -0400, MK wrote:
>> Two minutes then a seg fault, together with the infinite recursion
>> possibility, imply something is eating a lot of memory then getting
>> killed. Since the server apparently survives, that could be a single
>> apache processes if you are running it forked not threaded, or it could
>> be something else.
>>
>> So here's a suggestion in addition to strace: before you make your
>> request, fire up "top" in a console. Press shift-f to select sort
>> field order and choose 'n', "memory usage". If this is a dedicated
>> server, apache should be at the top to begin with -- watch and see if
>> the mem usage grows rapidly and then the process gets killed by the
>> kernel.
>
> The following will confirm it:
>
> dmesg | tail -30 | grep killer
>
> Look for 'oom-killer' which is the Out of Memory Killer process. If you
> find this, than your apache processes are slowly growing (over the two
> minutes) and the kernel is killing them off.
>
> Alfie
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
> Spend less time writing and rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> Mason-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mason-users
>
>
--
View this message in context:
http://old.nabble.com/caching-problem-%28it-seems%29-tp29900372p29916678.html
Sent from the Perl Mason - Users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Mason-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mason-users
