Digest emails not getting sent

[djensen47]

On Sunday the weekly digest was supposed to go out at 17:00. When I looked at the email settings after that time, it said Monday would be the next digest. So I just figured I misread it. Well it definitely happened today as well. I tried setting to 18 and the supposed time came along and nothing was sent. No errors, no digests, nothing.

Any thoughts?

[PitaJ]

I assume you've tried the test email and it went through fine?

[djensen47]

Yes, the test email works great.

[PitaJ]

What's your emailer setup?

[djensen47]

I'm using Sparkpost. I have a username and password entered. The time is set to 7 (which was skipped again today BTW). There really isn't much on the email settings page. It's very straightforward and a digest has been sent. Other emails are getting sent. The test email works. There seems to be something wrong with the cron but I don't know what or how to debug it.

About a 10-12 days ago the first digest went out but now it's not anymore.

[baris]

All the digest code is here https://github.com/NodeBB/NodeBB/blob/master/src/user/digest.js, can put a few console.logs to see whats going on.

[djensen47]

Is there a way to manually kick it off?

[PitaJ]

There probably should be a way, as this seems to be a common problem.

[djensen47]

Also, I noticed when chatting with one of my moderators that he was posting chats in the "future." E.g., for a little bit the time estimate would say, "a few moments from now."

Is that because his clock was ahead, my clock is behind, or, more importantly, it's a problem on the server?
And to bring it back, does that affect the cron and digest emails getting sent?

[PitaJ]

Yeah it sounds like either your clock or the server's clock is unsynchronized.

Edit: such an issue could affect it, but only if it's a big difference

[djensen47]

The other possibility that I eliminated was running NodeBB with forever vs. the nodebb command.

[djensen47]

@baris I put in some winston.info messages and nothing is getting set to the logs. I guess I'll try console.log next.

[baris]

If nothing is being printed in log/output.log then maybe the cronjob isn't running at all. Did you put one at the top of User.digest.execute ? You can also modify the interval of the cronjob so you don't have to wait all day. That code is here.

[djensen47]

@baris Yup, that's the first spot I put a winston log message.

Where do console.log messages end up? Also the logs?

[baris]

Yes if you are starting nodebb with ./nodebb start everything should go in logs/output.log if you are starting with ./nodebb dev you should see them in terminal.

If it's not printing it the next step would be to check if jobs are started at all, put a log here to see if it's printed.

[djensen47]

@baris When should that get printed?

If on startup, it didn't happen.

Okay, it printed out in the logs. (I need to make more gregarious debug messages so I see them).

[djensen47]

Probably irrelevant ... I explored the code that sets 'runJobs' ... I'm not running as a cluster. Here's my config.json

 {
     "url": "https://www.axisandallies.org/forums",
     "secret": "redacted",
     "database": "mongo",
     "port": "80",
     "trust_proxy": true,
     "mongo": {
         "host": "redacted.ip.address.here",
         "port": "27017",
         "username": "nodebb",
         "password": "redacted",
         "database": "nodebb"
     }
 }

[baris]

@djensen47 said in Digest emails not getting sent:

Okay, it printed out in the logs.

So jobs are getting started then but never triggering, try a log here https://github.com/NodeBB/NodeBB/blob/master/src/user/jobs.js#L44. If you get it cron is definitely setup.

If they are not run maybe has some time setup issue.

[djensen47]

For some reason, the digest was sent today. All I've done since last time was upgrade to 1.11.0.

[djensen47]

Actually, only a few went out and they went out at the wrong time. I have it set for 17:00 and they were sent at 9:00.