-
Version2.4.90 Installation MethodSecurity Onion ISO image Descriptionother (please provide detail below) Installation TypeDistributed Locationon-prem with Internet access Hardware SpecsExceeds minimum requirements CPU28 RAM395567560 Storage for /293G Storage for /nsm1.2T Network Traffic Collectionspan port Network Traffic Speeds1Gbps to 10Gbps StatusNo, one or more services are failed (please provide detail below) Salt StatusNo, there are no failures LogsNo, there are no additional clues DetailWe have a Manager node and a Forward node.
"sudo salt-call state.highstate" appears to check out okay. it ends with:
When I start the so-soc container, it seems to start without any errors:
but the docker logs show this:
Where is it grabbing 'ServerConfig.server.proxy' from? Guidelines
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 5 replies
-
I haven't found the solution yet, but I did upgrade. |
Beta Was this translation helpful? Give feedback.
-
Is the 404 response from Kratos an indication of a problem even though the status of so-kratos is 'running'
|
Beta Was this translation helpful? Give feedback.
-
Can you run
|
Beta Was this translation helpful? Give feedback.
Can you manually edit the file
/opt/so/saltstack/local/pillar/manager/soc_manager.sls
The file should look like
Then run
sudo so-restart soc
Did you manually edit this file before or did you make your changes via the SOC UI?