# Graylog isn't working after upgrade **URL:** \ **Category:** Graylog Central (peer support)\ **Created:** [August 17, 2017, 8:39pm UTC](https://community.graylog.org/t/graylog-isnt-working-after-upgrade/2135 "2017-08-17T20:39:01Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![crisleylinhares](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/crisleylinhares/32/717_2.png) [@crisleylinhares](https://community.graylog.org/u/crisleylinhares)\ **Post date:** [August 17, 2017, 8:39pm UTC](https://community.graylog.org/t/graylog-isnt-working-after-upgrade/2135/1 "2017-08-17T20:39:01Z")
Today we updated our version of Graylog to 2.3. However, she stopped receiving messages. When I try to perform a search, the following message is displayed: "Error Message: Unable to perform search query. Details: Search status code: 500 Search response: Can not GET [http://200.129.163.12:12900/search/universal/relative?query=\*&range=300&limit=150&sort=timestamp%3Adesc](http://200.129.163.12:12900/search/universal/relative?query=%2A&range=300&limit=150&sort=timestamp%3Adesc) (500) According to the graylog-server log, the message: “ERROR [Cluster] could not read cluster health for indices [graylog\_ \*] (could not connect to [http://127.0.0.1:9200](http://127.0.0.1:9200))” Followed by several errors. I noticed that it tries to connect to the elasticsearch cluster through localhost, however the cluster is available on another server and through our tests it is available. The graylog-server and elasticsearch configuration files are apparently normal. I would like help solving this problem since Graylog stopped working at our institution. ---
**Author:** ![joaociocca](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/joaociocca/32/401_2.png) [@joaociocca](https://community.graylog.org/u/joaociocca)\ **Post date:** [August 17, 2017, 10:19pm UTC](https://community.graylog.org/t/graylog-isnt-working-after-upgrade/2135/2 "2017-08-17T22:19:35Z")
I’m struggling with the same problem, it seems… sorry I couldn’t help =( ---
**Author:** ![crisleylinhares](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/crisleylinhares/32/717_2.png) [@crisleylinhares](https://community.graylog.org/u/crisleylinhares)\ **Post date:** [August 18, 2017, 7:39pm UTC](https://community.graylog.org/t/graylog-isnt-working-after-upgrade/2135/3 "2017-08-18T19:39:20Z")
Somebody with the same problem that could help me, please? ☹ ---
**Author:** ![joaociocca](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/joaociocca/32/401_2.png) [@joaociocca](https://community.graylog.org/u/joaociocca)\ **Post date:** [August 18, 2017, 8:14pm UTC](https://community.graylog.org/t/graylog-isnt-working-after-upgrade/2135/4 "2017-08-18T20:14:02Z")
so, my initial problem was server.conf using elasticsearch native port instead of http port. You checked that? Take a look at the details I’ve posted and see if anything resonates… > [@Tried upgrading 2.2.3 to 2.3 - ES won't connect, es\_hosts ok](https://community.graylog.org/t/tried-upgrading-2-2-3-to-2-3-es-wont-connect-es-hosts-ok/2137/): > > Searched around the forum and the web, and found nothing. For some reason I can’t find, Graylog just won’t connect to all green ES servers. Scenario: 3 graylog+mongo servers (10.0.2.131-133), 5 ES servers (.134-138) 131 = master elasticsearch\_hosts = http://10.0.2.134:9301,http://10.0.2.135:9301,http://10.0.2.136:9301,http://10.0.2.137:9301,http://10.0.2.138:9301 log goes like this… 2017-08-17T18:44:34.748-03:00 INFO [CmdLineTool] Loaded plugin: Elastic Beats Input 2.3.0 [org.graylog.plug… ---
**Author:** ![Jort](https://avatars.discourse-cdn.com/v4/letter/j/c37758/32.png) [@Jort](https://community.graylog.org/u/Jort)\ **Post date:** [August 28, 2017, 6:32pm UTC](https://community.graylog.org/t/graylog-isnt-working-after-upgrade/2135/5 "2017-08-28T18:32:44Z")
Unfortunately I’ve been hitting the same problem, on my dockerized instance. When running the v2.2.3-1, all is good. When upgrading to v2.3.1-1, the container does not get past the mentioned logged error: “ERROR [Cluster] could not read cluster health for indices [graylog\_ \*] (could not connect to [http://127.0.0.1:9200](http://127.0.0.1:9200))” Not sure how to proceed either…(sticking to v2.2 for now). ---
**Author:** ![nimolvanpersien](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/nimolvanpersien/32/324_2.png) [@nimolvanpersien](https://community.graylog.org/u/nimolvanpersien)\ **Post date:** [August 29, 2017, 6:43am UTC](https://community.graylog.org/t/graylog-isnt-working-after-upgrade/2135/6 "2017-08-29T06:43:32Z")
What’s the content of /etc/graylog/graylog-services.json inside the your machine? if like this { “etcd”: { “enabled”: true }, “nginx”: { “enabled”: true }, “mongodb”: { “enabled”: true }, “elasticsearch”: { “enabled”: true }, “graylog\_server”: { “enabled”: true } } then is fine just input _sudo graylog-ctl enable-all-services_ ---
**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:** [August 29, 2017, 6:57am UTC](https://community.graylog.org/t/graylog-isnt-working-after-upgrade/2135/7 "2017-08-29T06:57:35Z")
Please read the upgrade notes for Graylog 2.3.x: [http://docs.graylog.org/en/2.3/pages/upgrade/graylog-2.3.html#graylog-switches-to-elasticsearch-http-client](http://docs.graylog.org/en/2.3/pages/upgrade/graylog-2.3.html#graylog-switches-to-elasticsearch-http-client) ---
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\ **Post date:** [September 12, 2017, 6:57am UTC](https://community.graylog.org/t/graylog-isnt-working-after-upgrade/2135/8 "2017-09-12T06:57:38Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.