First let me thank you very, very much for this really
great, hot stuff, perl request tracker!
And a short first question… noticed some segfaults in
the error log of apache. So I searched for some hints
in the mailinglists, but there seems to be no solution
to fix it (if I searched right).
But I’m sure, the most people here are runnig rt without this
problem, so it would be very helpfully if someone could
tell me what versions are working well.
here I’ve some trouble with:
Apache/1.3.19
mod_perl-1.26
perl-5.6.0
on SuSE Linux 7.1 (i386) with linux-2.2.19
should I sent some more perl module version numbers?
I’m not really surely which module causes the problem, so
any hints and clues are welcome!
And a short first question… noticed some segfaults in
the error log of apache. So I searched for some hints
in the mailinglists, but there seems to be no solution
to fix it (if I searched right).
…I found a hint in frequent.html shipped with mod_perl-1.26:
" Lots of SegFaults and other problems were reported by
users who had turned PerlFreshRestart On. Most of them have
gone away when it was turned off. It doesn’t mean that you
shouldn’t use it, if it works for you. Just beware of the dragons…"
I turned it off and had no segfault the last minutes… what
about this feature PerlFreshRestart - is it save not to use it?
I dont’t know enough about hacking perl with apache… :-/
It’s definitely safe not to use it. That’s good to know. I’ll revise
the docs.On Tue, Sep 25, 2001 at 06:31:49PM +0200, Stephan Lauffer wrote:
hi!
And a short first question… noticed some segfaults in
the error log of apache. So I searched for some hints
in the mailinglists, but there seems to be no solution
to fix it (if I searched right).
…I found a hint in frequent.html shipped with mod_perl-1.26:
" Lots of SegFaults and other problems were reported by
users who had turned PerlFreshRestart On. Most of them have
gone away when it was turned off. It doesn’t mean that you
shouldn’t use it, if it works for you. Just beware of the dragons…"
I turned it off and had no segfault the last minutes… what
about this feature PerlFreshRestart - is it save not to use it?
I dont’t know enough about hacking perl with apache… :-/
SL> I turned it off and had no segfault the last minutes… what
SL> about this feature PerlFreshRestart - is it save not to use it?
SL> I dont’t know enough about hacking perl with apache… :-/
PerlFreshRestart operates differently depending on how you build
mod_perl. If it is statically compiled into apache, what it does is
try to unload all the modules it has loaded, then re-run your perl
startup script. If it is dynamically loaded, it does that as well as
totally unloading the mod_perl.so and reloading it.
Under perl 5.6.1 the DSO version should be safe. For perl 5.005_03,
I’m experiencing massive memory leakage (about 8Mb per process,
depending on what’s loaded into perl.)
I think ultimately it depends on your perl version, and whether
mod_perl is DSO, and what your OS and OS version are.
If you experience seg faults on a freshly started up perl, then that
is not your problem. It should only affect you after you send a
SIGHUP or SIGUSR1 to apache.
It’s definitely safe not to use it. That’s good to know. I’ll revise
the docs.
hi!
And a short first question… noticed some segfaults in
the error log of apache. So I searched for some hints
in the mailinglists, but there seems to be no solution
to fix it (if I searched right).
…I found a hint in frequent.html shipped with mod_perl-1.26:
" Lots of SegFaults and other problems were reported by
users who had turned PerlFreshRestart On. Most of them have
gone away when it was turned off. It doesn’t mean that you
shouldn’t use it, if it works for you. Just beware of the dragons…"
I turned it off and had no segfault the last minutes… what
about this feature PerlFreshRestart - is it save not to use it?
I dont’t know enough about hacking perl with apache… :-/
Ah, I think I found it. I just changed this part of the
/etc/httpd/conf/httpd.conf:
Alias /perl/ /var/www/perl/
SetHandler perl-script
PerlHandler Apache::Registry
Options +ExecCGI
to:
PerlFreshRestart off <---------added this line
Alias /perl/ /var/www/perl/
SetHandler perl-script
PerlHandler Apache::Registry
Options +ExecCGI
No SegFaults since adding that and restarting apache.
At 12:02 PM 9/25/2001 -0700, Russ Johnson wrote:
Where is that option?
At 12:39 PM 9/25/2001 -0400, Jesse Vincent wrote:
It’s definitely safe not to use it. That’s good to know. I’ll revise
the docs.
hi!
And a short first question… noticed some segfaults in
the error log of apache. So I searched for some hints
in the mailinglists, but there seems to be no solution
to fix it (if I searched right).
…I found a hint in frequent.html shipped with mod_perl-1.26:
" Lots of SegFaults and other problems were reported by
users who had turned PerlFreshRestart On. Most of them have
gone away when it was turned off. It doesn’t mean that you
shouldn’t use it, if it works for you. Just beware of the dragons…"
I turned it off and had no segfault the last minutes… what
about this feature PerlFreshRestart - is it save not to use it?
I dont’t know enough about hacking perl with apache… :-/
Well, I spoke too soon. SegFaults are again happening.
At 02:37 PM 9/25/2001 -0700, Russ Johnson wrote:
Ah, I think I found it. I just changed this part of the
/etc/httpd/conf/httpd.conf:
Alias /perl/ /var/www/perl/
SetHandler perl-script
PerlHandler Apache::Registry
Options +ExecCGI
to:
PerlFreshRestart off <---------added this line
Alias /perl/ /var/www/perl/
SetHandler perl-script
PerlHandler Apache::Registry
Options +ExecCGI
No SegFaults since adding that and restarting apache.
At 12:02 PM 9/25/2001 -0700, Russ Johnson wrote:
Where is that option?
At 12:39 PM 9/25/2001 -0400, Jesse Vincent wrote:
It’s definitely safe not to use it. That’s good to know. I’ll revise
the docs.
hi!
And a short first question… noticed some segfaults in
the error log of apache. So I searched for some hints
in the mailinglists, but there seems to be no solution
to fix it (if I searched right).
…I found a hint in frequent.html shipped with mod_perl-1.26:
" Lots of SegFaults and other problems were reported by
users who had turned PerlFreshRestart On. Most of them have
gone away when it was turned off. It doesn’t mean that you
shouldn’t use it, if it works for you. Just beware of the dragons…"
I turned it off and had no segfault the last minutes… what
about this feature PerlFreshRestart - is it save not to use it?
I dont’t know enough about hacking perl with apache… :-/
Well, I spoke too soon. SegFaults are again happening.
actually our traffic is low… we’re just “playing with rt”
and adding some minor simple scripts… but I’ll keep on
watching it. but we’d not any segfaults since switching
PerlFreshRestart off.
Well, I spoke too soon. SegFaults are again happening.
actually our traffic is low… we’re just “playing with rt”
and adding some minor simple scripts… but I’ll keep on
watching it. but we’d not any segfaults since switching
PerlFreshRestart off.
ok - bad news… new segfaults.
Thanks Vivek and Richard - I’ll check your hints asap.
