- This topic has 10 replies, 6 voices, and was last updated Jul 8-10:44 pm by Yuzeff.
- Posts
david235
I run a sysvinit sid system and after a recent reboot noticed no logging to syslog, messages etc. and rsyslog was not running, when I entered “service rsyslog start” got
“unknown service”
rsyslog was updated on 11/8 from 8.2110.0-1 to 8.2110.0-2 and the updated deb file does not contain the /etc/init.d/rsyslog entry and the postinst code removes any /etc/init.d entry.I reinstated rsyslog in /etc/init.d and all ok again
I cannot find any documentation about this change
- This topic was modified 1 year, 5 months ago by anticapitalista. Reason: solved
anticapitalistaI cannot find any documentation about this change
Look at Debian changelogs since that is where the deb comes from.
No doubt the packager(s) don’t want to support anything other than systemd …Found it for you
rsyslog (8.2110.0-2) unstable; urgency=medium * Remove SysV init script -- Michael Biebl <biebl@debian.org> Fri, 05 Nov 2021 23:29:45 +0100BTW Debian sid now has rsyslog (8.2110.0-3 and others)
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
ModdIt
Mailed the guy, bug reports are aplentay,
Not expecting any answer, the more persons protest the more likely somebody may turn over in their sleep
and realise without users and supporters debian becomes a dead duck. By supporters i mean paying kind too.
My christmas donation will be for antiX.Post that soeone who thinks of users has turned over the removal. Poor poettering, his linux cancer init
madness is not convincing everyone.Thank-you.
Of course I should have looked at the changelogs, I use apt-listchanges and found it only lists Debian NEWS by default.
Many thanks to you and your team for a fine distro.
seriousnessI noticed the same issue in antiX-21 stable and followed this Workaround.
seriousnessIt should be possible to get back the removed SysV init scripts by installing package orphan-sysvinit-scripts.
I have not tried this yet, since rsyslog is the only one I need at the moment.
seriousnessTodays update of rsyslog solves this for all users – thanx!
stevesr0
Hi all who posted on this thread,
I run Sid and only vaguely felt that some log files had gone missing. Have MANUALLY installed today’s update (8.2206.0-1.0nosystemd1) and I see many new files installed.
(Since apt full-upgrade didn’t automagically install it, it is possible I hadn’t installed it initially?)Thanks.
Two questions – (1) does this update “permanently” fix the problem or will future versions from debian once more eliminate the rsyslog packages if updated?
(2) If they do automagically remove rsyslog packages, does the orphan-sysvinit-scripts package act to maintain rsyslog files and functions?stevesr0
YuzeffI noticed the same issue in antiX-21 stable and followed this Workaround.
Thank you for pointing this out, it solved the problem. Neither orphan-sysvinit-scripts nor rsyslog updating/reinstalling to 8.2206.0-1.0nosystemd1 helped in my case. I use antiX-21 Full (stable).
- This reply was modified 1 year, 4 months ago by Yuzeff.
My Dell Vostro 1710: Core 2 Duo T6600 2.2 GHz, 4 GB RAM, 240 GB SSD, Intel 965GM Integrated Graphics, 1440x900, antiX 22 full.
anticapitalistaInstead of following the workaround, it is better to do the following.
sudo apt purge rsyslog sudo apt install rsyslogPhilosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Yuzeff@anticapitalista, thank you! Just checked it out and syslog is present.
My Dell Vostro 1710: Core 2 Duo T6600 2.2 GHz, 4 GB RAM, 240 GB SSD, Intel 965GM Integrated Graphics, 1440x900, antiX 22 full.
- You must be logged in to reply to this topic.