You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@issues.apache.org on 2010/04/27 11:40:35 UTC
[Bug 6424] New: Spamd execution error after building SA version
3.3.1 into perl 5.8.8 on Solaris 9 Sparc
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6424
Summary: Spamd execution error after building SA version 3.3.1
into perl 5.8.8 on Solaris 9 Sparc
Product: Spamassassin
Version: 3.3.1
Platform: Sun
OS/Version: Solaris
Status: NEW
Severity: normal
Priority: P2
Component: spamc/spamd
AssignedTo: dev@spamassassin.apache.org
ReportedBy: kralizec.craig@gmail.com
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.
--
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[Bug 6424] Spamd execution error after building SA version 3.3.1
into perl 5.8.8 on Solaris 9 Sparc
Posted by bu...@issues.apache.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6424
John Hardin <jh...@impsec.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jhardin@impsec.org
--- Comment #1 from John Hardin <jh...@impsec.org> 2010-04-27 09:07:48 EDT ---
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?
--
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[Bug 6424] Spamd execution error after building SA version 3.3.1
into perl 5.8.8 on Solaris 9 Sparc
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6424
Kevin A. McGrail <km...@pccc.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |kmcgrail@pccc.com
Resolution| |WORKSFORME
--- Comment #2 from Kevin A. McGrail <km...@pccc.com> 2011-10-29 04:02:52 UTC ---
No response from reporter to questions. Closing as worksforme.
--
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.