# Allocators lost connection to ZooKeeper **URL:** \ **Category:** Elastic Cloud Enterprise (ECE)\ **Created:** [November 21, 2017, 9:11am UTC](https://discuss.elastic.co/t/allocators-lost-connection-to-zookeeper/108535 "2017-11-21T09:11:13Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Lafunamor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lafunamor/32/22571_2.png) [@Lafunamor](https://discuss.elastic.co/u/Lafunamor)\ **Post date:** [November 21, 2017, 9:11am UTC](https://discuss.elastic.co/t/allocators-lost-connection-to-zookeeper/108535/1 "2017-11-21T09:11:13Z")
Hi Guys After increasing the RAM of all allocator nodes (this caused a sequential restart) they are no longer able to connect to ZooKeeper. Here are a couple of logs I found: services-forwarder.log ```auto [2017-11-21 09:02:20,780][INFO][org.apache.zookeeper.ClientCnxn] Opening socket connection to server 0.0.0.0/0.0.0.0:2181. Will not attempt to authenticate using SASL (unknown error) {} [2017-11-21 09:02:20,780][WARN][org.apache.zookeeper.ClientCnxn] Session 0x0 for server null, unexpected error, closing socket connection and attempting reconnect {} java.net.ConnectException: Connection refused at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717) at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357) at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214) ``` allocator.log: [https://gist.github.com/Lafunamor/ed8db7e384a442ecc2cb233c2c1405bb](https://gist.github.com/Lafunamor/ed8db7e384a442ecc2cb233c2c1405bb) I don't know if it's important but this cluster was upgraded from 1.0.2 to 1.1.0. Do you guys have any idea how I can recover from this state? ---
**Author:** ![Yuri](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yuri/32/52458_2.png) [@Yuri](https://discuss.elastic.co/u/Yuri)\ **Post date:** [November 21, 2017, 1:46pm UTC](https://discuss.elastic.co/t/allocators-lost-connection-to-zookeeper/108535/2 "2017-11-21T13:46:00Z")
Hi, Can you please check if container `frc-client-forwarders-client-forwarder` is running and if there are any errors? Also, I would be great if you can send logs from that host. ---
**Author:** ![Lafunamor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lafunamor/32/22571_2.png) [@Lafunamor](https://discuss.elastic.co/u/Lafunamor)\ **Post date:** [November 21, 2017, 2:28pm UTC](https://discuss.elastic.co/t/allocators-lost-connection-to-zookeeper/108535/3 "2017-11-21T14:28:24Z")
Hi @Yuri Thank you for your answer. The client forwarder is up and running on the allocator and here is the client-forwarder log from the allocator node: [https://gist.github.com/Lafunamor/0ab7d0835c53b2d1a2ee93c11cc80891](https://gist.github.com/Lafunamor/0ab7d0835c53b2d1a2ee93c11cc80891) Additionally here is the log from the client forwarder on a director node (container is also up and running): [https://gist.github.com/Lafunamor/7e184a6528db3beb10bf658887cf6f78](https://gist.github.com/Lafunamor/7e184a6528db3beb10bf658887cf6f78) Let me know if you need any further information or log file. ---
**Author:** ![Yuri](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yuri/32/52458_2.png) [@Yuri](https://discuss.elastic.co/u/Yuri)\ **Post date:** [November 21, 2017, 2:52pm UTC](https://discuss.elastic.co/t/allocators-lost-connection-to-zookeeper/108535/4 "2017-11-21T14:52:54Z")
Can you please do the following [https://www.elastic.co/guide/en/cloud-enterprise/current/ece-getting-help.html](https://www.elastic.co/guide/en/cloud-enterprise/current/ece-getting-help.html) and send the archive to me via direct message? ---
**Author:** ![Yuri](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yuri/32/52458_2.png) [@Yuri](https://discuss.elastic.co/u/Yuri)\ **Post date:** [November 21, 2017, 3:06pm UTC](https://discuss.elastic.co/t/allocators-lost-connection-to-zookeeper/108535/5 "2017-11-21T15:06:25Z")
Ah... sorry I probably misunderstood your problem! Please follow my comment here [Maintenance Mode enabled after upgrade](https://discuss.elastic.co/t/maintenance-mode-enabled-after-upgrade/108125/4?u=yuri) ---
**Author:** ![Lafunamor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lafunamor/32/22571_2.png) [@Lafunamor](https://discuss.elastic.co/u/Lafunamor)\ **Post date:** [November 21, 2017, 3:23pm UTC](https://discuss.elastic.co/t/allocators-lost-connection-to-zookeeper/108535/6 "2017-11-21T15:23:18Z")
Hey @Yuri I already tried the solution you posted there. It did not help. I'm sending you the archive now as a PM. ---
**Author:** ![Lafunamor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lafunamor/32/22571_2.png) [@Lafunamor](https://discuss.elastic.co/u/Lafunamor)\ **Post date:** [November 23, 2017, 8:07am UTC](https://discuss.elastic.co/t/allocators-lost-connection-to-zookeeper/108535/7 "2017-11-23T08:07:48Z")
I was able to resolve the problem thanks to a lot of help of @Yuri. Thank you very much. The issue was that my automation tried to perform the version upgrade multiple times and during a rollback of such an update some configuration got deleted. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 7, 2017, 8:07am UTC](https://discuss.elastic.co/t/allocators-lost-connection-to-zookeeper/108535/8 "2017-12-07T08:07:50Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.