Strange behavior with of scheduled reminders for Membership Renewal

[mudnik]

For some reason, the scheduled reminders for membership renewal has not been working.

A check of the scheduled log shows this:

Finished execution of Send Scheduled Reminders with result: Failure, Error message: DB Error: syntax error

I had a few scheduled reminders set up. When I disabled all of them, the job was able to execute without any DB error.

The culprit seems to be the reminder that has repetition activated. It was set to send 1 day after membership expires, and every two weeks until 8 weeks.

After the culprit was disabled, I went on the run the reminder jobs manually. I think when the job was in the midst of running, I accidentally went to run it again. Got this error message:

Finished execution of Send Scheduled Reminders with result: Failure, Error message: Could not acquire lock, another EmailProcessor process is running.

This is when things got haywire. The system (without my knowledge) started to sent out emails to everyone (all members past and present) even though the rule was set to "1 month before membership ends".

It even sent out reminders to non-members.

The membership expiry token in the email was also showing the wrong date. Could be a date many years ago.

I tried running the job a couple more times and got the could not acquire lock message again.

After waiting for some time, I went to run the job manually again. This time run, it gave me this error message:

Finished execution of Send Scheduled Reminders with result: Failure, Error message: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away

Got this error again after I tried running the job again.

When the emails were being sent out, I edited the wording of the reminder. It seems that those who received the first version of the reminder got another email with the updated version.

How should I debug/reset this?

[petednz]

Hi - we have had this issue - "It even sent out reminders to non-members" -though not for same reasons by sounds of it

Our problem occurred when i included an extra email to send reminders to

RECIPIENTS :  Also include : Choose recipient

by setting this and not including an email, or setting it with an email and then removing the emails and not resetting it to "Limit to" the system proceed to go "oh, there is a WHERE clause that is empty, lets starts from number one and work our way through your whole database"

Not happy outcome

just mentioning it in case it relates. Can't spot the ticket where this behaviour was discussed and solutions suggested - ah this one perhaps http://forum.civicrm.org/index.php/topic,34527.msg146786.html#msg146786

[mudnik]

Hi - we have had this issue - "It even sent out reminders to non-members" -though not for same reasons by sounds of it

Our problem occurred when i included an extra email to send reminders to

RECIPIENTS :  Also include : Choose recipient

by setting this and not including an email, or setting it with an email and then removing the emails and not resetting it to "Limit to" the system proceed to go "oh, there is a WHERE clause that is empty, lets starts from number one and work our way through your whole database"

Not happy outcome

just mentioning it in case it relates. Can't spot the ticket where this behaviour was discussed and solutions suggested - ah this one perhaps http://forum.civicrm.org/index.php/topic,34527.msg146786.html#msg146786

Hmm this could be the same reason. I have deleted that particular reminder though, so can't check.

But it's certainly a big minefield.