PERFECT! I rebuilt Apache and mod_perl works perfectly without the
urandom symlink hack. So if anyone else has the "server failed to
start!" problem again, the answer is to build Apache with --with-
devrandom=/dev/urandom (at least if they can live with the security
compromises.)
Now documented
Hi Stas! (and mod_perl crew! :-)
Stas Bekman <[EMAIL PROTECTED]> wrote at Sun, 7 Mar 2004 12:20:19 -0800
>> Unfortunately, you aren't the first one to hit this problem and not the
>> last one. So ideally we should find a way for the application to figure
>> out those things before it hangs and
The Doctor wrote:
On Fri, Mar 05, 2004 at 06:46:03PM -0800, Stas Bekman wrote:
A release candidate for mod_perl-1.99_13 is available:
http://apache.org/~stas/mod_perl-1.99_13-dev.tar.gz
Please test and report any failures to this list.
If everything goes well, 1.99_13 will be released on Tuesda
On Fri, Mar 05, 2004 at 06:46:03PM -0800, Stas Bekman wrote:
> A release candidate for mod_perl-1.99_13 is available:
>
> http://apache.org/~stas/mod_perl-1.99_13-dev.tar.gz
>
> Please test and report any failures to this list.
>
> If everything goes well, 1.99_13 will be released on Tuesday, so
>
> On closer inspection I think it's mostly okay because the session object
> is supposed to go out of scope and get destroyed (and thus untie) after
> every interaction, and the locking should mean that only process is
> writing during that time. You could run into trouble though if a
> process
All tests successful on my Win32: Apache/2.0.48 and
perl-5.8.3 (ActivePerl 809).
--
best regards,
randy
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
Hi Stas (and mod_perl community,)
Stas Bekman <[EMAIL PROTECTED]> wrote at Sat, 6 Mar 2004 16:38:39 -0800
>I've found this reference:
>http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=103049
>and it says that apr-0.9.3-14 solves the problem. But 2.0.48 comes with apr
>0.9.5 and supposedly sho
Jeffrey W. Baker wrote:
I wasn't aware of these issues before. Looks like I'll have to use
BerkeleyDB or Tie::DB_Lock or something.
On closer inspection I think it's mostly okay because the session object
is supposed to go out of scope and get destroyed (and thus untie) after
every interaction,
Unfortunately, you aren't the first one to hit this problem and not the
last one. So ideally we should find a way for the application to figure
out those things before it hangs and tell the user how to fix them or at
least print out the diagnosys information to help resolve the problem,
without
On Sun, 2004-03-07 at 09:31, Perrin Harkins wrote:
> Chris Ochs wrote:
> > This must be my day... I am stress testing a new application that uses
> > apache::session with the DB_File backend store. When hitting it with apache
> > bench after a few hundred connections something with the db file g
On Sat, 2004-03-06 at 08:33, John Kelly wrote:
> Hi,
>
> this is an oldbie question - i used to know something about mod_perl
> but haven't used it for so
> so long I've forgotten it all :)
>
> a mod_perl script i wrote quite some time ago has recently had
> increased "traffic". this has shown up
Hi there,
On Sat, 6 Mar 2004, Chris Ochs wrote:
> stress testing a new application that uses apache::session with the
> DB_File backend store. When hitting it with apache bench after a
> few hundred connections something with the db file gets wacked, and
> apache starts to segfault until I delet
Chris Ochs wrote:
This must be my day... I am stress testing a new application that uses
apache::session with the DB_File backend store. When hitting it with apache
bench after a few hundred connections something with the db file gets
wacked, and apache starts to segfault until I delete the .db
Chris Ochs wrote:
When I have apache::reload as an init handler in httpd.conf, apache
processes will randomly go from 20mb to 120 or sometimes over 500 mb of
memory. I haven't narrowed it down to an exact place in the code that
triggers it, because simply taking out apache::reload made it stop.
I
14 matches
Mail list logo
