-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
returned non-zero exit status 3 #1861
Comments
Did it use the ssh service? I also try to enable sshd service and start the service, but again see the last error. |
as I ran on, I recreate the cluster again. But still meet some errors.
It means command returned status is not correct. So I log into master node, and check the commands and services.
in fact
and these services cannot be restarted using |
Thank you @wiwengweng for this thorough bug report. The rough order of operations on the
The last of these has to support multiple versions of DC/OS. The following is a related comment in the code:
This means that it is not a problem for example that
How long did you wait to see if the services just started up? |
thanks for your response, adamtheturtle. I think I have waited for about 30mins+ before I see this error. Then I also try to manually start sshd in all nodes, and be sure they are all alive. But still see some services are "down/auto restart" state in my master container.
by this command line and here |
I am using miniDCOS to install and test dcos but without successful.
env:
ubuntu16.04
docker: Docker version 18.09.7, build 2d0083d
Python 3.6
minidcos, version 2019.06.19.0
(base) root@bogon:~/dcos-venv/bin# ./minidcos docker wait --transport docker-exec -vvv
and get the following output:
The text was updated successfully, but these errors were encountered: