-
Notifications
You must be signed in to change notification settings - Fork 94
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
Node does not start automatically after reboot. #36
Comments
Thanks for filing an issue on this. DispositionEnabling the ECS system to boot back up after a system reboot should be included in the install script. This enhancement is marked for inclusion in the 2.1 release due out sometime next quarter. Work-Around
*** For reference, here's an excerpt of
|
What is the container ID (where do I find it)? It does not seem to be a parameter specified during installation/configuration. |
Please issue |
docker psFATA[0000] Get http:///var/run/docker.sock/v1.16/containers/json: dial unix /var/run/docker.sock: no such file or directory. Are you trying to connect to a TLS-enabled daemon without TLS? |
After |
Please remember to use |
I am logged in as root :-) Status so far 5 minutes after reboot and startup:
5 minutes later, the system is up and running |
Depends on issue #66. Also need to install systemd scripts to ensure docker is auto-started and the docker image is auto-started after docker. |
Hello, I've followed the single node software only install process for ECS 2.2 plus the workarounds listed above but I can't log into the webUI after a reboot. Any tips in how to get this working? I log in as root with the correct password and the page hangs with a spinning "login" animation. Have CentOS 7 running in a VM. |
Resolved the above issue in discussion elsewhere. When editing /etc/fstab, use the following settings rather than the default:
|
Please see pull request #108 |
/etc/rc.local is a symlink to /etc/rc.d/rc.local so chmod +x /etc/rc.d/rc.local should work ! |
This is working in installer 2.0.0; unfortunately release has been delayed. |
For other reasons, I had to reboot my test server with the single node installation.
After reboot, the single-node ECS installation does not start the services.
What should be done in order to start everything up again - in order to avoid having to start an installation from scratch?
The text was updated successfully, but these errors were encountered: