Hello,
The mesos server ran out of disk space and so we were doing a cleanup by removing some of the old docker containers. But now the marathon won’t start and digging deeper shows nor does zookeeper. The docker log says that it cannot load some containers.
But what we noticed was that zookeeper get started then stops. So we had at look at the zookeeper folder and the the conf was missing. This was also removed on the other master server as well which we had not touched. I presume this is to do with the link between the masters. Now the slave has this conf folder but it has the default folder and files and I noticed that this is a symlink that points to the /etc/alternatives/zookeeper-conf folder.
Is there a simple process to get the conf folder back? Is there a quick way to repair this to get it working as it used to?
Any help is appreciated as I am fairly new to this and so only have a basic understanding of how all this works.
Thanks.
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Try DigitalOcean for free
Click below to sign up and get $100 of credit to try our products over 60 days!
Hello,
If the file has been deleted and you do not have a backup of the setup or the file, then the quickest way to get things working is to re-make your configuration. If it’s just a default config, I would suggest downloading Zookeeper and then just extracting the conf file.
You can find their download page here, then find the version you have and download it. Then extract it, you could do this on your local PC even, and copy the configuration file over and modify it as you need for your setup.