Hi,

I have a site that's been working great with Subscriptions; it's been sending notification emails to users for months.

It stopped sending anything about 10 days ago, and I have no idea why.

To my knowledge, no changes were made to the site around that time. I've confirmed with the site host that they didn't make any changes on the server that could have caused this.

A test version of the site running on the same server DOES send notifications.

Other types of emails (password resets and so on) are being sent with no problem.

I have confirmed that I am still subscribed to the several forum categories, and that there's new content for which notifications should be going out.

The Mail Log module shows dozens of subscriptions_mail_node-type-forum emails every day through Sept 3, when they stopped.

The Drupal logs show plenty of Subscriptions updates, right up until the time they stopped getting sent; the last one reads

Subscriptions sent 0 single and 2 digest notifications in 1 of 240 seconds. 0 queue items remaining (plus 17917 suspended), 238 seconds left for other cron client modules.

Cron is continuing to run, but no notifications are going out.

There are lots of messages in the queue:

There are 10431 active and 18398 suspended items in the queue.  

I'm thinking of trying the latest dev version of Subscriptions, but considering that this WAS working for us before, that may not be the best solution.

I've tried temporarily updating the settings at

https://www.example.com/admin/config/system/subscriptions

- I set "limit the number of outgoing emails" to 20 (it's usually 0) and "limit the percentage of cron job time" to 60 (it's usually 50) to see if that would nudge things back into action, but it didn't help. I set them back to 0 and 50.

Do you have any suggestions of things I could try or look at to get notifications to start going out again?

Thanks very much!

Kristi

Comments

Kristi Wachter created an issue. See original summary.

salvis’s picture

Is cron running? Run cron manually from the Status page and check the watchdog log.

Then check the Apache log for possible error messages.

You mention a "test version" — is that test version installed under the production version? Temporarily remove/move it out from under the Drupal directory of the production site. Having duplicate source files/directories (even when renamed to *.bak or whatever) causes problems for Drupal.

kristi wachter’s picture

Hi,

Thank you so much for the quick reply!

I HAVE run cron - cron has been running pretty regularly during the past week (usually finishing normally, but occasionally throwing "tried to run cron while still running" errors in the Drupal log). I also tried running it a few times from the Status Report page; it finished normally, but no subscription notifications were sent (and no subscription entries showed up in the Drupal log, the way they have when the subscription notifications DID go out).

The test site is not under the main Drupal directory; it's more like
/home/kristi/public_html - main site
/home/kristi/test - test site

I will try to check the Apache logs and update this ticket again. If you think of anything else for me to check in the meantime, please let me know.

Thank you very much!

Kristi

salvis’s picture

Status: Active » Postponed (maintainer needs more info)

Did you find anything in the logs? Note that there is typically a separate error log file.

salvis’s picture

Status: Postponed (maintainer needs more info) » Closed (outdated)