Overzealous administrator actions can put Fabric8 into a non-mangeable state

There are various ways to reproduce this problem. I suggest the simplest is this. 1. Install Fuse 6.3 2. Create a fabric and an ssh container 3. Ensure the ssh container is stopped 4. Change to the ssh container's installation directory 5. Run $ ./bin/start && ./bin/start Note that multiple JVMs are instantiated. Only one will be providing any sort of service – the other will be waiting for a lock. Check this using, for example, "netstat -anp". 6. Check the process IDs in instances/instances.properties. Note that the process ID of the recently-started container may be incorrect – it may reflect the ID of the container that is waiting for a lock, not the container providing a service 7. Try to shut down the container using Fabric8 tools, or by running ./bin/shutdown. Most likely this will fail, and the state of the container will remain ambiguous. Another approach is to use the Hawtio console, and hit "start" on the container many times in quick succession. Or, if the container is running, hit "stop" many times in quick succession. Problems are harder to reproduce this way – it might take several attempts.