Files
securityonion/salt
Mike Reeves 6bca92da4a fix: stop pip's patchelf 'ERROR' line from polluting sosetup.log
The cmd.run for psycopg2 install was already tolerating pip's
non-zero exit with `|| true`, but pip's stderr — which contains the
literal string "ERROR: Could not install packages due to an OSError:
[Errno 2] No such file or directory: 'patchelf'" — was still being
captured into salt's state-result dict. so-setup logs salt state
output to /root/sosetup.log, and verify_setup() then greps for the
substring "ERROR" to build /root/errors.log. The patchelf line then
shows up at the end of every install as "WARNING: Errors detected
during setup" even though the install is in fact green.

Redirect pip's combined stdout/stderr to
/opt/so/log/so_pillar/psycopg2_install.log so the noise lives in a
dedicated, predictable triage location instead of leaking into salt's
state result. The `unless: import psycopg2` check is still the
actual readiness gate, so a real install failure (rather than just
the patchelf RPATH-rewrite step that has no functional effect on the
wheel) would still surface via the state being re-run on every apply
and `import psycopg2` failing.
2026-05-05 10:38:57 -04:00
..
2025-05-30 12:50:59 -04:00
2025-12-02 11:16:08 -06:00
2025-12-11 17:30:06 -05:00
2026-04-24 09:24:58 -05:00
2025-12-02 11:16:08 -06:00
2026-03-23 16:26:56 -04:00
2026-04-09 10:18:36 -04:00
2026-04-24 13:56:35 -04:00
2025-10-30 11:02:36 -04:00
2026-03-06 15:45:36 -05:00
2026-03-19 14:39:10 -04:00
2026-03-19 14:41:49 -04:00
2026-01-07 14:14:57 -05:00
2026-03-23 14:04:48 -05:00
2025-10-14 11:03:00 -04:00
2025-08-04 15:25:26 -04:00