# Not able to search after upgrade to 2.2.3-1 from 2.1.2-1

**URL:** <https://community.graylog.org/t/not-able-to-search-after-upgrade-to-2-2-3-1-from-2-1-2-1/1028>\
**Category:** Graylog Central (peer support)\
**Created:** [May 3, 2017, 3:46pm UTC](https://community.graylog.org/t/not-able-to-search-after-upgrade-to-2-2-3-1-from-2-1-2-1/1028 "2017-05-03T15:46:33Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![libincheeran](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/libincheeran/32/7648_2.png) [@libincheeran](https://community.graylog.org/u/libincheeran)\
**Post date:** [May 3, 2017, 3:46pm UTC](https://community.graylog.org/t/not-able-to-search-after-upgrade-to-2-2-3-1-from-2-1-2-1/1028/1 "2017-05-03T15:46:34Z")

</div>

I upgraded Graylogserr2 from 2.1.2-1 to 2.2.3-1 running using docker. Now I can’t see any of the saved searches and streams. I don’t see any error message in the logs. There is an error message popping up on screen with the following message **“Fetching saved searches failed with status: TypeError: Cannot read property ‘toJS’ of undefined”**

Any help is appreciated.

---

<div class="post-metadata">

**Author:** ![jochen](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jochen/32/8_2.png) [@jochen](https://community.graylog.org/u/jochen)\
**Post date:** [May 3, 2017, 5:22pm UTC](https://community.graylog.org/t/not-able-to-search-after-upgrade-to-2-2-3-1-from-2-1-2-1/1028/2 "2017-05-03T17:22:58Z")

</div>

- How exactly did you install and upgrade Graylog?
- Are you running multiple different versions of Graylog in your cluster?
- Have you tried clearing your browser cache?

---

<div class="post-metadata">

**Author:** ![libincheeran](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/libincheeran/32/7648_2.png) [@libincheeran](https://community.graylog.org/u/libincheeran)\
**Post date:** [May 3, 2017, 5:59pm UTC](https://community.graylog.org/t/not-able-to-search-after-upgrade-to-2-2-3-1-from-2-1-2-1/1028/3 "2017-05-03T17:59:40Z")

</div>

Graylog is installed using Docker.I have a docker-compose yaml file and updated the image to “graylog2/server:2.2.3-1”. Graylog server is running on single node. I had stopped and removed all the older docker process before running the docker-compose with with this new image. I have tried clearing the browser cache and it did not help.

Note : When I rollback to the pervious version of 2.1.2-1. I get these errors in the logs now .

> Unrecognized field “stream\_ids” (class org.graylog2.indexer.ranges.AutoValue\_MongoIndexRange), not marked as ignorable (3 known properties: “index\_name”, “\_id”, “took\_ms”])  
> at [Source: e.undercouch.bson4jackson.io.LittleEndianInputStream@74599b7a; pos: 126] (through reference chain: org.graylog2.indexer.ranges.AutoValue\_MongoIndexRange[“stream\_ids”])

---

<div class="post-metadata">

**Author:** ![jochen](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jochen/32/8_2.png) [@jochen](https://community.graylog.org/u/jochen)\
**Post date:** [May 4, 2017, 7:52am UTC](https://community.graylog.org/t/not-able-to-search-after-upgrade-to-2-2-3-1-from-2-1-2-1/1028/4 "2017-05-04T07:52:47Z")

</div>

> [@libincheeran](#):
>
> Graylog is installed using Docker.I have a docker-compose yaml file and updated the image to “graylog2/server:2.2.3-1”

Are you using any plugins with Graylog? Make sure that they are compatible with Graylog 2.2.x.

> [@libincheeran](#):
>
> When I rollback to the pervious version of 2.1.2-1. I get these errors in the logs now .

Downgrades from Graylog 2.2.x to an older version are not supported.

---

<div class="post-metadata">

**Author:** ![libincheeran](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/libincheeran/32/7648_2.png) [@libincheeran](https://community.graylog.org/u/libincheeran)\
**Post date:** [May 4, 2017, 2:44pm UTC](https://community.graylog.org/t/not-able-to-search-after-upgrade-to-2-2-3-1-from-2-1-2-1/1028/5 "2017-05-04T14:44:38Z")

</div>

Thank you! the plugins we causing the problem. I uninstalled the plugins and everything works just fine. Appreciate your prompt response and help 🙂
