Lost Formatting Problems of Digest emails

As you suggest, it looks to me from https://www.ads-software.com/support/topic/lost-formatting-problems-of-digest-emails/#post-14135204 that two batches are being sent out. This indicates that the batch system is generally working.

A few possibilities:
1. The pending items in your queue are too old to be sent. By default, BPGES will only send out items in a daily digest if they are less than three days old. In this scenario, BPGES would be working properly, but you’d still have items in the queue because they are past the “expiration” date.
2. Something at your server level is blocking the self-request from completing. Look for 40x or 50x errors in your server log. These would be requests that originate from your server’s IP and would be requesting admin-ajax.php.
3. There’s some sort of fatal error that’s causing one of the batches to die midway through. Your last log entry indicates that a third batch has begun, but that it never finishes. Your server error log may have more information about this. It would also be helpful to know whether *any* emails were sent during this third batch. You could do this by comparing against the timestamp, or by seeing whether the entire digest run sent 190 emails (95 + 95) or a higher number than that.

Dear @boonebgorges,

thanks for your answer. So to test the issue, I sent out an admin notification to one group with 196 users today and 113 mails were sent. The bpges debug log just says:

[17-Mar-2021 17:50:55] Beginning batch of immediate notifications for 7838.

The server log says the following:

[Wed Mar 17 18:51:47.205984 2021] [fcgid:warn] [pid 25803:tid 139710261266176] (32)Broken pipe: [client 141.101.69.43:41064] mod_fcgid: ap_pass_brigade failed in handle_request_ipc function
[Wed Mar 17 18:51:48.505551 2021] [fcgid:warn] [pid 25803:tid 139710303229696] (32)Broken pipe: [client 162.158.158.237:13252] mod_fcgid: ap_pass_brigade failed in handle_request_ipc function
[Wed Mar 17 18:51:53.759707 2021] [fcgid:warn] [pid 26531:tid 139710244480768] [client 141.101.96.37:36192] mod_fcgid: read data timeout in 60 seconds, referer: https://domain.org/wp-admin/admin-ajax.php?action=wp_bpges_send_queue&nonce=7babbcaf9f
[Wed Mar 17 18:51:53.759748 2021] [core:error] [pid 26531:tid 139710244480768] [client 141.101.96.37:36192] End of script output before headers: admin-ajax.php, referer: https://domain.org/wp-admin/admin-ajax.php?action=wp_bpges_send_queue&nonce=7babbcaf9f

So something is causing a core error ??

Please note: For some reason BP GES always is 1 hour off the actual time, hence the 1 hour difference between the two logs.

Kind regards, Philip

• This reply was modified 3 years, 8 months ago by Strothi.

Thanks. The third line of your log suggests that there is a timeout. There is logic in the plugin that’s intended to avoid timeouts, but it could be failing in your environment for some reason.

Here’s the method: https://github.com/boonebgorges/buddypress-group-email-subscription/blob/master/classes/class-bpges-async-request-send-queue.php#L256 It would be helpful if you were able to debug what’s going on here a bit. What is your server’s max_execution_time? I’m guessing that it’s coming back as something fairly large – say, 120 seconds – but that there’s a mismatch between this and the actual config on the server. So BPGES tries to run for too long. You might experiment by forcing $max_execution_time to ’30’, around this line https://github.com/boonebgorges/buddypress-group-email-subscription/blob/master/classes/class-bpges-async-request-send-queue.php#L263

Dear @boonebgorges,

I think that was the solution. I just sent out a test notification and while I blocked the smtp send out to not spam my members, all logs look good! I don’t have an error anymore on the server side and the BPGES log says that the correct amount of emails was successfully send out! I’ll report back on Thursday when my actual mailing goes out, but it looks like the issue is solved ??

Thank you SO MUCH!

Have a great day.

Kind regards, Philip

Fantastic! Thanks for your persistence and patience.

Dear @boonebgorges,

I forgot to report back last week, but all is fine now! ??

Have a great Easter!

Kind regards, Philip