Closed mamba143 closed 4 years ago
@mamba143
Which OS and type of node install is this? Was it a fresh install or an upgrade?
Do the containers stay in error mode for beyond a 15 minute system uptime?
Can you run a salt-call state.highstate
from the node that is having this issue and report any errors here?
Are there any errors in the log files for each container under the appropriate directory under /opt/so/logs?
Hi Josh,
The processes did stay in error state far beyond the 15 minute mark.. however I checked after 4 hours and they are all started and set as ok.
On Mon, Nov 2, 2020, 12:26 PM Josh Patterson notifications@github.com wrote:
@mamba143 https://github.com/mamba143
Which OS and type of node install is this? Was it a fresh install or an upgrade?
Do the containers stay in error mode for beyond a 15 minute system uptime?
Can you run a salt-call state.highstate from the node that is having this issue and report any errors here?
Are there any errors in the log files for each container under the appropriate directory under /opt/so/logs?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Security-Onion-Solutions/securityonion/issues/1770#issuecomment-720646144, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARTDXRCQIYCXAVWPNDYFHTTSN32UNANCNFSM4TG6Y72Q .
So.kratos, so-steno, so-mysql, so-cortex & so-filebeat not starting, stays in error mode