# Graylog search Stuck at 23:23 (can't search past 23:23)
**URL:** https://community.graylog.org/t/graylog-search-stuck-at-23-23-cant-search-past-23-23/2500
**Category:** Graylog Central (peer support)
**Created:** [September 19, 2017, 8:31am UTC](https://community.graylog.org/t/graylog-search-stuck-at-23-23-cant-search-past-23-23/2500 "2017-09-19T08:31:11Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Shane](https://community.graylog.org/u/Shane)
#### Post date: [September 19, 2017, 8:31am UTC](https://community.graylog.org/t/graylog-search-stuck-at-23-23-cant-search-past-23-23/2500/1 "2017-09-19T08:31:11Z")
Recently updated to the newest Graylog version 2.3.1, running ES 5.6 and I can not longer search past 23:23 CST. I can see the indices are growing, there aren’t any errors in elasticsearch logs (cluster is green), nothing in graylog, nothing in the journal, and I can event see the logs being processed and can manually perform a query and see that graylog is shipping the logs into the indices. For whatever reason though, the last log I am able to see is at 23:23. I’ve seen it before where it was a time zone issue, but if I go back 8 hours, and turn on live updates, i’m not even getting new messages popping in. The side bar where it states how many total messages were found in the past 8 hours is growing, but no new messages pop up into the messages feed. I’m assuming it has something to do with having to manually clear out the sessions from my MongoDB because I was getting the timeout error that doesn’t appear to have a solution to, referenced here [https://github.com/Graylog2/graylog2-server/issues/2559](https://github.com/Graylog2/graylog2-server/issues/2559).
Is there a point of reference/file that is telling graylog that message x is the last available message to search for or something?
---
### Author:  [@Shane](https://community.graylog.org/u/Shane)
#### Post date: [September 19, 2017, 3:32pm UTC](https://community.graylog.org/t/graylog-search-stuck-at-23-23-cant-search-past-23-23/2500/2 "2017-09-19T15:32:33Z")
It appears I was able to fix the issue. To help others I’ll identify what I did to fix this:
What happened:
For some reason, Graylog was not including the “gralog\_deflector” index. (Graylog\_deflector index is the default name of the current index that is being written too.)
This was verified by connecting to my mongoDB, and running:
use graylog
db.index\_ranges.find()
I believe there should be an entry in there with your latest index. You can check your current index name on the web app under System\>indices\>“Default Index” and the index name should be the current “active write index”. Whatever the name of that index is, there should be an entry located in the db.index\_ranges.find() output from your mongodb. If there is not an entry, go to the web app\>indices\>“Default Index set” and in the top right there is a blue button called maintenance.
Select that button and choose the recalculate index ranges button, and that should re-add that index into your db.index\_range.find() output. Your alerts should start appearing again.
---
### Author:  [@dbernaci](https://community.graylog.org/u/dbernaci)
#### Post date: [September 19, 2017, 3:55pm UTC](https://community.graylog.org/t/graylog-search-stuck-at-23-23-cant-search-past-23-23/2500/3 "2017-09-19T15:55:43Z")
I have the same issue with graylog 2.3.1 + elasticsearch 5.6, and this solves also for my installation.
Thanx
---
### Author:  [@system](https://community.graylog.org/u/system)
#### Post date: [October 3, 2017, 3:55pm UTC](https://community.graylog.org/t/graylog-search-stuck-at-23-23-cant-search-past-23-23/2500/4 "2017-10-03T15:55:47Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.