ERROR 500 after sending newsletter to 80K

[Timm]

Hey Stefano,

yesterday evening I was sending out my first campaign using your plugin coupled with Amazon SES. Testing with a group of about 10 recipients worked fine. So I sent the newsletter to 77.900 recipients, sending 10.000 per hour. Sadly I can’t access the plugin anymore now due to an ERROR 500.

I already tried several things:
– My server allows me to increase memory_limit to 128 MB and max_execution_time to 90 sek.
– Additionally I set wp_config.php to
define(‘WP_MEMORY_LIMIT’, ‘256M’);
define(‘WP_DEBUG’, true);
define( ‘WP_DEBUG_LOG’, true );

The main log ends with:

…
…
24-05-2018 23:03:12 – INFO – m: 43,2 MB, u: 0 – limits_exceeded> Max time set to 285
24-05-2018 23:08:33 – INFO – m: 43,2 MB, u: 0 – limits_exceeded> Max time set to 285
24-05-2018 23:13:17 – INFO – m: 43,2 MB, u: 0 – limits_exceeded> Max time set to 285
24-05-2018 23:18:36 – INFO – m: 37,2 MB, u: 0 – limits_exceeded> Max time set to 285
24-05-2018 23:23:14 – INFO – m: 29,7 MB, u: 0 – send> No more users, set as sent

In the Email log file I found the following entries. (The entries are from today, but the 500 issue appeared already yesterday night).

25-05-2018 07:02:18 – INFO – m: 37,3 MB, u: 1 – upgrade_query> Executing alter table sabt_newsletter_emails change column type type varchar(50) not null default ”
25-05-2018 07:02:18 – INFO – m: 37,3 MB, u: 1 – upgrade_query> Executing alter table sabt_newsletter_emails add column token varchar(10) not null default ”
25-05-2018 07:02:18 – INFO – m: 37,3 MB, u: 1 – upgrade_query> Executing alter table sabt_newsletter_emails drop column visibility
25-05-2018 07:02:18 – INFO – m: 37,3 MB, u: 1 – upgrade_query> Executing alter table sabt_newsletter_emails add column private tinyint(1) not null default 0

The Amazon SNS log is 1.7MB and start with:

— Handle the [SubscriptionConfirmation] notification
Type: SubscriptionConfirmation
SubscriptionConfirmation [URL: https://sns.eu-west-1.amazonaws.com/?Action=ConfirmSubscription&TopicArn=arn:aws:sns:eu-west-1:572259636868:wp_newsletter_bounce&Token=2336412f37fb687f5d51e6e241da92fd70a8ae965666bc4bb1541da70d337b3879e9c2261b6ccd81f0fb20a6d5d296ed24f4aa15cb53a3ad06abe2e014fae347219f40723668c39b9e770ef7332255ef0af539be549cac0bce44cd5671dc91307027714586ceca02cc583743ff0d32c86ed0081abbd8c9b41d5ae3ad662xyz%5D
— Handle the [SubscriptionConfirmation] notification
Type: SubscriptionConfirmation
SubscriptionConfirmation [URL: https://sns.eu-west-1.amazonaws.com/?Action=ConfirmSubscription&TopicArn=arn:aws:sns:eu-west-1:572259636868:wp_newsletter_bounce&Token=2336412f37fb687f5d51e6e241da92fd70a8ae965666bc4bb322872bdfcc79bbec649ef44b5671186219d24f8cb6a6187747c93378802316c949131c9536a128f68b62729e659111e2fd855366aa77b19ef60ea033bed357f772e0f7c65d2e4e5b726340de42da27a2656ca2f21846e49b34047c054f728bbcd95e42acc7xyz%5D
— Handle the [Notification] notification
Type: Notification
Handle the message
Process soft bounces:
[0] recipients
— Handle the [Notification] notification
Type: Notification
Handle the message
Process soft bounces:
[0] recipients
— Handle the [Notification] notification
Type: Notification
Handle the message
Process soft bounces:
Bounce type: Permanent
[1] recipients
Executing SQL: [update sabt_newsletter set status=’B’ where email=bounce@simulator.amazonses.com limit 1]

Hopefully you have some good advice for me.. 🙂
Thanks in advance
Timm

[Stefano]

Hi, the error 500 is in the whole blog? Error 500 is logged in the webserver error log, since the error 500 is returned by your webserver. Can you ask the provider that log?

Stefano.

[Timm]

Thanks for the quick response!
No, the error 500 occurs only when I try to open the plugin. Everything else is working just fine…

I forgot to mention the statistics log which became 0,8MB since yesterday evening and basically looks all the same and ends with:

25-05-2018 08:27:09 – INFO – m: 27,3 MB, u: 0 – Email with no token hence not signature to check
25-05-2018 08:27:14 – INFO – m: 27,3 MB, u: 0 – Email with no token hence not signature to check
25-05-2018 08:27:21 – INFO – m: 27,3 MB, u: 0 – Email with no token hence not signature to check
25-05-2018 08:27:23 – INFO – m: 27,3 MB, u: 0 – Email with no token hence not signature to check
25-05-2018 08:27:30 – INFO – m: 27,6 MB, u: 0 – Email with no token hence not signature to check
25-05-2018 08:27:37 – INFO – m: 27,3 MB, u: 0 – Email with no token hence not signature to check
25-05-2018 08:27:38 – INFO – m: 27,3 MB, u: 0 – Email with no token hence not signature to check
25-05-2018 08:27:45 – INFO – m: 27,3 MB, u: 0 – Email with no token hence not signature to check
25-05-2018 08:27:57 – INFO – m: 27,3 MB, u: 0 – Email with no token hence not signature to check
25-05-2018 08:27:38 – INFO – m: 27,3 MB, u: 0 – Email with no token hence not signature to check
25-05-2018 08:27:45 – INFO – m: 27,3 MB, u: 0 – Email with no token hence not signature to check
25-05-2018 08:27:57 – INFO – m: 27,3 MB, u: 0 – Email with no token hence not signature to check

[Timm]

I think I found the log-file. How can I send it to you directly?

[Timm]

Sorry.. I’ll better open a new support ticket than posting the details here.

[Timm]

OK, problem solved! Suddenly login works again… Strange.

[Stefano]

Hi, the info log you reported is not a problem, we should remove it.

Stefano.

[Timm]

Hey Stefano!
Could you remove it please? I can’t find the edit button any more…
Thanks
Timm

[Author]

Posts