Hi,
I have a relatively small sample set, this is the output of yesterdays run:
status: starting scan stage now: 2018-12-04
10:00:22 AM
status: completed scan stage, 4560 messages now: 2018-12-04
10:00:24 AM
status: starting run stage now: 2018-12-04
10:00:24 AM
status: 10% ham: 397 spam: 60 date: 2012-12-18 now: 2018-12-04
10:01:29 AM
status: 20% ham: 793 spam: 121 date: 2014-04-09 now: 2018-12-04
10:02:39 AM
status: 30% ham: 1191 spam: 180 date: 2018-10-26 now: 2018-12-04
10:03:54 AM
status: 40% ham: 1592 spam: 236 date: 2016-02-04 now: 2018-12-04
10:05:35 AM
status: 50% ham: 1993 spam: 292 date: 2016-10-03 now: 2018-12-04
10:07:04 AM
status: 60% ham: 2388 spam: 354 date: 2017-03-30 now: 2018-12-04
10:08:21 AM
status: 70% ham: 2788 spam: 411 date: 2018-11-22 now: 2018-12-04
10:09:12 AM
status: 80% ham: 3184 spam: 472 date: 2018-03-11 now: 2018-12-04
10:11:11 AM
status: 90% ham: 3579 spam: 534 date: 2018-07-24 now: 2018-12-04
10:14:32 AM
status: completed run stage now: 2018-12-04
11:45:05 PM
Note that the progress was ok until the last 10%, where it took 13.5h in
stead of a few minutes. Definitely something is broken here...
Kind regards,
Tom
On 04-12-18 21:53, Kevin A. McGrail wrote:
Yes, Jarif was saying the same thing is happening to him. I just cross
posted his email to the system admins. Might need to trace back to
changes for the past few days.
Regards,
KAM
--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171
On Tue, Dec 4, 2018 at 3:41 PM Steven Ihde <[email protected]
<mailto:[email protected]>> wrote:
Anybody else having trouble with this? Second (third?) morning in a row
I've found perl processing spinning at 100% CPU, hours after they should
have been done, and killed them. Based on the output looks like they
both hung around 30% of the way through. If it happens again I'll try to
debug a little to figure out where they are hanging.
