SOUP 2.4.50 Power Loss #12410
Replies: 3 comments 4 replies
-
What does |
Beta Was this translation helpful? Give feedback.
3 replies
-
Depending on which version of 2.4.30 you have you can see the top.sls here https://github.com/Security-Onion-Solutions/securityonion/blob/2.4.30-20231228/salt/top.sls that is for If that was a fresh install, where did the 2.3 |
Beta Was this translation helpful? Give feedback.
1 reply
-
Appears to be a lost cause. Will create new discussion about restore. |
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.
Uh oh!
There was an error while loading. Please reload this page.
-
Well after years of SO I finally think I broke one. My distributed system is running 3 search nodes 3 senors and one manager spanning a few states in the US. I was running Soup and in the middle my work station(house) lost power. When I got back online and checked the grid everything seamed fine. I ran soup and it showed good to go. In the web dashboard all systems showed version 2.4.40 but if I typed "cat /etc/soversion" in the manager it reported 2.4.50. I rebooted the entire grid and to my surprise it never came back up. I went in and reset the socversion and /opt/so/saltstack/local/pillar/global/soc_global.sls to 2.4.40, and ran soup. It looked like it was working, downloading new images and containers. At the end errors. Then i ran so-docker-refresh only to see all failures all like " dial tcp 127.0.0.1:5000: connect: connection refused" . When executing docker ps it only shows so-elastichsearch running.
Any help would be greatly appreciated.
so-docker-refresh
soup
docker ps
Rebooted this morning. After running soup I get a message below.
When running "systemctl status salt-master"
Beta Was this translation helpful? Give feedback.
All reactions