# User admin panel broken due to timestamp out of range

**URL:** https://meta.discourse.org/t/user-admin-panel-broken-due-to-timestamp-out-of-range/30967
**Category:** Support
**Created:** [2015 年 7 月 11 日午前 3:44 UTC](https://meta.discourse.org/t/user-admin-panel-broken-due-to-timestamp-out-of-range/30967 "2015-07-11T03:44:15Z")
**Posts on this page:** 10
**Page:** 1

<div class="post-metadata">

### Author: ![bweissman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bweissman/32/116408_2.png) [@bweissman](https://meta.discourse.org/u/bweissman)
#### Post date: [2015 年 7 月 11 日午前 3:44 UTC](https://meta.discourse.org/t/user-admin-panel-broken-due-to-timestamp-out-of-range/30967/1 "2015-07-11T03:44:15Z")

</div>

I went to edit a user today and I was presented with the following error:

☹  
Error  
while trying to load  
Something went wrong.  
Go Back Try Again

I am unsure what the problem is, and did not make any major changes to discourse itself. New users work fine, just existing users.

Any help would be appreciated.

---

<div class="post-metadata">

### Author: ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)
#### Post date: [2015 年 7 月 11 日午前 4:13 UTC](https://meta.discourse.org/t/user-admin-panel-broken-due-to-timestamp-out-of-range/30967/2 "2015-07-11T04:13:10Z")

</div>

Can you do it again with the browser’s developer tools network tab open and tell us what the erroring request(s) are?

---

<div class="post-metadata">

### Author: ![bweissman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bweissman/32/116408_2.png) [@bweissman](https://meta.discourse.org/u/bweissman)
#### Post date: [2015 年 7 月 11 日午前 4:30 UTC](https://meta.discourse.org/t/user-admin-panel-broken-due-to-timestamp-out-of-range/30967/3 "2015-07-11T04:30:30Z")

</div>

GET [http://example.com/admin/users/bryan.json?\_=1436587808570](http://example.com/admin/users/bryan.json?_=1436587808570)

```plaintext
500 (Internal Server Error)Y.cors.e.crossDomain.send @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:2280J.extend.ajax @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:1874n @ _application-fa2de301309586b795c15c1b1f12731d.js:103_ @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:22270h @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:23328Discourse.Ajax.Em.Mixin.create.ajax @ _application-fa2de301309586b795c15c1b1f12731d.js:117r.reopenClass.find @ _admin-ba1f14c90da9460534ded85b6a9913c4.js:4889Discourse.User.extend.loadDetails @ _admin-ba1f14c90da9460534ded85b6a9913c4.js:4824e.default.Discourse.Route.extend.afterModel @ _admin-ba1f14c90da9460534ded85b6a9913c4.js:7053r @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:3365d @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:21743n.runSharedModelHook @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:19007n.runAfterModelHook @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:19007(anonymous function) @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:21270b @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:22255y @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:22040g @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:22194(anonymous function) @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:6693r.invoke @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:3364r.flush @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:3364n.flush @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:3364s.end @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:3364s.run @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:3364s.join @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:3364l.join @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:3365e.default.l.default.extend._bubbleEvent @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:13406(anonymous function) @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:13360J.event.dispatch @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:1874g.handle @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:1874

[object Object]Discourse.Route.extend.actions.error @ _application-fa2de301309586b795c15c1b1f12731d.js:79527C @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:4797l @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:21369i.trigger @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:20841(anonymous function) @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:20587b @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:22255y @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:22040g @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:22194p @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:22087(anonymous function) @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:6693r.invoke @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:3364r.flush @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:3364n.flush @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:3364s.end @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:3364s.run @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:3364l @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:3365a.error @ _application-fa2de301309586b795c15c1b1f12731d.js:83c @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:1874h.fireWith @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:1874r @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:1874(anonymous function) @ _vendor-68a043ffb30ca8b0ef68bf301d9c2efb.js:2267

```

---

<div class="post-metadata">

### Author: ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)
#### Post date: [2015 年 7 月 11 日午前 5:19 UTC](https://meta.discourse.org/t/user-admin-panel-broken-due-to-timestamp-out-of-range/30967/4 "2015-07-11T05:19:49Z")

</div>

Okay, so it’s a 500. What shows up in `/logs` ?

---

<div class="post-metadata">

### Author: ![bweissman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bweissman/32/116408_2.png) [@bweissman](https://meta.discourse.org/u/bweissman)
#### Post date: [2015 年 7 月 11 日午前 5:25 UTC](https://meta.discourse.org/t/user-admin-panel-broken-due-to-timestamp-out-of-range/30967/5 "2015-07-11T05:25:05Z")

</div>

It seems that /logs doesn’t load. It is just sitting at a white page.

---

<div class="post-metadata">

### Author: ![bweissman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bweissman/32/116408_2.png) [@bweissman](https://meta.discourse.org/u/bweissman)
#### Post date: [2015 年 7 月 11 日午後 9:35 UTC](https://meta.discourse.org/t/user-admin-panel-broken-due-to-timestamp-out-of-range/30967/6 "2015-07-11T21:35:43Z")

</div>

I still have no idea what is wrong. I rebuilt the app and restarted the server with no success.

---

<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: [2015 年 7 月 11 日午後 9:36 UTC](https://meta.discourse.org/t/user-admin-panel-broken-due-to-timestamp-out-of-range/30967/7 "2015-07-11T21:36:33Z")

</div>

There is another report of this so something might be up [User admin panel fails to load after making a change - #4 by codinghorror](https://meta.discourse.org/t/user-admin-panel-fails-to-load-after-making-a-change/30986/4)

---

<div class="post-metadata">

### Author: ![bweissman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bweissman/32/116408_2.png) [@bweissman](https://meta.discourse.org/u/bweissman)
#### Post date: [2015 年 7 月 11 日午後 10:02 UTC](https://meta.discourse.org/t/user-admin-panel-broken-due-to-timestamp-out-of-range/30967/8 "2015-07-11T22:02:06Z")

</div>

I got the logs working. This is what happens every time it tries to load a user admin page.  
(!)  
PG::DatetimeFieldOverflow: ERROR: timestamp out of range: “2735892-07-09 17:17:08.646893 BC”  
LINE 1: …“user\_histories”.“action” = 15 AND (created\_at \>= '2735892-0…  
^  
: SELECT 1 AS one FROM “user\_histories” WHERE “user\_histories”.“target\_user\_id” = 1 AND “user\_histories”.“action” = 15 AND (created\_at \>= ‘2735892-07-09 17:17:08.646893 BC’) AND “user\_histories”.“previous\_value” = ‘2’ AND “user\_histories”.“new\_value” = ‘3’ LIMIT 1  
  
  
(!!)  
ActiveRecord::StatementInvalid (PG::DatetimeFieldOverflow: ERROR: timestamp out of range: “2735892-07-09 17:17:08.646893 BC”  
LINE 1: …“user\_histories”.“action” = 15 AND (created\_at \>= '2735892-0…  
^  
: SELECT 1 AS one FROM “user\_histories” WHERE “user\_histories”.“target\_user\_id” = 1 AND “user\_histories”.“action” = 15 AND (created\_at \>= ‘2735892-07-09 17:17:08.646893 BC’) AND “user\_histories”.“previous\_value” = ‘2’ AND “user\_histories”.“new\_value” = ‘3’ LIMIT 1)

---

<div class="post-metadata">

### Author: ![bweissman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bweissman/32/116408_2.png) [@bweissman](https://meta.discourse.org/u/bweissman)
#### Post date: [2015 年 7 月 12 日午前 12:04 UTC](https://meta.discourse.org/t/user-admin-panel-broken-due-to-timestamp-out-of-range/30967/9 "2015-07-12T00:04:01Z")

</div>

I found this thread and it fixed it. Thanks for your help guys.

> [@Error While Trying to load, New and Admin accounts](https://meta.discourse.org/t/error-while-trying-to-load-new-and-admin-accounts/29050):
>
> So whenever I try and access a users account from the ‘Users’ Tab on the admin panel I get this error. Error When trying to load, go back or retry It only happens on non ‘Normal User’ Accounts. aka, Admin Accounts, Mod accounts and new accounts. Though it should show there profile, there badges and allow me to change other settings. Any suggestions could be helpful ^.^ I tried upgrading my RAM I have 16 GB now instead of 1 and it still happens. @codinghorror Just saw that you frequent here …

---

<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: [2015 年 7 月 12 日午前 12:33 UTC](https://meta.discourse.org/t/user-admin-panel-broken-due-to-timestamp-out-of-range/30967/10 "2015-07-12T00:33:18Z")

</div>


