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
unhandled exception when plugin timeout happens during logging a collected file #2722
Comments
|
|
|
A race condition, certainly, but is this at all reproduce-able with timeouts longer than 1 second? Locally, for 1 second timeouts I see the same issue, but for anything longer than 1 second I am unable to reproduce this for any plugin - our normal timeout handling functions as expected. |
|
It started to occur on systems with a high number of CPUs after applying #2665 - |
|
This is more severe: when calling without verbose mode, the process segfaults after an attempt to write to closed/removed file. Reproducer: |
Wait for shutting down threads of timeouted plugins, to prevent them in writing to moved auxiliary files like sos_logs/sos.log Resolves: sosreport#2722 Closes: sosreport#2746 Signed-off-by: Pavel Moravec <pmoravec@redhat.com>
Reproducer:
The above appears many times, for
_collect_copy_specsas well as for_collect_cmdsor for"collected plugin '%s' in %s" % fieldslog.The cause is that https://github.com/sosreport/sos/blob/main/sos/report/plugins/__init__.py#L706 attempts to log verobse messages (
-vvis crucial for this reproducer) at a time when the plugin is timeouted already and the temporarysos.logfile is moved to its final destination - while (timeouted) plugin still attempts to log to the temp file.The text was updated successfully, but these errors were encountered: