digest emails not being sent

[Robert Marianski]

We received a report that digest emails were not being sent out. Based on the cron job, it should be running every 6 hours. I looked at the digest logs, and there are errors there. Here's an example:

2012-02-15 06:11:25,169 ERROR karl.utilities.alerts: Error sending digest to <email elided>
2012-02-15 06:11:25,170 ERROR karl.utilities.alerts: Traceback (most recent call last):
  File "/srv/osfkarl/production/40/eggs/karl-3.81-py2.6.egg/karl/utilities/alerts.py", line 119, in send_digests
    alerts=profile._pending_alerts),
TypeError: __call__() takes exactly 3 arguments (2 given)

I suppose we should have two courses of action:
1. Fix the error
2. Hook up the error monitor with the digest log

[Paul Everitt (paul-agendaless)]

I think it's worth doing at least the error monitor part pretty soon.

[Paul Everitt (paul-agendaless)]

Holy crap, this has been sitting here since February. :)

I also saw some other errors:

Error in daemon process

Traceback (most recent call last):
  File "/srv/osfkarl/deploy/1/eggs/karl-3.87-py2.6.egg/karl/scripting.py", line 95, in run_daemon
    func()
  File "/srv/osfkarl/deploy/1/eggs/karlserve-1.16-py2.6.egg/karlserve/scripts/main.py", line 160, in run
    func(args)
  File "/srv/osfkarl/deploy/1/eggs/karlserve-1.16-py2.6.egg/karlserve/scripts/mailin.py", line 26, in main
    mailin(args, instance)
  File "/srv/osfkarl/deploy/1/eggs/karlserve-1.16-py2.6.egg/karlserve/scripts/mailin.py", line 40, in mailin
    args.parser.error("postoffice.zodb_uri must be set in config file")
  File "/srv/osfkarl/deploy/1/eggs/argparse-1.1-py2.6.egg/argparse.py", line 2353, in error
    self.exit(2, _('%s: error: %s\n') % (self.prog, message))
  File "/srv/osfkarl/deploy/1/eggs/argparse-1.1-py2.6.egg/argparse.py", line 2341, in exit
    _sys.exit(status)
SystemExit: 2

[Chris Rossi (chris-archimedeanco)]

Branch 'fix-digest' is deployed on karldev for testing. I've temporarily set up a cronjob to call digest every 5 minutes so QA can test.

I've also sneakily snuck the fix onto production as a stopgap to shut the error monitor up.

[Paul Everitt (paul-agendaless)]

What's the right way for us to test?

--Paul

On Jun 1, 2012, at 5:13 PM, Chris Rossi wrote:

> Branch 'fix-digest' is deployed on karldev for testing. I've
> temporarily set up a cronjob to call digest every 5 minutes so QA can
> test.
>
> I've also sneakily snuck the fix onto production as a stopgap to shut
> the error monitor up.
>
> ** Changed in: karl3
> Status: In Progress => Fix Committed
>
> --
> You received this bug notification because you are subscribed to KARL3.
> https://bugs.launchpad.net/bugs/932865
>
> Title:
> digest emails not being sent
>
> Status in KARL3:
> Fix Committed
>
> Bug description:
> We received a report that digest emails were not being sent out. Based
> on the cron job, it should be running every 6 hours. I looked at the
> digest logs, and there are errors there. Here's an example:
>
> 2012-02-15 06:11:25,169 ERROR karl.utilities.alerts: Error sending digest to <email elided>
> 2012-02-15 06:11:25,170 ERROR karl.utilities.alerts: Traceback (most recent call last):
> File "/srv/osfkarl/production/40/eggs/karl-3.81-py2.6.egg/karl/utilities/alerts.py", line 119, in send_digests
> alerts=profile._pending_alerts),
> TypeError: __call__() takes exactly 3 arguments (2 given)
>
> I suppose we should have two courses of action:
> 1. Fix the error
> 2. Hook up the error monitor with the digest log
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/karl3/+bug/932865/+subscriptions

[Chris Rossi (chris-archimedeanco)]

Change your preferences to digest for some community, then generate
some alerts.

Chris

On Fri, Jun 1, 2012 at 5:26 PM, Paul Everitt <email address hidden> wrote:
> What's the right way for us to test?
>
> --Paul
>
> On Jun 1, 2012, at 5:13 PM, Chris Rossi wrote:
>
>> Branch 'fix-digest' is deployed on karldev for testing.  I've
>> temporarily set up a cronjob to call digest every 5 minutes so QA can
>> test.
>>
>> I've also sneakily snuck the fix onto production as a stopgap to shut
>> the error monitor up.
>>
>> ** Changed in: karl3
>>       Status: In Progress => Fix Committed
>>
>> --
>> You received this bug notification because you are subscribed to KARL3.
>> https://bugs.launchpad.net/bugs/932865
>>
>> Title:
>>  digest emails not being sent
>>
>> Status in KARL3:
>>  Fix Committed
>>
>> Bug description:
>>  We received a report that digest emails were not being sent out. Based
>>  on the cron job, it should be running every 6 hours. I looked at the
>>  digest logs, and there are errors there. Here's an example:
>>
>>  2012-02-15 06:11:25,169 ERROR karl.utilities.alerts: Error sending digest to <email elided>
>>  2012-02-15 06:11:25,170 ERROR karl.utilities.alerts: Traceback (most recent call last):
>>    File "/srv/osfkarl/production/40/eggs/karl-3.81-py2.6.egg/karl/utilities/alerts.py", line 119, in send_digests
>>      alerts=profile._pending_alerts),
>>  TypeError: __call__() takes exactly 3 arguments (2 given)
>>
>>  I suppose we should have two courses of action:
>>  1. Fix the error
>>  2. Hook up the error monitor with the digest log
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/karl3/+bug/932865/+subscriptions
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/932865
>
> Title:
>  digest emails not being sent
>
> Status in KARL3:
>  Fix Committed
>
> Bug description:
>  We received a report that digest emails were not being sent out. Based
>  on the cron job, it should be running every 6 hours. I looked at the
>  digest logs, and there are errors there. Here's an example:
>
>  2012-02-15 06:11:25,169 ERROR karl.utilities.alerts: Error sending digest to <email elided>
>  2012-02-15 06:11:25,170 ERROR karl.utilities.alerts: Traceback (most recent call last):
>    File "/srv/osfkarl/production/40/eggs/karl-3.81-py2.6.egg/karl/utilities/alerts.py", line 119, in send_digests
>      alerts=profile._pending_alerts),
>  TypeError: __call__() takes exactly 3 arguments (2 given)
>
>  I suppose we should have two courses of action:
>  1. Fix the error
>  2. Hook up the error monitor with the digest log
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/karl3/+bug/932865/+subscriptions

[Paul Everitt (paul-agendaless)]

Done, now we wait for the digest period.

--Paul

On Jun 1, 2012, at 7:03 PM, Chris Rossi wrote:

> Change your preferences to digest for some community, then generate
> some alerts.
>
> Chris
>
> On Fri, Jun 1, 2012 at 5:26 PM, Paul Everitt <email address hidden> wrote:
>> What's the right way for us to test?
>>
>> --Paul
>>
>> On Jun 1, 2012, at 5:13 PM, Chris Rossi wrote:
>>
>>> Branch 'fix-digest' is deployed on karldev for testing. I've
>>> temporarily set up a cronjob to call digest every 5 minutes so QA can
>>> test.
>>>
>>> I've also sneakily snuck the fix onto production as a stopgap to shut
>>> the error monitor up.
>>>
>>> ** Changed in: karl3
>>> Status: In Progress => Fix Committed
>>>
>>> --
>>> You received this bug notification because you are subscribed to KARL3.
>>> https://bugs.launchpad.net/bugs/932865
>>>
>>> Title:
>>> digest emails not being sent
>>>
>>> Status in KARL3:
>>> Fix Committed
>>>
>>> Bug description:
>>> We received a report that digest emails were not being sent out. Based
>>> on the cron job, it should be running every 6 hours. I looked at the
>>> digest logs, and there are errors there. Here's an example:
>>>
>>> 2012-02-15 06:11:25,169 ERROR karl.utilities.alerts: Error sending digest to <email elided>
>>> 2012-02-15 06:11:25,170 ERROR karl.utilities.alerts: Traceback (most recent call last):
>>> File "/srv/osfkarl/production/40/eggs/karl-3.81-py2.6.egg/karl/utilities/alerts.py", line 119, in send_digests
>>> alerts=profile._pending_alerts),
>>> TypeError: __call__() takes exactly 3 arguments (2 given)
>>>
>>> I suppose we should have two courses of action:
>>> 1. Fix the error
>>> 2. Hook up the error monitor with the digest log
>>>
>>> To manage notifications about this bug go to:
>>> https://bugs.launchpad.net/karl3/+bug/932865/+subscriptions
>>
>> --
>> You received this bug notification because you are a bug assignee.
>> https://bugs.launchpad.net/bugs/932865
>>
>> Title:
>> digest emails not being sent
>>
>> Status in KARL3:
>> Fix Committed
>>
>> Bug description:
>> We received a report that digest emails were not being sent out. Based
>> on the cron job, it should be running every 6 hours. I looked at the
>> digest logs, and there are errors there. Here's an example:
>>
>> 2012-02-15 06:11:25,169 ERROR karl.utilities.alerts: Error sending digest to <email elided>
>> 2012-02-15 06:11:25,170 ERROR karl.utilities.alerts: Traceback (most recent call last):
>> File "/srv/osfkarl/production/40/eggs/karl-3.81-py2.6.egg/karl/utilities/alerts.py", line 119, in send_digests
>> alerts=profile._pending_alerts),
>> TypeError: __call__() takes exactly 3 arguments (2 given)
>>
>> I suppose we should have two courses of action:
>> 1. Fix the error
>> 2. Hook up the error monitor with the digest log
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/karl3/+bug/932865/+subscriptions
>
> --
> You received this bug notification because you are subscribed to KARL3.
> https://bugs.launchpad.net/bugs/932865
>
> Title:
> digest emails not being sent
>
> Status in KARL3:
> Fix Committed
>
> Bug description:
> We rece...

[Chris Rossi (chris-archimedeanco)]

Should be ~5 minutes.

Chris

On Sat, Jun 2, 2012 at 8:31 AM, Paul Everitt <email address hidden> wrote:
> Done, now we wait for the digest period.
>
> --Paul
>
> On Jun 1, 2012, at 7:03 PM, Chris Rossi wrote:
>
>> Change your preferences to digest for some community, then generate
>> some alerts.
>>
>> Chris
>>
>> On Fri, Jun 1, 2012 at 5:26 PM, Paul Everitt <email address hidden> wrote:
>>> What's the right way for us to test?
>>>
>>> --Paul
>>>
>>> On Jun 1, 2012, at 5:13 PM, Chris Rossi wrote:
>>>
>>>> Branch 'fix-digest' is deployed on karldev for testing.  I've
>>>> temporarily set up a cronjob to call digest every 5 minutes so QA can
>>>> test.
>>>>
>>>> I've also sneakily snuck the fix onto production as a stopgap to shut
>>>> the error monitor up.
>>>>
>>>> ** Changed in: karl3
>>>>       Status: In Progress => Fix Committed
>>>>
>>>> --
>>>> You received this bug notification because you are subscribed to KARL3.
>>>> https://bugs.launchpad.net/bugs/932865
>>>>
>>>> Title:
>>>>  digest emails not being sent
>>>>
>>>> Status in KARL3:
>>>>  Fix Committed
>>>>
>>>> Bug description:
>>>>  We received a report that digest emails were not being sent out. Based
>>>>  on the cron job, it should be running every 6 hours. I looked at the
>>>>  digest logs, and there are errors there. Here's an example:
>>>>
>>>>  2012-02-15 06:11:25,169 ERROR karl.utilities.alerts: Error sending digest to <email elided>
>>>>  2012-02-15 06:11:25,170 ERROR karl.utilities.alerts: Traceback (most recent call last):
>>>>    File "/srv/osfkarl/production/40/eggs/karl-3.81-py2.6.egg/karl/utilities/alerts.py", line 119, in send_digests
>>>>      alerts=profile._pending_alerts),
>>>>  TypeError: __call__() takes exactly 3 arguments (2 given)
>>>>
>>>>  I suppose we should have two courses of action:
>>>>  1. Fix the error
>>>>  2. Hook up the error monitor with the digest log
>>>>
>>>> To manage notifications about this bug go to:
>>>> https://bugs.launchpad.net/karl3/+bug/932865/+subscriptions
>>>
>>> --
>>> You received this bug notification because you are a bug assignee.
>>> https://bugs.launchpad.net/bugs/932865
>>>
>>> Title:
>>>  digest emails not being sent
>>>
>>> Status in KARL3:
>>>  Fix Committed
>>>
>>> Bug description:
>>>  We received a report that digest emails were not being sent out. Based
>>>  on the cron job, it should be running every 6 hours. I looked at the
>>>  digest logs, and there are errors there. Here's an example:
>>>
>>>  2012-02-15 06:11:25,169 ERROR karl.utilities.alerts: Error sending digest to <email elided>
>>>  2012-02-15 06:11:25,170 ERROR karl.utilities.alerts: Traceback (most recent call last):
>>>    File "/srv/osfkarl/production/40/eggs/karl-3.81-py2.6.egg/karl/utilities/alerts.py", line 119, in send_digests
>>>      alerts=profile._pending_alerts),
>>>  TypeError: __call__() takes exactly 3 arguments (2 given)
>>>
>>>  I suppose we should have two courses of action:
>>>  1. Fix the error
>>>  2. Hook up the error monitor with the digest log
>>>
>>> To manage notifications about this bug go to:
>>> https://bugs.launchpad.net/karl3/+bug/932865/+subscriptions
>>
>> --
>> You received this bug notification because you are subscrib...

[Paul Everitt (paul-agendaless)]

Nope, didn't receive it.

--Paul

On Jun 2, 2012, at 10:38 AM, Chris Rossi wrote:

> Should be ~5 minutes.
>
> Chris
>
> On Sat, Jun 2, 2012 at 8:31 AM, Paul Everitt <email address hidden> wrote:
>> Done, now we wait for the digest period.
>>
>> --Paul
>>
>> On Jun 1, 2012, at 7:03 PM, Chris Rossi wrote:
>>
>>> Change your preferences to digest for some community, then generate
>>> some alerts.
>>>
>>> Chris
>>>
>>> On Fri, Jun 1, 2012 at 5:26 PM, Paul Everitt <email address hidden> wrote:
>>>> What's the right way for us to test?
>>>>
>>>> --Paul
>>>>
>>>> On Jun 1, 2012, at 5:13 PM, Chris Rossi wrote:
>>>>
>>>>> Branch 'fix-digest' is deployed on karldev for testing. I've
>>>>> temporarily set up a cronjob to call digest every 5 minutes so QA can
>>>>> test.
>>>>>
>>>>> I've also sneakily snuck the fix onto production as a stopgap to shut
>>>>> the error monitor up.
>>>>>
>>>>> ** Changed in: karl3
>>>>> Status: In Progress => Fix Committed
>>>>>
>>>>> --
>>>>> You received this bug notification because you are subscribed to KARL3.
>>>>> https://bugs.launchpad.net/bugs/932865
>>>>>
>>>>> Title:
>>>>> digest emails not being sent
>>>>>
>>>>> Status in KARL3:
>>>>> Fix Committed
>>>>>
>>>>> Bug description:
>>>>> We received a report that digest emails were not being sent out. Based
>>>>> on the cron job, it should be running every 6 hours. I looked at the
>>>>> digest logs, and there are errors there. Here's an example:
>>>>>
>>>>> 2012-02-15 06:11:25,169 ERROR karl.utilities.alerts: Error sending digest to <email elided>
>>>>> 2012-02-15 06:11:25,170 ERROR karl.utilities.alerts: Traceback (most recent call last):
>>>>> File "/srv/osfkarl/production/40/eggs/karl-3.81-py2.6.egg/karl/utilities/alerts.py", line 119, in send_digests
>>>>> alerts=profile._pending_alerts),
>>>>> TypeError: __call__() takes exactly 3 arguments (2 given)
>>>>>
>>>>> I suppose we should have two courses of action:
>>>>> 1. Fix the error
>>>>> 2. Hook up the error monitor with the digest log
>>>>>
>>>>> To manage notifications about this bug go to:
>>>>> https://bugs.launchpad.net/karl3/+bug/932865/+subscriptions
>>>>
>>>> --
>>>> You received this bug notification because you are a bug assignee.
>>>> https://bugs.launchpad.net/bugs/932865
>>>>
>>>> Title:
>>>> digest emails not being sent
>>>>
>>>> Status in KARL3:
>>>> Fix Committed
>>>>
>>>> Bug description:
>>>> We received a report that digest emails were not being sent out. Based
>>>> on the cron job, it should be running every 6 hours. I looked at the
>>>> digest logs, and there are errors there. Here's an example:
>>>>
>>>> 2012-02-15 06:11:25,169 ERROR karl.utilities.alerts: Error sending digest to <email elided>
>>>> 2012-02-15 06:11:25,170 ERROR karl.utilities.alerts: Traceback (most recent call last):
>>>> File "/srv/osfkarl/production/40/eggs/karl-3.81-py2.6.egg/karl/utilities/alerts.py", line 119, in send_digests
>>>> alerts=profile._pending_alerts),
>>>> TypeError: __call__() takes exactly 3 arguments (2 given)
>>>>
>>>> I suppose we should have two courses of action:
>>>> 1. Fix the error
>>>> 2. Hook up the error monitor with the dig...

[Chris Rossi (chris-archimedeanco)]

Which instance did you use to test? Which user on that instance?

[Paul Everitt (paul-agendaless)]

https://karldev.gocept.com/ux2/osf/communities/default/blog/digest-to-paul/

I changed Ad Min to have my email address, as the add member stuff is still broken (Balazs has to work on autocomplete.)

--Paul

On Jun 4, 2012, at 2:27 PM, Chris Rossi wrote:

> Which instance did you use to test? Which user on that instance?
>
> --
> You received this bug notification because you are subscribed to KARL3.
> https://bugs.launchpad.net/bugs/932865
>
> Title:
> digest emails not being sent
>
> Status in KARL3:
> In Progress
>
> Bug description:
> We received a report that digest emails were not being sent out. Based
> on the cron job, it should be running every 6 hours. I looked at the
> digest logs, and there are errors there. Here's an example:
>
> 2012-02-15 06:11:25,169 ERROR karl.utilities.alerts: Error sending digest to <email elided>
> 2012-02-15 06:11:25,170 ERROR karl.utilities.alerts: Traceback (most recent call last):
> File "/srv/osfkarl/production/40/eggs/karl-3.81-py2.6.egg/karl/utilities/alerts.py", line 119, in send_digests
> alerts=profile._pending_alerts),
> TypeError: __call__() takes exactly 3 arguments (2 given)
>
> I suppose we should have two courses of action:
> 1. Fix the error
> 2. Hook up the error monitor with the digest log
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/karl3/+bug/932865/+subscriptions

[Chris Rossi (chris-archimedeanco)]

Karldev wasn't running mailout. :( I did test and got digest to work manually. I've added mailout to karldev. Try again. Sorry!

[JimPGlenn (jpglenn09)]

digest messages delivered.