Fix the issue of full cpus/ram when handling corrupted org #2886
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
scudette
pushed a commit
to scudette/velociraptor
that referenced
this pull request
Aug 28, 2023
…#2886) When the disk was full, some strange things happened. Some files are created but the files are empty. In my case, my disk was full, so an organization's .json.db file was created with zero length content, causing a loop of the startOrg call. This commit will fix that problem by checking if the organization's .json.db file is corrupted.
scudette
pushed a commit
that referenced
this pull request
Aug 28, 2023
When the disk was full, some strange things happened. Some files are created but the files are empty. In my case, my disk was full, so an organization's .json.db file was created with zero length content, causing a loop of the startOrg call. This commit will fix that problem by checking if the organization's .json.db file is corrupted.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When the disk was full, some strange things happened.
Some files are created but the files are empty.
In my case, my disk was full, so an organization's .json.db file was created with zero length content, causing a loop of the startOrg call.
This commit will fix that problem by checking if the organization's .json.db file is corrupted.