MailScanner Segmentation fault

joop · Post by **joop** » 13 Jan 2009, 08:16

Hello,
I try to install MailScanner on my new server. it worked very well before but in new installation I have some problem!
My server is a core 2 quad Q9300 with 8GB ram and CentOS 5.2 x86_64
here is my related application version:
MailScanner: 4.74.13
ClamAV: 0.94.2/8856
Perl: 5.8.8
PathTools: 3.29

the problem is that MailScanner continually restarting. here is the its log in /var/log/maillog:

Code: Select all

Jan 12 11:37:40 LSN-D1371 MailScanner[12810]: MailScanner E-Mail Virus Scanner version 4.74.13 starting...
Jan 12 11:37:40 LSN-D1371 MailScanner[12810]: Using SpamAssassin results cache
Jan 12 11:37:40 LSN-D1371 MailScanner[12810]: Connected to SpamAssassin cache database
Jan 12 11:37:45 LSN-D1371 MailScanner[12811]: MailScanner E-Mail Virus Scanner version 4.74.13 starting...
Jan 12 11:37:45 LSN-D1371 MailScanner[12811]: Using SpamAssassin results cache
Jan 12 11:37:45 LSN-D1371 MailScanner[12811]: Connected to SpamAssassin cache database
Jan 12 11:37:50 LSN-D1371 MailScanner[12813]: MailScanner E-Mail Virus Scanner version 4.74.13 starting...
Jan 12 11:37:50 LSN-D1371 MailScanner[12813]: Using SpamAssassin results cache
Jan 12 11:37:50 LSN-D1371 MailScanner[12813]: Connected to SpamAssassin cache database
Jan 12 11:37:55 LSN-D1371 MailScanner[12815]: MailScanner E-Mail Virus Scanner version 4.74.13 starting...
Jan 12 11:37:55 LSN-D1371 MailScanner[12815]: Using SpamAssassin results cache
Jan 12 11:37:55 LSN-D1371 MailScanner[12815]: Connected to SpamAssassin cache database
Jan 12 11:38:00 LSN-D1371 MailScanner[12816]: MailScanner E-Mail Virus Scanner version 4.74.13 starting...
Jan 12 11:38:00 LSN-D1371 MailScanner[12816]: Using SpamAssassin results cache
Jan 12 11:38:00 LSN-D1371 MailScanner[12816]: Connected to SpamAssassin cache database
Jan 12 11:38:05 LSN-D1371 MailScanner[12817]: MailScanner E-Mail Virus Scanner version 4.74.13 starting...
Jan 12 11:38:05 LSN-D1371 MailScanner[12817]: Using SpamAssassin results cache
Jan 12 11:38:05 LSN-D1371 MailScanner[12817]: Connected to SpamAssassin cache database

when I run it in debug mode I see the following error:

Code: Select all

# /usr/mailscanner/bin/MailScanner --debug
In Debugging mode, not forking...
Segmentation fault(unix)
Segmentation fault

I tried following:

config server.com/blog/index.php?itemid=263
config server.com/techfaq/faqlist.php?catid=5&faqid=14&page=2

please help me if some body had same problem before.

tnx

Post by **Sarah** » 13 Jan 2009, 10:55

We have seen this on one server, it seemed there was a problem with the compiled SpamAssassin rules. These are located in:

/var/lib/spamassassin/compiled/3.002004/

We removed that directory and commented out the following plugin in /etc/mail/spamassassin/v320.pre:

loadplugin Mail::SpamAssassin::Plugin::Rule2XSBody

Change it to:

# loadplugin Mail::SpamAssassin::Plugin::Rule2XSBody

Then restart MailScanner. That seemed to fix it on the server we looked at.

Regards,
Sarah

joop · Post by **joop** » 13 Jan 2009, 11:17

wow! it worked!:D
thanks Sarah.
you told that this problem related to compiled SA rules, so in the next SA update it will be back?

Post by **Sarah** » 13 Jan 2009, 17:28

It shouldn't come back if you comment out the Rule2XSBody plugin in /etc/mail/spamassassin/v320.pre.

Post by **Sarah** » 14 Jan 2009, 08:57

Are you still seeing this segmentation fault problem? I notice that you (I think it is you) posted to the MailScanner mailing list as well.

Post by **Sarah** » 05 Apr 2009, 19:00

I doubt it is related to the 64-bit OS because we had the same issue on one of our own 32-bit OS servers.

caryw · Post by **caryw** » 06 Apr 2009, 04:31

Judging by the fact that this thread was bumped today after months of inactivity it looks like this trouble will become much more widespread in the coming weeks.

I'm just posting here to say that I also encountered this exact same problem and Sarah's solution worked perfectly (Thanks Sarah!).

I'm going to post some Google fodder here as well, as my searches earlier pulled up nothing. When MailScanner was segfaulting the following errors appeared in /var/log/messages:

Apr 5 16:59:50 redacted kernel: MailScanner[876] general protection rip:313f6141fc rsp:e64549efc649b3c7 error:0
Apr 5 16:59:54 redacted MailScanner: Process did not exit cleanly, returned 0 with signal 11
Apr 5 16:59:55 redacted kernel: MailScanner[891] general protection rip:313f6141fc rsp:e64549efc649b3c7 error:0
Apr 5 16:59:59 redacted MailScanner: Process did not exit cleanly, returned 0 with signal 11
Apr 5 17:00:00 redacted kernel: MailScanner[894] general protection rip:313f6141fc rsp:e64549efc649b3c7 error:0
Apr 5 17:00:04 redacted MailScanner: Process did not exit cleanly, returned 0 with signal 11
Apr 5 17:00:05 redacted kernel: MailScanner[914] general protection rip:313f6141fc rsp:e64549efc649b3c7 error:0
Apr 5 17:00:09 redacted MailScanner: Process did not exit cleanly, returned 0 with signal 11

The affected server also happened to be running the 64-bit version of CentOS:

root@redacted [~]# cat /etc/redhat-release
CentOS release 5.3 (Final)

root@redacted [~]# uname -a
Linux redacted.example.com 2.6.18-92.1.22.el5 #1 SMP Tue Dec 16 11:57:43 EST 2008 x86_64 x86_64 x86_64 GNU/Linux

root@redacted [~]# php -v
PHP 5.2.8 (cli) (built: Jan 30 2009 14:52:59)
Copyright (c) 1997-2008 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2008 Zend Technologies
with Zend Extension Manager v1.2.2, Copyright (c) 2003-2007, by Zend Technologies
with Suhosin v0.9.27, Copyright (c) 2007, by SektionEins GmbH
with Zend Optimizer v3.3.3, Copyright (c) 1998-2007, by Zend Technologies

I'm sure more people will have this trouble tomorrow (Monday) so I'm glad to get this one figured out on my slow day.

Thanks again Sarah! I'll watch this thread tomorrow.

- Cary
--Superb Internet Corp, Tier 3 Support