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...@bugzilla.spamassassin.org on 2009/07/07 19:59:38 UTC

[Bug 6150] New: spamd fails: /usr/bin/spamd line 2504

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6150

           Summary: spamd fails: /usr/bin/spamd line 2504
           Product: Spamassassin
           Version: 3.3.0
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P3
         Component: spamc/spamd
        AssignedTo: dev@spamassassin.apache.org
        ReportedBy: wtogami@redhat.com


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

-- 
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 6150] spamd fails: /usr/bin/spamd line 2504

Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6150


Karsten Bräckelmann <gu...@rudersport.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P2
   Target Milestone|Undefined                   |3.3.0




--- Comment #5 from Karsten Bräckelmann <gu...@rudersport.de>  2009-07-10 11:23:33 PST ---
(In reply to comment #1)
> I think too many people will complain about this.

Indeed, they will.  Raising Priority, Target Milestone 3.3.0.

-- 
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 6150] spamd fails: /usr/bin/spamd line 2504

Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6150


Justin Mason <jm...@jmason.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |




--- Comment #3 from Justin Mason <jm...@jmason.org>  2009-07-08 02:31:42 PST ---
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...

-- 
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 6150] spamd fails: /usr/bin/spamd line 2504

Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6150

Mark Martinec <Ma...@ijs.si> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |FIXED

--- Comment #7 from Mark Martinec <Ma...@ijs.si> 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.

-- 
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 6150] spamd fails: /usr/bin/spamd line 2504

Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6150





--- Comment #6 from Mark Martinec <Ma...@ijs.si>  2009-09-03 03:49:54 PST ---
> > 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 ( https://svn.apache.org/viewcvs.cgi?view=rev&rev=810883 ).



The concern in #1 remains...

-- 
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 6150] spamd fails: /usr/bin/spamd line 2504

Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6150





--- Comment #4 from Mark Martinec <Ma...@ijs.si>  2009-07-08 03:23:42 PST ---
(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).

-- 
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 6150] spamd fails: /usr/bin/spamd line 2504

Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6150


Warren Togami <wt...@redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




--- Comment #2 from Warren Togami <wt...@redhat.com>  2009-07-07 12:02:44 PST ---
not a bug

-- 
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 6150] spamd fails: /usr/bin/spamd line 2504

Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6150





--- Comment #1 from Warren Togami <wt...@redhat.com>  2009-07-07 12:02:20 PST ---
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.

-- 
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.