# Email log errors reported

**URL:** <https://meta.discourse.org/t/email-log-errors-reported/72960>\
**Category:** Support\
**Created:** [October 28, 2017, 3:00am UTC](https://meta.discourse.org/t/email-log-errors-reported/72960 "2017-10-28T03:00:33Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Fsantiago](https://avatars.discourse-cdn.com/v4/letter/f/c5a1d2/32.png) [@Fsantiago](https://meta.discourse.org/u/Fsantiago)\
**Post date:** [October 28, 2017, 3:00am UTC](https://meta.discourse.org/t/email-log-errors-reported/72960/1 "2017-10-28T03:00:34Z")

</div>

Every now and then my admin dashboard tells me I have x number of errors in a 24 hour span. I review the logs and they typically appear as:

```
Job exception: execution expired 6 Oct 10:17 pm
Job exception: Found two rules with same prefix 'tombstone/' 8 Oct 7:57 pm
Job exception: Filter element can only be used in Lifecycle V2. 9 Oct 7:18 pm
Job exception: Filter element can only be used in Lifecycle V2. 11 Oct 6:34 pm
Job exception: Cannot assign requested address - connect(2) for "email server" port x We 8:52 am   		
Job exception: Filter element can only be used in Lifecycle V2. 3:15 pm
ActiveRecord::StatementInvalid (PG::InvalidColumnReference: ERROR: for SELECT DISTINCT, ORDER BY expressions must appear in select list LINE 1: ... NOT NULL) AND (invites.user_id IS NULL) ORDER BY CA
3:16 pm		
Job exception: execution expired

```

Is this anything I should be concerned with? I also run my own email server so I have full ability to review aspects of it as well. I also occasionally reboot it for service reasons. I assume that could explain some of it. Just wondering. Thanks.

---

<div class="post-metadata">

**Author:** ![Fsantiago](https://avatars.discourse-cdn.com/v4/letter/f/c5a1d2/32.png) [@Fsantiago](https://meta.discourse.org/u/Fsantiago)\
**Post date:** [October 28, 2017, 3:02am UTC](https://meta.discourse.org/t/email-log-errors-reported/72960/2 "2017-10-28T03:02:33Z")

</div>

I should also add I allow email topic posting and it does work fine from my experience.

---

<div class="post-metadata">

**Author:** ![Fsantiago](https://avatars.discourse-cdn.com/v4/letter/f/c5a1d2/32.png) [@Fsantiago](https://meta.discourse.org/u/Fsantiago)\
**Post date:** [October 30, 2017, 1:39am UTC](https://meta.discourse.org/t/email-log-errors-reported/72960/3 "2017-10-30T01:39:23Z")

</div>

More recent errors:

Job exception: Filter element can only be used in Lifecycle V2. 3:45 pm  
ActiveRecord::StatementInvalid (PG::InvalidColumnReference: ERROR: for SELECT DISTINCT, ORDER BY expressions must appear in

Strange; does no one else’s logs show such messages or is this normal and I’m overstressing…?

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [October 30, 2017, 4:25am UTC](https://meta.discourse.org/t/email-log-errors-reported/72960/4 "2017-10-30T04:25:14Z")

</div>

The lifecycle thing is an Amazon S3 versioning issue, and you can fix that via your amazon S3 control panel.

---

<div class="post-metadata">

**Author:** ![Fsantiago](https://avatars.discourse-cdn.com/v4/letter/f/c5a1d2/32.png) [@Fsantiago](https://meta.discourse.org/u/Fsantiago)\
**Post date:** [October 30, 2017, 2:10pm UTC](https://meta.discourse.org/t/email-log-errors-reported/72960/5 "2017-10-30T14:10:38Z")

</div>

i have two different s3 buckets that my site utilizes and they both have versioning disabled. is that why?

---

<div class="post-metadata">

**Author:** ![gerhard](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gerhard/32/119479_2.png) [@gerhard](https://meta.discourse.org/u/gerhard)\
**Post date:** [November 14, 2017, 10:47am UTC](https://meta.discourse.org/t/email-log-errors-reported/72960/6 "2017-11-14T10:47:02Z")

</div>

Sam fixed the S3 issue yesterday ([Amazon S3 job exception -- Filter element can only be used in Lifecycle V2 - #18 by sam](https://meta.discourse.org/t/amazon-s3-job-exception-filter-element-can-only-be-used-in-lifecycle-v2/71702/18)) and I just pushed a [fix for the InvalidColumnReference](https://github.com/discourse/discourse/commit/4be8f17e66d95e786edd91cdade334ff5da8ee04) error you noticed.

---

<div class="post-metadata">

**Author:** ![Fsantiago](https://avatars.discourse-cdn.com/v4/letter/f/c5a1d2/32.png) [@Fsantiago](https://meta.discourse.org/u/Fsantiago)\
**Post date:** [November 14, 2017, 12:34pm UTC](https://meta.discourse.org/t/email-log-errors-reported/72960/7 "2017-11-14T12:34:52Z")

</div>

Excellent thanks for the heads up!

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [November 16, 2017, 2:00am UTC](https://meta.discourse.org/t/email-log-errors-reported/72960/8 "2017-11-16T02:00:01Z")

</div>

This topic was automatically closed after 38 hours. New replies are no longer allowed.
