Bug 6150 - spamd fails: /usr/bin/spamd line 2504
Summary: spamd fails: /usr/bin/spamd line 2504
Status: RESOLVED FIXED
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamc/spamd (show other bugs)
Version: 3.3.0
Hardware: Other Linux
: P2 major
Target Milestone: 3.3.0
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-07 10:59 UTC by Warren Togami
Modified: 2009-10-16 06:16 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Warren Togami 2009-07-07 10:59:37 UTC 
RHEL-4 or RHEL-5, spamd startup fails.

[root@xserver ~]# service spamassassin restart
Stopping spamd:                                            [FAILED]
Starting spamd: child process exited or timed out without signaling production of a PID file at /usr/bin/spamd line 2504.
                                                           [FAILED]

RHEL-4 perl-5.8.5-49.el4
RHEL-5 perl-5.8.8-18.el5_3.1
Comment 1 Warren Togami 2009-07-07 12:02:20 UTC 
My mistake.  Forgot to run sa-update.

I think too many people will complain about this.  I'm going to ship my own copy of the rules.
Comment 2 Warren Togami 2009-07-07 12:02:44 UTC 
not a bug
Comment 3 Justin Mason 2009-07-08 02:31:42 UTC 
we need a better error message though.  Is the "real" spamd stderr output being hidden by the init script, or does it really exit with that inscrutable message?

reopening just in case it really is that obtuse...
Comment 4 Mark Martinec 2009-07-08 03:23:42 UTC 
(In reply to comment #3)
> we need a better error message though.  Is the "real" spamd stderr output
> being hidden by the init script, or does it really exit with that
> inscrutable message?

The following is loosely related, a need for better reporting
the exit status of a crashed spamd child process: Bug 6127 Comment #19.

Bringing it here so as not to be forgotten:

| It's a pitty that spamd does not log the exit status of
| a failing process (the $? after a waitpid call).
Comment 5 Karsten Bräckelmann 2009-07-10 11:23:33 UTC 
(In reply to comment #1)
> I think too many people will complain about this.

Indeed, they will.  Raising Priority, Target Milestone 3.3.0.
Comment 6 Mark Martinec 2009-09-03 03:49:54 UTC 
> > we need a better error message though.  Is the "real" spamd stderr output
> > being hidden by the init script, or does it really exit with that
> > inscrutable message?
> 
> The following is loosely related, a need for better reporting
> the exit status of a crashed spamd child process: Bug 6127 Comment #19.
> 
> Bringing it here so as not to be forgotten:
>   It's a pitty that spamd does not log the exit status of
>   a failing process (the $? after a waitpid call).


  Bug 6150, Bug 6127, Bug 5981, Bug 5950, Bug 6191: let spamd
  log report a child process exit status or aborting condition
  in an informative way
Sending        lib/Mail/SpamAssassin/Util.pm
Sending        spamd/spamd.raw
Committed revision 810883.



The concern in #1 remains...
Comment 7 Mark Martinec 2009-10-16 06:16:14 UTC 
> The concern in #1 remains...

(In reply to comment #1)
> My mistake.  Forgot to run sa-update.
> I think too many people will complain about this.

Actually, this seems already to have been dealt with:

$ spamassassin -t <0.lis
config: no rules were found!  Do you need to run 'sa-update'?
  at /usr/local/bin/spamassassin line 403.

$ spamd -p 2555
[88930] error: config: no rules were found! Do you need to run 'sa-update'?
config: no rules were found!  Do you need to run 'sa-update'?


So I believe this can now be closed.