G'day,
Just did a usual update and now mod_perl breaks apache with a seg fault.
In /etc/apache/httpd.conf
LoadModule perl_module /usr/lib/apache/1.3/mod_perl.so
Commenting out the above line and apache works fine.
I've got installed:
/usr/bin/dpkg -l '*mod-perl*' | grep ^ii
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==================-==================-====================================================
ii libapache-mod-perl 1.27-4 Integration of perl with the Apache web
server
ii libapache-mod-perl 1.29.0.1-1cvs20031 mod_perl documentation
An 'strace apache' shows:
open("/usr/local/share/perl/5.8.2/AutoLoader.pm", O_RDONLY|O_LARGEFILE) = -1 ENOENT
(No such file or directory)
stat64("/usr/lib/perl5/AutoLoader.pmc", 0xbfffb300) = -1 ENOENT (No such file or
directory)
open("/usr/lib/perl5/AutoLoader.pm", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file
or directory)
stat64("/usr/share/perl5/AutoLoader.pmc", 0xbfffb300) = -1 ENOENT (No such file or
directory)
open("/usr/share/perl5/AutoLoader.pm", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file
or directory)
stat64("/usr/lib/perl/5.8.2/AutoLoader.pmc", 0xbfffb300) = -1 ENOENT (No such file or
directory)
open("/usr/lib/perl/5.8.2/AutoLoader.pm", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such
file or directory)
stat64("/usr/share/perl/5.8.2/AutoLoader.pmc", 0xbfffb300) = -1 ENOENT (No such file
or directory)
open("/usr/share/perl/5.8.2/AutoLoader.pm", O_RDONLY|O_LARGEFILE) = 4
ioctl(4, TCGETS, 0xbfffb10c) = -1 ENOTTY (Inappropriate ioctl for device)
_llseek(4, 0, [0], SEEK_CUR) = 0
read(4, "package AutoLoader;\n\nuse strict;"..., 4096) = 4096
read(4, " \'lib\').\n #\n\n (my $calldir"..., 4096) = 841
_llseek(4, 4936, [4936], SEEK_SET) = 0
_llseek(4, 0, [4936], SEEK_CUR) = 0
close(4) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
Which is what lead me to look at mod_perl as the culprit ...
I'll be rebooting the box Monday morning, as I'm connected to the
net via South Africa's telskum provider for the weekend @ 7 Rand
if there's no interruption. Hopefully a reboot will fix it, probably
not though as this ain't no wincrap box, but you never know.
Any how this stuff really should not happen in testing, or should it?
Any ideas greatly appreciated.
Cheers, Sabio
--
>> Sabio
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
