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

last_run_times causes process to hang #28

Closed
phokur opened this issue Jun 2, 2022 · 2 comments
Closed

last_run_times causes process to hang #28

phokur opened this issue Jun 2, 2022 · 2 comments

Comments

@phokur
Copy link

phokur commented Jun 2, 2022

Running on debain

Whenever last_run_times exists in the directory the command runs from, the program will hang at reading the logs.

Ctrl-C gives the following:

Traceback (most recent call last):
File "AuditLogCollector.py", line 93, in receive_results_from_rust_engine
ValueError: No logs ready

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "AuditLogCollector.py", line 692, in
File "AuditLogCollector.py", line 60, in run
File "AuditLogCollector.py", line 73, in run_once
File "AuditLogCollector.py", line 95, in receive_results_from_rust_engine
File "AuditLogCollector.py", line 54, in force_stop
File "logging/init.py", line 2082, in info
File "logging/init.py", line 1446, in info
File "logging/init.py", line 1565, in _log
File "AuditLogCollector.py", line 55, in force_stop
File "threading.py", line 1006, in join
RuntimeError: cannot join thread before it is started
[26644] Failed to execute script 'AuditLogCollector' due to unhandled exception!

@ddbnl
Copy link
Owner

ddbnl commented Jun 3, 2022

Could you post your config file so I can try to reproduce this? I'll get back to you asap.

In the meantime you could try running without 'resume' but with 'skipKnownContent' as a workaround; that way you wouldn't run into the crash but also avoid duplicates.

ddbnl added a commit that referenced this issue Jun 12, 2022
#28 #29.  + Bug fix to clean_known_content
@ddbnl
Copy link
Owner

ddbnl commented Jun 12, 2022

I have not heard back so I will close this issue. If you need further assistance let me know. As I've mentioned, setting 'resume' to false in the config and 'skipKnownLogs' to true should fix the issue.

I've released a new version in which 'resume' is deprecated and produces a warning in the log file, so people can avoid this issue in the future.

@ddbnl ddbnl closed this as completed Jun 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants