If the rpm command times out during initial policy setup we will fail to start sosreport if the list of packages read before the timeout does not include the 'filesystem' package. This is because the version of this package is checked to determine the correct PATH setting (taking account of UsrMove).
This was addressed upstream via PR 942:
https://github.com/sosreport/sos/pull/942
Following this change the initial read of the RPMDB is carried out with no timeout. Users with very large databases or very busy systems may see a pause while sos starts up but policy will be correctly set and the run will complete as normal.
(In reply to Marina from comment #2)
> Is there any way to workaround it and still gather the sosreports?
Two independent options/workarounds are there:
- ensure by either way that "rpm -qa" like command finishes within 30 seconds
- or apply the patch from [1] to /usr/lib/python2.6/site-packages/sos/policies/__init__.py (officially not supported as not shipped, but shall work well)
[1] https://github.com/sosreport/sos/pull/942/files
Comment 4Miroslav Hradílek
2017-11-13 15:02:08 UTC
*** This bug has been marked as a duplicate of bug 1506596 ***