Replies: 2 comments
-
I would suggest upgrading before doing anything else, then see if you still experience the same or a similar issue. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hi again all Thanks @weslambert - I have now upgraded to v2.3.60 and we still see the same problem. I have been able to get a full clean-sheet of "OK" now by doing more than one sudo docker restart $(sudo docker ps -a -q)and salt-call state.highstateBut it seems like it should do this itself after a reboot? Is there anything else that anyone can suggest that I could try in order to get this stable after a reboot without interference? Thanks |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi there
Please can someone help?
When rebooting a single node SO instance, the majority of services don't automatically start, and are shown as STARTING by an so-status command.
After a
$ sudo docker restart $(sudo docker ps -a -q)
We are left with 3 not started (2 in ERROR and 1 in PENDING):
Checking Docker status
Checking container statuses
and the following messages in /opt/so/log/salt/minion:
I have tried a docker refresh, but this did not seem to help.
Restarting these manually one by one does not seem to help either, and a salt-call state.highstate returns:
local:
Data failed to compile:
Any help would be most appreciated.
Ideally we would want all these services to start automatically on boot without any interference - can this be done?
Is there a setting I am missing?
This is on v2.3.51, will an upgrade fix this?
Thanks,
Helen
Beta Was this translation helpful? Give feedback.
All reactions