Skip to content

Uninstalling rsyslog to use syslog-ng uninstalls google-compute-engine and breaks a lot of stuff #20

@fdr

Description

@fdr

As-is, removing rsyslog on CentOS 8 uninstalls critical google cloud functionality because of this dependency:

I stumbled upon this because after uninstalling rsyslog, my startup scripts would not work, neither would browser SSH nor key management. Upon running reqoquery and inspecting google-compute-engine, I realized I shouldn't use GCP without this package.

The Debian version has been changed to rely on a virtual package to solve this, but there's no similar remedy for CentOS et al yet: GoogleCloudPlatform/compute-image-packages#548, GoogleCloudPlatform/compute-image-packages@f3fd94c. The virtual package name provided by both rsyslog and syslog-ng on CentOS 8 is syslog:

$ comm -12 <(repoquery --provides rsyslog | sort) <(repoquery --provides syslog-ng | sort)
syslog

The only unique thing rsyslog gets is kernel logs, and perhaps a duplicate copy of all daemon facility logs (when systemd is present):

daemon,kern.* /dev/console

Forwarding the "daemon" facility was made redundant for systemd OSes in GoogleCloudPlatform/compute-image-packages@aaea64d

Though there are various forms of solution, I don't think kernel logs in the console are worth breaking ssh key management, startup-scripts, etc should one uninstall rsyslog, if it came down to that. If you want, I can furnish and test a syslog-ng configuration fragment to send kernel output to the console, so things can Just Work for the two major syslog implementations.

A duplicate issue from last year:
GoogleCloudPlatform/compute-image-packages#897

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions