Bug 1226523

Summary:	spamd segfaulting
Product:	[Fedora] Fedora	Reporter:	Lance Lassetter <lancelassetter>
Component:	perl	Assignee:	Jitka Plesnikova <jplesnik>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	22	CC:	cweyl, iarnell, jjelen, jplesnik, kasal, kevin, lancelassetter, nb, perl-devel, plautrba, ppisar, psabata, rc040203, tcallawa, wtogami
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-06-01 09:28:44 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lance Lassetter 2015-05-30 09:06:04 UTC

Description of problem:

in dmesg:

[Sat May 30 03:54:01 2015] spamd[10130]: segfault at 5 ip 00007f0d6a1762
6e sp 00007ffea55fa3c0 error 4 in Base64.so[7f0d6a174000+3000]
Version-Release number of selected component (if applicable):


How reproducible:

upgrade to Fedora 22 with fedup.  Options in /etc/sysconfig/spamassassin are:

# Options to spamd
SPAMDOPTIONS="-u spamd -g spamd -x --siteconfigpath=/etc/mail/spamassass
in -m5"

Steps to Reproduce:
1. upgrade from Fedora 21 to 22 with fedup
2. restore /etc/sysconfig/spamassassin settings
3. re-enable spamassassin in systemd

Actual results:
 
spamd segfaults

Expected results:

normal operation expected as in Fedora 21

Additional info:

Please request additional debug information if neeeded.  With dnf there is no way to upgrade or downgrade the package.  Package version is spamassassin-3.4.1-2.fc22.x86_64

Comment 1 Kevin Fenzi 2015-05-30 17:37:55 UTC

The Base64.so is in base perl package. Moving over there for perl maintainers to look into... 

You might provide if you can: 

rpm -q perl
rpm -V perl
locate Base64.so

Comment 2 Lance Lassetter 2015-05-31 01:48:32 UTC

$ rpm -q perl
perl-5.20.2-325.fc22.x86_64

rpm -V perl there is no output

locate Base64.so
/usr/lib64/perl5/auto/MIME/Base64/Base64.so
/usr/lib64/perl5/vendor_perl/auto/APR/Base64/Base64.so
/usr/local/lib64/perl5/auto/MIME/Base64/Base64.so

As a side note I did install some cpan stuff which might have upgraded perl.  Any way to delete all of it?

perl -V
...
  Built under linux
  Compiled at Apr 15 2015 11:15:41
  @INC:
    /usr/local/lib64/perl5
    /usr/local/share/perl5
    /usr/lib64/perl5/vendor_perl
    /usr/share/perl5/vendor_perl
    /usr/lib64/perl5
    /usr/share/perl5

This is most probably the problem.  I am sorry.  I probably tried to install a perl module through cpan to get SA dcc working and cpan upgraded perl?  I then manually removed some of what cpan installed and not all of it?

Lance

Comment 3 Lance Lassetter 2015-05-31 02:09:20 UTC

I think deleting lib64/perl in /usr/local fixed it.  I then installed two perl modules through cpan and made an SELinux exception for dccproc and it seems to be working.  No more dmesg errors on perl.

Verified SA working with Postfix 3 on Fedora 22 with SA plugin DCC enabled.

Comment 4 Petr Pisar 2015-06-01 09:28:44 UTC

There is no easy way how to uinstall modules which were installed by cpan.

If you always install all the modules into the same location, you remove content of the directories. By default, modules installed by root goes into `site' directories. That's /usr/local/share/perl5 and /usr/local/lib64/perl5 on Fedora.

If you keep build directories in ~/.cpan/build, you can try to run `make uninstall' in all of them (this applies only to ExtUtils::MakeMaker driven build scripts).

Also you look into .packlist files in paths where you install your modules. The list files installed by cpan if did not disables creating .packlist files before.