Bug 6424

Summary:	Spamd execution error after building SA version 3.3.1 into perl 5.8.8 on Solaris 9 Sparc
Product:	Spamassassin	Reporter:	Craig Dewick <kralizec.craig>
Component:	spamc/spamd	Assignee:	SpamAssassin Developer Mailing List <dev>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	jhardin, kmcgrail
Priority:	P2
Version:	3.3.1
Target Milestone:	Undefined
Hardware:	Sun
OS:	Solaris
Whiteboard:

Description Craig Dewick 2010-04-27 05:40:32 UTC

I recently noticed that dev work on SpamAssassin had progressed and version 3.3.1 had been released.

I maintain a few Sun systems (Sparc-based machines) remotely and they are running Solaris 9 with Perl 5.8.8 installed. I use Postfix as my MTA have SpamAssassin integrated into Perl and Postfix uses it's components. Previously I had been running SA v3.2.4 since 3.2.5 would not install correctly into Perl 5.8.8 for some reason, so an update was very welcome.

I have an init script that I use to launch spamd at boot time and when I ran it manually to start up spamd following the build and installation of SA 3.3.1 using 'install Mail::SpamAssassin' at the CPAN shell prompt, I'm getting this error message:

# /etc/init.d/spamd start
# child process [8975] exited or timed out without signaling production of a PID file: exit 255 at /usr/local/bin/spamd line 2588.

Checking using 'pgrep spamd' reveals that there are indeed no spamd processes running.

Has anyone else encountered this problem and come up with a solution? I'm unable to upgrade the systems to Solaris 10 though I may look at trying a newer version of Perl. The installation of Perl I use is a pre-compiled one for Solaris 9 (Sparc) obtained from sunfreeware.com

Regards, Craig.

Comment 1 John Hardin 2010-04-27 09:07:48 UTC

Did you run sa-update?

Another thing that has changed for 3.3.x is the distribution of the initial rule set. The rules have been split from the code and installing the base rules is now a separate step, either by running sa-update or downloading and installing the current rules tarball.

The behaviour you're seeing, immediately after an install, really feels like SA has no rules and is giving up.

Do your logs confirm this? Does running "spamassassin --lint" from the command line confirm this?

Comment 2 Kevin A. McGrail 2011-10-29 04:02:52 UTC

No response from reporter to questions.  Closing as worksforme.