Segmentation fault

message originally sent from wrong email address

Hi all.

I have just installed RT2 on my rh7.2 box and am getting the following
error…

apachectl configtest
Syntax OK
/usr/sbin/apachectl: line 198: 1520 Segmentation fault $HTTPD -t

line 198 reads “Group apache”

Any suggestions on how to fix this?

CyberT
cybert@frontiernet.net

My guess as to the cause of this problem is any modules that use DBI must be
loaded after Apache::DBI. Be sure 'PerlModule Apache::DBI appears before
PerlModule Apache::Registry in your httpd.conf.

See this mod_perl thread for more information:
http://archive.davin.ottawa.on.ca/modperl/2001-09/msg00167.phtml

Take care,
George-----Original Message-----
From: CyberT [mailto:cybert@frontiernet.net]
Sent: Friday, May 03, 2002 1:20 AM
To: rt-users
Subject: [rt-users] segmentation fault

message originally sent from wrong email address

Hi all.

I have just installed RT2 on my rh7.2 box and am getting the following
error…

apachectl configtest
Syntax OK
/usr/sbin/apachectl: line 198: 1520 Segmentation fault $HTTPD -t

line 198 reads “Group apache”

Any suggestions on how to fix this?

CyberT
cybert@frontiernet.net

rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

This email message may contain information that is confidential and
proprietary to Babcock & Brown or a third party. If you are not the
intended recipient, please contact the sender and destroy the original and
any copies of the original message. Babcock & Brown takes measures to
protect the content of its communications. However, Babcock & Brown cannot
guarantee that email messages will not be intercepted by third parties or
that email messages will be free of errors or viruses.

Finally, we’ve tracked down the segmentation fault error people
reported about. Thanks to people for bringing attention to this
problem and providing reproducible examples. The fix is in 2.04
version of the Text::Quoted module and it’s on its way to CPAN
mirrors. People who can not wait and want install it asap can get it
using the following link.

http://pause.cpan.org/incoming/Text-Quoted-2.04.tar.gz

I’ve grabbed list of people who reported about this or similar
problems. Please, try again and report back. Don’t forget to
stop/start server and return back using of Text::Quoted if you
disabled it. In the latter case you have to clean mason cache too.

Best regards, Ruslan.

Hi,

My RT 4.2 instance is not working properly. Sometimes it gets errors in creating tickets or sending mails. Logs show segmentation faults of httpd. On of the cores I could get
shows that the segmentation happens in malloc

This RT is running in a virtual machine. At the beginning, it had 512 MB of RAM and was very slow when several sessions were open. Then we increased the RAM to 1 GB. The speed is now good but this strange behavior started.

Any ideas?

#0 0x00007fc929e9e245 in malloc_consolidate () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install httpd-2.2.15-29.el6.centos.x86_64
(gdb) where
#0 0x00007fc929e9e245 in malloc_consolidate () from /lib64/libc.so.6
#1 0x00007fc929ea13c5 in _int_malloc () from /lib64/libc.so.6
#2 0x00007fc929ea2951 in malloc () from /lib64/libc.so.6
#3 0x00007fc92109ab46 in Perl_safesysmalloc () from /usr/lib64/perl5/CORE/libperl.so
#4 0x00007fc9210bab41 in Perl_get_arena () from /usr/lib64/perl5/CORE/libperl.so
#5 0x00007fc9210babaa in ?? () from /usr/lib64/perl5/CORE/libperl.so
#6 0x00007fc9210c4bfb in Perl_sv_upgrade () from /usr/lib64/perl5/CORE/libperl.so
#7 0x00007fc9210c367f in Perl_sv_setsv_flags () from /usr/lib64/perl5/CORE/libperl.so
#8 0x00007fc9210ba03c in Perl_pp_sassign () from /usr/lib64/perl5/CORE/libperl.so
#9 0x00007fc9210b0af6 in Perl_runops_standard () from /usr/lib64/perl5/CORE/libperl.so
#10 0x00007fc921058268 in Perl_call_sv () from /usr/lib64/perl5/CORE/libperl.so
#11 0x00007fc92109a3d6 in ?? () from /usr/lib64/perl5/CORE/libperl.so
#12 0x00007fc92109cd12 in ?? () from /usr/lib64/perl5/CORE/libperl.so
#13 0x00007fc92109fe65 in Perl_vdie () from /usr/lib64/perl5/CORE/libperl.so
#14 0x00007fc92109ff88 in Perl_die () from /usr/lib64/perl5/CORE/libperl.so
#15 0x00007fc9210e0a02 in Perl_pp_rv2gv () from /usr/lib64/perl5/CORE/libperl.so
#16 0x00007fc9210b0af6 in Perl_runops_standard () from /usr/lib64/perl5/CORE/libperl.so
#17 0x00007fc9210585df in Perl_call_sv () from /usr/lib64/perl5/CORE/libperl.so
#18 0x00007fc92138f0be in modperl_callback () from /etc/httpd/modules/mod_perl.so
#19 0x00007fc92138f80b in modperl_callback_run_handlers () from /etc/httpd/modules/mod_perl.so
#20 0x00007fc92138fe0f in modperl_callback_per_dir () from /etc/httpd/modules/mod_perl.so
#21 0x00007fc92138975f in ?? () from /etc/httpd/modules/mod_perl.so
#22 0x00007fc921389ac6 in modperl_response_handler () from /etc/httpd/modules/mod_perl.so
#23 0x00007fc92b917bb0 in ap_run_handler ()
#24 0x00007fc92b91b46e in ap_invoke_handler ()
#25 0x00007fc92b926b30 in ap_process_request ()
#26 0x00007fc92b9239a8 in ?? ()
#27 0x00007fc92b91f6b8 in ap_run_process_connection ()
#28 0x00007fc92b92b977 in ?? ()
#29 0x00007fc92b92bc8a in ?? ()
#30 0x00007fc92b92bfbb in ap_mpm_run ()
#31 0x00007fc92b903900 in main ()

saludos,

José Luis Gordillo Ruiz
Coordinación de Supercómputo
UNAM

On Wed, 2014-02-05 at 18:50 -0600, José Luis Gordillo Ruiz

My RT 4.2 instance is not working properly. Sometimes it gets errors
in creating tickets or sending mails. Logs show segmentation faults of
httpd. On of the cores I could get
shows that the segmentation happens in malloc

This RT is running in a virtual machine. At the beginning, it had 512
MB of RAM and was very slow when several sessions were open. Then we
increased the RAM to 1 GB. The speed is now good but this strange
behavior started.

While segfaults are not the form I’d generally expect the failure to
take, this is likely still memory contention. What do your monitoring
tools tell you about memory usage on the box?

If you’re also running your database server on the same machine, I’d
expect 1G to definitely be insufficient.

  • Alex