# When Jobs::UserEmail fail the email that failed is not logged
**URL:** https://meta.discourse.org/t/when-jobs-useremail-fail-the-email-that-failed-is-not-logged/31849
**Category:** Support
**Created:** [6 augustus 2015 om 23:51 UTC](https://meta.discourse.org/t/when-jobs-useremail-fail-the-email-that-failed-is-not-logged/31849 "2015-08-06T23:51:00Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@meglio](https://meta.discourse.org/u/meglio)
#### Post date: [6 augustus 2015 om 23:51 UTC](https://meta.discourse.org/t/when-jobs-useremail-fail-the-email-that-failed-is-not-logged/31849/1 "2015-08-06T23:51:00Z")
Just a fresh Discourse install and logs show a lof of this:
> Job exception: Wrapped SocketError: getaddrinfo: Name or service not known
How would I fix it?
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [7 augustus 2015 om 00:05 UTC](https://meta.discourse.org/t/when-jobs-useremail-fail-the-email-that-failed-is-not-logged/31849/2 "2015-08-07T00:05:43Z")
Need a lot more context than that, whats in env? what is the backtrace.
Is it an invalid image link causing it?
---
### Author:  [@meglio](https://meta.discourse.org/u/meglio)
#### Post date: [7 augustus 2015 om 00:14 UTC](https://meta.discourse.org/t/when-jobs-useremail-fail-the-email-that-failed-is-not-logged/31849/3 "2015-08-07T00:14:44Z")
# Note
I just noticed that all errors dated 2 days ago, which is the day when I installed Discourse. It is not happening now, so maybe error gone away. Still, might be useful?
* * *
# ENV
```plaintext
class: Jobs::UserEmail
retry: true
queue: default
jid: 2aa2098b845cef4a809e0749
enqueued_at: 1438774425.6689548
error_message: Wrapped SocketError: getaddrinfo: Name or service not known
error_class: Jobs::HandledExceptionWrapper
failed_at: 1438774425.964529
retry_count: 1
retried_at: 1438774494.9332433
current_hostname: forum.twiganything.com
hostname: forum.twiganything.com-app
process_id: 88
args:
0: [object Object]
```
# Backtrace
```plaintext
/var/www/discourse/app/jobs/base.rb:178:in `perform'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.4/lib/sidekiq/processor.rb:75:in `execute_job'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.4/lib/sidekiq/processor.rb:52:in `block (2 levels) in process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.4/lib/sidekiq/middleware/chain.rb:127:in `block in invoke'
/var/www/discourse/lib/sidekiq/pausable.rb:81:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.4/lib/sidekiq/middleware/chain.rb:129:in `block in invoke'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.4/lib/sidekiq/middleware/server/active_record.rb:6:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.4/lib/sidekiq/middleware/chain.rb:129:in `block in invoke'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.4/lib/sidekiq/middleware/server/retry_jobs.rb:74:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.4/lib/sidekiq/middleware/chain.rb:129:in `block in invoke'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.4/lib/sidekiq/middleware/server/logging.rb:15:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.4/lib/sidekiq/logging.rb:24:in `with_context'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.4/lib/sidekiq/middleware/server/logging.rb:11:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.4/lib/sidekiq/middleware/chain.rb:129:in `block in invoke'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.4/lib/sidekiq/middleware/chain.rb:132:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.4/lib/sidekiq/middleware/chain.rb:132:in `invoke'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.4/lib/sidekiq/processor.rb:51:in `block in process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.4/lib/sidekiq/processor.rb:98:in `stats'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.4/lib/sidekiq/processor.rb:50:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/celluloid-0.16.0/lib/celluloid/calls.rb:26:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/celluloid-0.16.0/lib/celluloid/calls.rb:26:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/celluloid-0.16.0/lib/celluloid/calls.rb:122:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/celluloid-0.16.0/lib/celluloid/cell.rb:60:in `block in invoke'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/celluloid-0.16.0/lib/celluloid/cell.rb:71:in `block in task'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/celluloid-0.16.0/lib/celluloid/actor.rb:357:in `block in task'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/celluloid-0.16.0/lib/celluloid/tasks.rb:57:in `block in initialize'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/celluloid-0.16.0/lib/celluloid/tasks/task_fiber.rb:15:in `block in create'
```
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [7 augustus 2015 om 00:21 UTC](https://meta.discourse.org/t/when-jobs-useremail-fail-the-email-that-failed-is-not-logged/31849/4 "2015-08-07T00:21:37Z")
Its failing to send an email to a particular user, real shame we don’t log the email in that error, I consider that a bug and will recategorize cause we want it fixed.
---
### Author:  [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)
#### Post date: [30 mei 2016 om 13:52 UTC](https://meta.discourse.org/t/when-jobs-useremail-fail-the-email-that-failed-is-not-logged/31849/5 "2016-05-30T13:52:17Z")
Where can the logged email body be found?
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [23 juli 2022 om 22:53 UTC](https://meta.discourse.org/t/when-jobs-useremail-fail-the-email-that-failed-is-not-logged/31849/6 "2022-07-23T22:53:02Z")
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [9 november 2022 om 12:22 UTC](https://meta.discourse.org/t/when-jobs-useremail-fail-the-email-that-failed-is-not-logged/31849/7 "2022-11-09T12:22:39Z")