英文:
Mesos framework stays inactive due to "Authentication failed: EOF"
问题
我目前正在尝试使用提供的示例配置，在Marathon之上部署Eremetic（版本0.28.0）。实际上，我已经成功部署过一次，但在尝试重新部署后，框架保持不活动状态。
通过检查日志，我注意到不断尝试连接到某个服务，显然由于某个身份验证问题而无法成功连接。
2017/08/14 12:30:45 连接到[REDACTED_MESOS_MASTER_ADDRESS]
2017/08/14 12:30:45 身份验证失败：EOF
看起来返回错误的服务是ZooKeeper，更准确地说，错误可以追溯到Go ZooKeeper库中的这一行。然而，ZooKeeper似乎是正常工作的：我尝试直接使用zkCli查询它，并运行了一个小的Spark作业（其中Mesos主节点使用zk:// URL提供），一切似乎都正常。
不幸的是，我无法进一步诊断问题，可能是什么原因呢？
英文:
I'm currently trying to deploy Eremetic (version 0.28.0) on top of Marathon using the configuration provided as an example. I actually have been able to deploy it once, but suddenly, after trying to redeploy it, the framework stays inactive.
By inspecting the logs I noticed a constant attempt to connect to some service that apparently never succeeds because of some authentication problem.
2017/08/14 12:30:45 Connected to [REDACTED_MESOS_MASTER_ADDRESS]
2017/08/14 12:30:45 Authentication failed: EOF
It looks like the service returning an error is ZooKeeper and more precisely it looks like the error can be traced back to this line in the Go ZooKeeper library. ZooKeeper however seems to work: I've tried to query it directly with zkCli and to run a small Spark job (where the Mesos master is given with zk:// URL) and everything seems to work.
Unfortunately I'm not able to diagnose the problem further, what could it be?
答案1
得分: 0
原来是配置问题。主节点的URL设置错误，这就是报错的原因。
英文:
It turned out to be a configuration problem. The master URL was simply wrong and this is how the error was reported.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论