Skip to content

fix: enable rsyslog so rotv actually forwards its logs (RT #1460) - #580

Open
fatherlinux wants to merge 2 commits into
masterfrom
fix/enable-rsyslog-forwarding
Open

fix: enable rsyslog so rotv actually forwards its logs (RT #1460)#580
fatherlinux wants to merge 2 commits into
masterfrom
fix/enable-rsyslog-forwarding

Conversation

@fatherlinux

Copy link
Copy Markdown
Member

rotv ships the forwarding drop-in from ubi10-core but with rsyslog.service disabled, so it looks correctly configured and sends nothing.

$ podman exec rootsofthevalley.org systemctl is-enabled rsyslog
disabled
$ podman exec rootsofthevalley.org ls /etc/rsyslog.d/00-crunchtools-forward.conf
-rw-r--r--. 1 root root 1986 Aug 23 17:11 ...   # config is there

Why

CI builds FROM quay.io/crunchtools/rotv-base:latest, not directly from ubi10-core, so the enable symlink ubi10-core creates does not reliably reach the final image. Confirmed by comparing the two:

ubi10-core:  etc/systemd/system/multi-user.target.wants/rsyslog.service
rotv:        etc/systemd/system/multi-user.target.wants/postgresql.service    <- no rsyslog

Enabling it explicitly makes this independent of whatever the pre-baked base happens to carry.

Worth a separate look

The rotv-base indirection means rotv can silently lag ubi10-core in other ways too. Anything added to the shared base is only guaranteed to reach rotv once rotv-base is rebuilt.

Every other systemd container on lotor picked this up correctly in today's rollout — rotv is the only one that didn't.

🤖 Generated with Claude Code

https://claude.ai/code/session_014dGq9ivDC6sqeJJfkra6C2

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gatehouse found no issues.

rotv shipped with the forwarding drop-in from ubi10-core present at
/etc/rsyslog.d/00-crunchtools-forward.conf, but with rsyslog.service DISABLED
-- so it sent nothing to the central collector while looking correctly
configured.

Cause: CI builds this image FROM quay.io/crunchtools/rotv-base rather than
directly from ubi10-core, so the enable symlink ubi10-core creates does not
reliably survive into the final image. Verified by inspecting both:

  ubi10-core: etc/systemd/system/multi-user.target.wants/rsyslog.service
  rotv:       etc/systemd/system/multi-user.target.wants/postgresql.service   (no rsyslog)

Enabling it explicitly alongside the other services makes this independent of
what the pre-baked base happens to carry.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014dGq9ivDC6sqeJJfkra6C2
@fatherlinux
fatherlinux force-pushed the fix/enable-rsyslog-forwarding branch from ea9e457 to 5f05921 Compare August 23, 2026 18:31

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gatehouse found no issues.

Gatehouse flagged that nothing guarded the fix in the previous commit, which is
fair -- the regression it fixes was invisible precisely because the config file
was present and only the service was off.

Asserted in tests.yml, which already boots the image under systemd. Checked
here rather than assumed from ubi10-core's own smoke test, because CI builds
this image FROM rotv-base and the enable does not reliably survive that hop.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014dGq9ivDC6sqeJJfkra6C2

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gatehouse found no issues.

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

Successfully merging this pull request may close these issues.

1 participant