Skip to content
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

securityonion-elastic: container status scripts should check system uptime before declaring fail #1686

Closed
dougburks opened this issue Dec 24, 2019 · 2 comments
Assignees
Projects

Comments

@dougburks
Copy link
Contributor

@dougburks dougburks commented Dec 24, 2019

If a user runs so-status right after the system boots, all Elastic containers are marked FAIL. This may be misleading and may cause the user to try to manually start the containers.

Update the status scripts so that if the container is not yet running, then check the system uptime. If it has recently booted, then show container status as WARN.

@dougburks dougburks self-assigned this Dec 24, 2019
@dougburks dougburks added this to To do in 16.04.6.4 via automation Dec 24, 2019
dougburks added a commit to Security-Onion-Solutions/securityonion-elastic that referenced this issue Dec 24, 2019
…ptime before declaring fail Security-Onion-Solutions/security-onion#1686
@dougburks dougburks moved this from To do to In progress in 16.04.6.4 Dec 24, 2019
@dougburks dougburks moved this from In progress to In Testing in 16.04.6.4 Jan 4, 2020
@defensivedepth

This comment has been minimized.

Copy link
Collaborator

@defensivedepth defensivedepth commented Jan 13, 2020

Looks good!

@defensivedepth defensivedepth moved this from In Testing to Tested in 16.04.6.4 Jan 13, 2020
@dougburks

This comment has been minimized.

@dougburks dougburks closed this Feb 5, 2020
16.04.6.4 automation moved this from Tested to Done Feb 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
16.04.6.4
  
Done
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.