Error: "There are 965 email jobs that failed. Check your app.yml and ensure that the mail server settings are correct."

#1

Hi there, woke up this morning to some sort of email error. My Discourse seemed to be running fine until this.

In Sidekiq, I get many errors such as this:

"16 	default 	Jobs::UserEmail 	
{"type"=>"digest", "user_id"=>8, "current_site_id"=>"default"}

Jobs::HandledExceptionWrapper: Wrapped SocketError: getaddrinfo: No address associated with hostname"

Also this one:

"5 	default 	Jobs::VersionCheck 	
{}
	
Jobs::HandledExceptionWrapper: Wrapped SocketError: Failed to open TCP connection to api.discourse.org:443 (getaddrinfo: No address associated with hostname)"

I’m not sure how to access the app.yml to check. Can’t seem to find it.

Thanks for your help!

#2

Kinda looks like your server lost DNS service at some point overnight…

When was the last job that failed? Have more recent jobs succeeded?

1 Like
#3

Thanks for the response, more recent jobs don’t seem to be working. Tried to set up a new account and received an error instead of getting a successful email. What’s strange is that I did not do any work on the site recently or change settings.

1 Like
#4

Can you log into your server via SSH? If so, try running

ping discourse.org

and see if that works.

1 Like
#5

Yes, ping seems to work fine,

#6

Hmm, if the jobs are still failing then I’m not really sure what to suggest. You could try running one manually by going to sidekiq, “scheduler”, then find “Jobs::VersionCheck” and click “Trigger”.

The app.yml file is at /var/discourse/containers/app.yml, but since the errors are with the DNS resolution I’m not sure that’ll help.

2 Likes
#7

Yes, that trigger failed as well. I have found my app.yml file and can’t see anything that stands out that would cause failure.

Again, I appreciate your help.

#8

Maybe try looking up the exact domain name that’s failing? So:

host api.discourse.org

You should get something like

api.discourse.org is an alias for corp.discourse.org.
corp.discourse.org has address 64.71.168.251
corp.discourse.org has IPv6 address 2001:470:1:3a8::251
1 Like
#9

sorry, where would I check that?

#10

SSH into the server and run

host api.discourse.org

(the same way you did ping earlier)

1 Like
#11

Ah yes, I get what you said I should get as a result

1 Like
#12

Other than trying a reboot on your server, I’m not sure I have any other suggestions - sorry. :frowning:

Hopefully someone else will have some ideas.

1 Like
[Resolved] Getting Discourse going again after Vultr server hard restart
#13

Well, I should have started with the old turn it off and on routine. That seemed to work and emails are coming through. Thanks very much for your help. Major kudos!

3 Likes
#14