[Bug 2026292] [NEW] conflict on syslog.service when moving between rsyslog and busybox-syslogd
Dan Bungert
2026292 at bugs.launchpad.net
Thu Jul 6 15:24:26 UTC 2023
Public bug reported:
Suppose a system with systemd 252 and rsyslog installed. Install
busybox-syslogd version 1:1.36.1-3ubuntu1, which will cause rsyslog to
be removed (but not purged). The install of busybox-syslogd will fail
as follows:
Failed to preset unit, file "/etc/systemd/system/syslog.service" already
exists and is a symlink to "/lib/systemd/system/rsyslog.service".
The failure can also be seen in the reverse direction - busybox-syslogd
1:1.36.1-3ubuntu1 installed, then install rsyslog.
With systemd 253, we instead see:
Removed "/etc/systemd/system/syslog.service".
Workarounds:
* use systemd 253 when available
* purge the existing system-log-daemon before installing the new one
** Affects: busybox (Ubuntu)
Importance: Undecided
Status: New
** Affects: rsyslog (Ubuntu)
Importance: Undecided
Status: New
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: rsyslog (Ubuntu)
Importance: Undecided
Status: New
** Also affects: busybox (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/2026292
Title:
conflict on syslog.service when moving between rsyslog and busybox-
syslogd
Status in busybox package in Ubuntu:
New
Status in rsyslog package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Bug description:
Suppose a system with systemd 252 and rsyslog installed. Install
busybox-syslogd version 1:1.36.1-3ubuntu1, which will cause rsyslog to
be removed (but not purged). The install of busybox-syslogd will fail
as follows:
Failed to preset unit, file "/etc/systemd/system/syslog.service"
already exists and is a symlink to
"/lib/systemd/system/rsyslog.service".
The failure can also be seen in the reverse direction - busybox-
syslogd 1:1.36.1-3ubuntu1 installed, then install rsyslog.
With systemd 253, we instead see:
Removed "/etc/systemd/system/syslog.service".
Workarounds:
* use systemd 253 when available
* purge the existing system-log-daemon before installing the new one
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2026292/+subscriptions
More information about the foundations-bugs
mailing list