[Bug 696963] New: systemd does not start syslog
https://bugzilla.novell.com/show_bug.cgi?id=696963 https://bugzilla.novell.com/show_bug.cgi?id=696963#c0 Summary: systemd does not start syslog Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: mt@novell.com ReportedBy: aj@novell.com QAContact: qa@suse.de CC: kasievers@novell.com Blocks: 696902 Found By: --- Blocker: --- Currently systemd does not start syslog at all. This might be a fallout from removing the syslog.service file from the syslog package. I have to start syslog manually and then it runs fine... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=696963 https://bugzilla.novell.com/show_bug.cgi?id=696963#c1 --- Comment #1 from Kay Sievers <kasievers@novell.com> 2011-05-30 13:12:38 UTC --- Please just install the upstream-maintained native systemd service files named after the syslog implementation, and drop the multiplexing of all possible syslog implementations through the magic SUSE sysconfig script on systemd boots. We need proper and unified native management of services, and which implementation of syslog should be started is to be configured by: systemctrl enable/disable, and not by magic multiplex switches in SUSE config files, which we should avoid in the future for many reasons. Syslog is special regarding SYSV compatibility. The current version of systemd requires socket passing to be active for syslog to integrate with systemd's only syslog logic, and will only work with native service files and not with SYSV compat scripts. Systemd also does not support any klogd-like process listening for kernel messages and forwarding them to /dev/log. It will create a message loop with the systemd's own kmsg bridge. The syslog implementation needs to support reading kernel messages directly, to integrate properly with systemd, or needs to explicitly work around such issues. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=696963 https://bugzilla.novell.com/show_bug.cgi?id=696963#c2 Bruno Friedmann <bruno@ioda-net.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bruno@ioda-net.ch --- Comment #2 from Bruno Friedmann <bruno@ioda-net.ch> 2011-05-30 14:01:03 UTC --- For 12.1, if we go with systemd we have to choose one of the syslog we have syslog, syslog-ng, rsyslog which one is the best to use and to be push as default/recommanded ? Also there's a need in packaging to not force one of them but ask for capabilities. Example a plain factory use now rsyslog, if you ask for webyast you get syslog-ng -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=696963 https://bugzilla.novell.com/show_bug.cgi?id=696963#c3 Marius Tomaschewski <mt@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |656259 AssignedTo|mt@novell.com |kasievers@novell.com --- Comment #3 from Marius Tomaschewski <mt@novell.com> 2011-05-30 14:19:26 UTC --- Until now I just see a regression in systemd that disallows LSB service starts. There is a feature request about improving the syslog / systemd issue: https://features.opensuse.org/311316 I guess, I'll not have time to work on this before August or something like this. BTW: Using service file names named after the syslog daemon implementation as described by Kay above (rsyslog.service, syslogd.service, ...) needs a split out of every syslog-daemon into a <name>-systemd and <name>-sysvinit to provide e.g. log rotation files with the correct systemctl action <name>.service actions. There will be no possibility any more to provide a custom config file (/etc/rsyslog.d/foo-bar.conf) with log destination for a program and a log rotation file without to follow the -systemd / -sysvinit split because of the systemctl log rotation call that needs the implementation name in the log rotation file. IMO a step backward instead forward. The limitation with klogd is AFAIR a systemd bug tracked already on 11.4. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=696963 https://bugzilla.novell.com/show_bug.cgi?id=696963#c4 --- Comment #4 from Dr. Werner Fink <werner@novell.com> 2011-05-30 14:39:27 UTC --- (In reply to comment #2) Most enterprise users want to have the choice between all three sysloggers and the openSUSE is the base of all enterprise products. Next is that systemd should not abuse the kernel kprintf logging buffer but use its own logging ring buffer. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=696963 https://bugzilla.novell.com/show_bug.cgi?id=696963#c5 --- Comment #5 from Kay Sievers <kasievers@novell.com> 2011-05-30 14:48:56 UTC --- (In reply to comment #2)
which one is the best to use and to be push as default/recommanded ?
For now it's rsyslog, which is actively tested and supported from upstream. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=696963 https://bugzilla.novell.com/show_bug.cgi?id=696963#c6 --- Comment #6 from Kay Sievers <kasievers@novell.com> 2011-05-30 15:01:34 UTC ---
(In reply to comment #2)
Most enterprise users want to have the choice between all three sysloggers and the openSUSE is the base of all enterprise products.
Sure, if the syslog implementation supports systemd, it can be enabled/disabled with systemctl commands. No magic needed here, it will work just fine, like everything else on the system.
Next is that systemd should not abuse the kernel kprintf logging buffer but use its own logging ring buffer.
"Abuse' is your personal opinion, which the systemd developers don't share. We have quite to opposite feedback on this feature from many people involved in this decision. Early-boot messages are mixed with the kernel messages, in 'dmesg' and that's exactly what you want to look at if things go wrong. These days it does not matter at all if boot/init components run in user- or kernel-space, hence they should log to the same target during early boot, until a real syslog is available. Laptop- and embedded-like setups do not need to run any syslog service at all, but they still have a fully working 'syslog' from the kernel. It's just that nothing is ever written to disk. Rsyslog can distinguish the userspace messages from the kernel messages just fine, and can even write them to different log files. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=696963 https://bugzilla.novell.com/show_bug.cgi?id=696963#c7 --- Comment #7 from Dr. Werner Fink <werner@novell.com> 2011-05-30 15:12:21 UTC --- (In reply to comment #6) With this approach you're not able to report all kernel and system messages send to /dev/console to all console devices. This is IMHO required for all systems using e.g. a serial console together with an other console e.g a virtual one or a simple printer. OK most openSUSE nor Fedora users will use this features but our enterprise customers do. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=696963 https://bugzilla.novell.com/show_bug.cgi?id=696963#c8 --- Comment #8 from Dr. Werner Fink <werner@novell.com> 2011-05-30 15:18:57 UTC --- NB: I'm willingly to port the main features of blogd to systemd if and only if this work is not for the waste basket of the upstream developers of systemd. Last month I've ported the main features of mingetty to agetty of the current util-linux tree and Karel Zak has accepeted my patches. The only question is due to my rare time for such a work (I'm currently hunting bugs in the ksh93u and ksh93t) if such a contribution will be accepted or not. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=696963 https://bugzilla.novell.com/show_bug.cgi?id=696963#c9 --- Comment #9 from Kay Sievers <kasievers@novell.com> 2011-05-30 15:31:32 UTC --- (In reply to comment #7)
(In reply to comment #6)
With this approach you're not able to report all kernel and system messages send to /dev/console to all console devices. This is IMHO required for all systems using e.g. a serial console together with an other console
We should not try to make userspace 'smarter' than the kernel with its log messages? We must avoid handling early-boot messages from the kernel differently than the ones from early boot tools. Today it is just an irrelevant detail if an early-boot tool runs in kernel- or userspace. The only visible difference should be the facility value of the syslog prefix. I does not make much sense to have early-boot and kernel bootup-messages separate. These messages belong together during the time the system is brought up. The messages the kernel sends out need to show up the same way, and on all the same devices. So if there is anything missing, please let's change the kernel, and not work around it in userspace without being able to provide a complete solution to the problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=696963 https://bugzilla.novell.com/show_bug.cgi?id=696963#c10 Kay Sievers <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kasievers@novell.com |bnc-team-screening@forge.pr | |ovo.novell.com --- Comment #10 from Kay Sievers <kasievers@novell.com> 2011-05-30 15:43:10 UTC --- Reassign to default. I have zero time to work on syslog issues. They need to be fixed in the syslog package not in systemd. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=696963 https://bugzilla.novell.com/show_bug.cgi?id=696963#c Kay Sievers <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|systemd does not start |syslog: missing native |syslog |systemd service files -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=696963 https://bugzilla.novell.com/show_bug.cgi?id=696963#c Andreas Jaeger <aj@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |mt@novell.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=696963 https://bugzilla.novell.com/show_bug.cgi?id=696963#c12 Dr. Werner Fink <werner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |coolo@novell.com InfoProvider| |aj@novell.com Severity|Major |Enhancement --- Comment #12 from Dr. Werner Fink <werner@novell.com> 2011-05-31 08:05:50 UTC --- I've no time do work on this. Beside I'd like to see an real answer on my question in comment #8 (In reply to comment #9) Our enterprise customers using serial consoles in combination with virtual consoles (and there are a lot of customers) will not agree with you're point of view. It would be help a lot if you and/or the upstream developer of systemd would not that snootily, that is instead of ignoring requests from paying customers and the existing solutions for such requests. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=696963 https://bugzilla.novell.com/show_bug.cgi?id=696963#c13 Andreas Jaeger <aj@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|aj@novell.com | --- Comment #13 from Andreas Jaeger <aj@novell.com> 2011-05-31 12:16:49 UTC --- IMO this is not blocking adoption for openSUSE 12.1. For SLES 12 I expect that we need this, so after talking with mge, I created a feature for this, please help me to improve the feature. It's https://features.opensuse.org/312466 Btw. I'm submitting a rsyslog with native systemd service file again to factory now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=696963 https://bugzilla.novell.com/show_bug.cgi?id=696963#c14 --- Comment #14 from Bernhard Wiedemann <bwiedemann@novell.com> 2011-06-01 01:00:13 CEST --- This is an autogenerated message for OBS integration: This bug (696963) was mentioned in https://build.opensuse.org/request/show/72365 Factory / rsyslog -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=696963 https://bugzilla.novell.com/show_bug.cgi?id=696963#c15 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #15 from Dr. Werner Fink <werner@suse.com> 2011-09-02 16:32:10 UTC --- fixed -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com