Le 06/09/2015 21:29, Bill Cole a écrit : >> Just after un upgrade, I happen to have an issue with Spamassassin that >> would refuse to start, giving a segmentation fault. > > You neglected to mention what you upgraded, but that generic problem > description is typical of a situation where something that you > upgraded includes a shared library that changed enough that you should > also have rebuilt everything that uses it, but did not. A segfault > usually isn't the result of a latent misconfiguration of a suite of > Perl modules (i.e. SpamAssassin) but rather the result of binary > executable code linked incorrectly. > > Rebuilding spamd would seem like a strong contender for a fix... Agreed.
I upgraded my Fedora server from v.21 to v.22. My spamd executable comes from an RPM package directly from the official repositories. As mentioned before, commenting out the lines about the MySQL support are effective, and spamd successfully starts. So it is undoubtedly related to this upgrade, and the "new" package (it's the same Spamassassin version, though), but I'm struggling to understand where the problem is. And I'm not really sure I want to build an executable from source instead of using the packaged one. So of course, my next step is to contact directly the support lists @Fedora, but I was hoping that maybe there was something to do here first. Cheers ! Hoggins!
signature.asc
Description: OpenPGP digital signature