http://bugzilla.spamassassin.org/show_bug.cgi?id=3138
------- Additional Comments From felicity@kluge.net 2004-03-08 07:08 -------
Subject: Re: New: spamassassin crashs when port 2703 is blocked
On Mon, Mar 08, 2004 at 02:30:08AM -0800, bugzilla-daemon@bugzilla.spamassassin.org wrote:
> Process 84466 attached - interrupt to quit
> stat("/root/.razor/servers.discovery.lst.lock", 0x281abd00) = -1 ENOENT (No such
> file or directory)
[...]
> pid 26104 (perl5.8.2), uid 1041: exited on signal 11
> pid 60540 (perl5.8.2), uid 1041: exited on signal 11
> pid 8318 (perl5.8.2), uid 1041: exited on signal 11
> pid 27513 (perl5.8.2), uid 1041: exited on signal 11
> pid 22388 (perl5.8.2), uid 1041: exited on signal 11
Hmmm! Well, 2703 (as shown above) is all about razor which should
timeout after 10 seconds (by default). Did that seem to be the length
of time the discover failures occured?
As for the SIG11... That kind of indicates a problem with your perl
install or hardware (perl programs can't cause segfaults in and of
themselves).
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
------- Additional Comments From felicity@kluge.net 2004-03-08 07:08 -------
Subject: Re: New: spamassassin crashs when port 2703 is blocked
On Mon, Mar 08, 2004 at 02:30:08AM -0800, bugzilla-daemon@bugzilla.spamassassin.org wrote:
> Process 84466 attached - interrupt to quit
> stat("/root/.razor/servers.discovery.lst.lock", 0x281abd00) = -1 ENOENT (No such
> file or directory)
[...]
> pid 26104 (perl5.8.2), uid 1041: exited on signal 11
> pid 60540 (perl5.8.2), uid 1041: exited on signal 11
> pid 8318 (perl5.8.2), uid 1041: exited on signal 11
> pid 27513 (perl5.8.2), uid 1041: exited on signal 11
> pid 22388 (perl5.8.2), uid 1041: exited on signal 11
Hmmm! Well, 2703 (as shown above) is all about razor which should
timeout after 10 seconds (by default). Did that seem to be the length
of time the discover failures occured?
As for the SIG11... That kind of indicates a problem with your perl
install or hardware (perl programs can't cause segfaults in and of
themselves).
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.