Upgraded mga2 (i586) installation in VBox to mga3 with DVD (release Nov 8th). Everything works like charm :) But after reboot I've got a wast amount of following messages (several per seconds!) using journalctl -f: Nov 10 00:43:51 MGA2_32BIT systemd[1]: Starting System Logging Service... Nov 10 00:43:51 MGA2_32BIT systemd[1]: rsyslog.service start request repeated too quickly, refusing to start. Nov 10 00:43:51 MGA2_32BIT systemd[1]: Failed to start System Logging Service. systemctl status revealed: [root@MGA2_32BIT test]# systemctl status syslog.service rsyslog.service - System Logging Service Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled) Active: activating (start-pre) since Sat, 2012-11-10 01:00:30 CET; 349ms ago Control: 4788 (systemctl) CGroup: name=systemd:/system/rsyslog.service â control â 4788 /bin/systemctl stop systemd-kmsg-syslogd.service... Nov 10 01:00:30 MGA2_32BIT systemd[1]: Failed to start System Logging Service. Nov 10 01:00:30 MGA2_32BIT systemd[1]: Failed to start System Logging Service. Nov 10 01:00:30 MGA2_32BIT systemd[1]: Failed to start System Logging Service. Nov 10 01:00:30 MGA2_32BIT systemd[1]: Failed to start System Logging Service. Nov 10 01:00:30 MGA2_32BIT systemd[1]: Failed to start System Logging Service. Nov 10 01:00:30 MGA2_32BIT systemd[1]: Failed to start System Logging Service. [...]
CC: (none) => marc.lattemannWhiteboard: (none) => 3alpha3
CC: (none) => mageia, tmbComponent: Installer => RPM PackagesBlocks: (none) => 8016, 8039Source RPM: (none) => rsyslog
I think something must be messed up as I dropped this ExecStartPre thing 4 months ago: http://svnweb.mageia.org/packages/cauldron/rsyslog/current/SOURCES/rsyslog-5.8.11-systemd.patch?revision=267901&view=markup Are you sure your rsyslog package was updated properly during the upgrade? Can you do rpm -qV rsyslog?
As systemd now provides syslog daemon rsyslog never made it to the install medias, so it does not get upgraded. I guess we need to decide if we should do a versioned obsolete against rsyslog if we intend to defult to the systemd one. And then the versioned obsolete must be set so people can install rsyslog in mga3 again if they want/need it.
Ahh yeah I see how that happened now. Thanks Thomas. Interesting issue. I wonder what the best solution is here? I'm not necessarily in favour of removing rsyslog automatically so perhaps we should just find a way to make sure rsyslog is included in the media to prevent this kind of problem and let people rpm -e it afterwords if they want to (I don't want to be accused of "forcing" the removal of a traditional syslog daemon!) I'm happy for new installs not to install rsyslog by default tho'. Actually, was there not a proposal to remove upgrade mode from the media-based installers?
OK, so I've made some changes here: I made systemd provide "system-logger" rather than "syslog-daemon" and updated every package that required syslog-daemon to require system-logger instead. This is a rather pointless change were it not for me adding a require on syslog-daemon to the fail2ban package (although it will likely get a release at some point to support journal directly which would be nice when it arrives). This doesn't solve the fundamental problem of not including rsyslog on the isos tho', so someone who knows how to do this should find some clever way.
Also I can add versioned conflicts or obsoletes to systemd package so that rsyslog and syslog-ng are removed on upgrade if it's not in the install media... this would maybe annoy people (i.e. they'd have to reinstall it if they want it but as the old version would be broken anyway, it's hardly much different - although I bet someone will use it as justification of some elaborate plot ;))
Summary: Mga3Alpha3: rsyslog.service failed after upgrading with mga3-DVD => Mga3Alpha3: rsyslog package not included on mga3 install media leading to upgrade problems
add something in the prefer.vendor.list ? http://svnweb.mageia.org/packages/cauldron/meta-task/current/SOURCES/prefer.vendor.list
CC: (none) => ennael1
I don't think that causes it to be included in the iso if nothing else on the iso requires it.... that's kinda the problem now. Nothing specifically requires it any more (other than fail2ban!). rsyslog is already listed in the prefer list.
So what about this bug ?
Dunno. Like I said above, there is no specific requirement on it except in a few packages where it's really needed. As a result it'll likely not be included in the isos unless it's specifically included in some list somewhere... I'm not really sure where those lists live.
Included in bcd lists. tmb can you check it for live isos?
not needed for live images, as we dont support upgrades with them. new inställs should default to journald. So closing as fixes per comment 10
Status: NEW => RESOLVEDResolution: (none) => FIXED