[SOLVED] SpamAssassin Mail Filter Socket6.c: loadable library and perl binaries are mismatched
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
SpamAssassin Mail Filter Socket6.c: loadable library and perl binaries are mismatched
I've just upgraded to Slackware 15.0 on my main computer. I use the SpamAssassin Mail Filter daemon run by rc.spamd. This worked fine with 14.2, but with 15.0 I get:
Code:
Starting SpamAssassin Mail Filter Daemon: Socket6.c: loadable library and perl binaries are mismatched (got handshake key 0xdb00080, needed 0xeb00080)
I never deal with perl, so I don't even know how to [re]install any of this. I found instructions in reinstalling CPAN: 'cpan App::cpanminus', and on installing modules: 'cpanm Module::Name'. Should I do that? What module do I need?
https://www.linuxquestions.org/quest...0/#post6146003
It worked for me every time.
1. Stop Amavis (if you use it) and Spamassassin
2. Uninstall the previous version of Perl with removepkg
3. Move all related modules that were compiled with the previous version of Perl with the script in the link
4. Install the new version of Perl with installpkg
5. Install CPAN
6. Rebuild all desired Perl packages with the current version of Perl means Amavis, Spamassassin, etc
7. The folders moved by that script will be deleted
I have no idea what the previous version was so I just called it "versionX". Some of these were not found. I hope this is the script to which you were referring.
To install Perl, 'installpkg perl' didn't work, I had to do 'slackpkg install perl'.
I didn't notice your "or" on 'perl -MCPAN -e shell' or 'cpan' so I did both. I don't suppose that hurt. The 'perl -MCPAN -e shell' asked me to install 'install Term::ReadLine::Perl' so at the 'cpan[2]>' prompt I entered that. It installed and left me at the 'cpan>' prompt, so I typed "exit".
Being Perl-challenged, I didn't realize at first that your following commands were to be from within 'cpan', but I figured that out and did:
Test Summary Report
-------------------
t/svg.t (Wstat: 3328 (exited 13) Tests: 13 Failed: 13)
Failed tests: 1-13
Non-zero exit status: 13
Files=21, Tests=209, 2 wallclock secs ( 0.12 usr 0.02 sys + 1.71 cusr 0.23 csys = 2.08 CPU)
Result: FAIL
Failed 1/21 test programs. 13/209 subtests failed.
make: *** [Makefile:939: test_dynamic] Error 255
Cleaning up...
perl-Image-Info:
Would you like to continue processing the rest of the
queue or would you like to abort? If this failed
package is a dependency of another package in the queue
then it may not make sense to continue.
This isn't a mismatch error, but still seems Perl related.
I have no idea what the previous version was so I just called it "versionX". Some of these were not found. I hope this is the script to which you were referring.
To install Perl, 'installpkg perl' didn't work, I had to do 'slackpkg install perl'.
I didn't notice your "or" on 'perl -MCPAN -e shell' or 'cpan' so I did both. I don't suppose that hurt. The 'perl -MCPAN -e shell' asked me to install 'install Term::ReadLine::Perl' so at the 'cpan[2]>' prompt I entered that. It installed and left me at the 'cpan>' prompt, so I typed "exit".
Being Perl-challenged, I didn't realize at first that your following commands were to be from within 'cpan', but I figured that out and did:
Test Summary Report
-------------------
t/svg.t (Wstat: 3328 (exited 13) Tests: 13 Failed: 13)
Failed tests: 1-13
Non-zero exit status: 13
Files=21, Tests=209, 2 wallclock secs ( 0.12 usr 0.02 sys + 1.71 cusr 0.23 csys = 2.08 CPU)
Result: FAIL
Failed 1/21 test programs. 13/209 subtests failed.
make: *** [Makefile:939: test_dynamic] Error 255
Cleaning up...
perl-Image-Info:
Would you like to continue processing the rest of the
queue or would you like to abort? If this failed
package is a dependency of another package in the queue
then it may not make sense to continue.
This isn't a mismatch error, but still seems Perl related.
Any ideas?
Quote:
I have no idea what the previous version was so I just called it "versionX". Some of these were not found. I hope this is the script to which you were referring
It refers to the previous version of Perl installed.
Before the Perl update you can find it with the command:
Code:
ls /var/log/packages | grep perl
Quote:
To install Perl, 'installpkg perl' didn't work, I had to do 'slackpkg install perl'.
You use package management automation tools (slackpkg) but you could also take a look at the classic Slackware tools.
I don't use sbopkg to install packages (old man, old habits, that is, I install by compiling from sources the packages that are not official in Slackware) so I don't know if you install Spamassassin from here, but if you do, it is already a new version 4.0.0 and it will come in soon 4.0.1
You can find out the version of Spamassassin with the command:
Code:
slackpkg Info <packagename>
The error message needs to be debugged.
Maybe you don't have the librsvg/svgalib Slackware packages installed (check with above command "slackpkg Info"), or maybe a problem with the Perl modules that Spamassassin depends on (check here).
Is that the only error message that appears?
It refers to the previous version of Perl installed.
Before the Perl update you can find it with the command:
Code:
ls /var/log/packages | grep perl
I looked in /var/log/removed_packages and found perl-5.34.0-x86_64-2_slack15.0. So that is the same package I reinstalled.
Quote:
You use package management automation tools (slackpkg) but you could also take a look at the classic Slackware tools.
I don't use sbopkg to install packages (old man, old habits, that is, I install by compiling from sources the packages that are not official in Slackware) so I don't know if you install Spamassassin from here, but if you do, it is already a new version 4.0.0 and it will come in soon 4.0.1
You can find out the version of Spamassassin with the command:
Code:
slackpkg Info <packagename>
'slackpkg info' (or slackpkg search) doesn't work on installs from SlackBuilds, but 'spmassassin --version' gives 3.4.6, which is the current one in SlackBuilds.
Quote:
The error message needs to be debugged.
Maybe you don't have the librsvg/svgalib Slackware packages installed (check with above command "slackpkg Info"), or maybe a problem with the Perl modules that Spamassassin depends on (check here).
Is that the only error message that appears?
In fact, I aborted the build after I got that first "Would you like to continue processing ..." message. In order to answer your question I re-ran and answered 'Yes' to this question, and several more after that! In the end, spamassassin and spamd got built and installed. Perhaps those errors were for Perl modules SpamAssassin doesn't use?
I fired up spamd and spamass-milter and they ran and are running. It looks like the re-install and cpan stuff must have worked. I'll give this a day or so and see if it traps spam -- which I've been getting quite a bit of without my spamass-milter running. Stay tooned!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.