0 Replies Latest reply on May 9, 2013 3:36 PM by Chris Geer

    FUSE Server won't restart

    Chris Geer Newbie

      I have a server setup with three instances (root + two more). I had to shut it down and now I can't restart it because it says it can't connect to zookeeper (which is part of the root container). I keep getting the following error:


      19:12:16,494 | INFO  | hat-024-thread-2 | ZooKeeper                        | 53 - org.fusesource.fabric.fabric-linkedin-zookeeper - 7.2.0.redhat-024 | Initiating client connection, connectString= sessionTimeout=30000 watcher=org.linkedin.zookeeper.client.WatcherChain@1a30465

      19:12:16,689 | INFO  | d-2-SendThread() | ClientCnxn                       | 53 - org.fusesource.fabric.fabric-linkedin-zookeeper - 7.2.0.redhat-024 | Opening socket connection to server /

      19:12:16,779 | INFO  | .99.130.10:2181) | ZooKeeperSaslClient              | 53 - org.fusesource.fabric.fabric-linkedin-zookeeper - 7.2.0.redhat-024 | Client will not SASL-authenticate because the default JAAS configuration section 'Client' could not be found. If you are not using SASL, you may ignore this. On the other hand, if you expected SASL to work, please fix your JAAS configuration.

      19:12:16,791 | WARN  | .99.130.10:2181) | ClientCnxn                       | 53 - org.fusesource.fabric.fabric-linkedin-zookeeper - 7.2.0.redhat-024 | 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)[:1.6.0_24]

              at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:592)[:1.6.0_24]

              at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:286)[53:org.fusesource.fabric.fabric-linkedin-zookeeper:7.2.0.redhat-024]

              at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1035)[53:org.fusesource.fabric.fabric-linkedin-zookeeper:7.2.0.redhat-024]



      What's strange about the rest of the log is that it is starting up bundles that aren't part of the root container, but are deployed on the instances. Is there a way to validate what profiles are trying to be deployed to the container while it's stopped. I've done a lot of work building up profiles which are stored in zookeeper that I don't want to lose.


      Can I get access to the profiles if the server won't start?