maybe someone of the server SIG could try to explain the systemd-maintainers that calculation and that this is unacceptable on real-world servers because it burries any interesting information
the way systemd in Rawhide now logs make it unacceptable on production servers and that said from someone running Fedora on a lot of real-world servers for 6 years now
https://bugzilla.redhat.com/show_bug.cgi?id=1072368#c8
if the "Stopping", "Stopped", "Removed", "Starting" and "Reached" messages would only have a prefix to filter them out with rsyslog, currently you can't distinct them between system-wide messages
such flooing up to a self-DOS belongs in a debug level ________________________________________________
[root@rawhide ~]# rpm -q systemd systemd-212-5.fc21.x86_64
[root@rawhide ~]# cat messages May 27 12:44:25 rawhide systemd[1]: Stopping User Manager for UID 0... May 27 12:44:25 rawhide systemd[531]: Stopping Default. May 27 12:44:25 rawhide systemd[531]: Stopped target Default. May 27 12:44:25 rawhide systemd[531]: Stopping Basic System. May 27 12:44:25 rawhide systemd[531]: Stopped target Basic System. May 27 12:44:25 rawhide systemd[531]: Stopping Paths. May 27 12:44:25 rawhide systemd[531]: Stopped target Paths. May 27 12:44:25 rawhide systemd[531]: Stopping Timers. May 27 12:44:25 rawhide systemd[531]: Stopped target Timers. May 27 12:44:25 rawhide systemd[531]: Stopping Sockets. May 27 12:44:25 rawhide systemd[531]: Stopped target Sockets. May 27 12:44:25 rawhide systemd[531]: Starting Shutdown. May 27 12:44:25 rawhide systemd[531]: Reached target Shutdown. May 27 12:44:25 rawhide systemd[531]: Starting Exit the Session... May 27 12:44:25 rawhide systemd[531]: Received SIGRTMIN+24 from PID 687 (kill). May 27 12:44:25 rawhide systemd[1]: Stopped User Manager for UID 0. May 27 12:44:25 rawhide systemd[1]: Stopping user-0.slice. May 27 12:44:25 rawhide systemd[1]: Removed slice user-0.slice. May 27 13:01:01 rawhide systemd[1]: Starting user-0.slice. May 27 13:01:01 rawhide systemd[1]: Created slice user-0.slice. May 27 13:01:01 rawhide systemd[1]: Starting User Manager for UID 0... May 27 13:01:01 rawhide systemd[697]: Starting Paths. May 27 13:01:01 rawhide systemd[697]: Reached target Paths. May 27 13:01:01 rawhide systemd[697]: Starting Timers. May 27 13:01:01 rawhide systemd[697]: Reached target Timers. May 27 13:01:01 rawhide systemd[697]: Starting Sockets. May 27 13:01:01 rawhide systemd[697]: Reached target Sockets. May 27 13:01:01 rawhide systemd[697]: Starting Basic System. May 27 13:01:01 rawhide systemd[697]: Reached target Basic System. May 27 13:01:01 rawhide systemd[697]: Starting Default. May 27 13:01:01 rawhide systemd[697]: Reached target Default. May 27 13:01:01 rawhide systemd[697]: Startup finished in 9ms. May 27 13:01:01 rawhide systemd[1]: Started User Manager for UID 0. May 27 13:01:01 rawhide systemd[1]: Stopping User Manager for UID 0... May 27 13:01:01 rawhide systemd[697]: Stopping Default. May 27 13:01:01 rawhide systemd[697]: Stopped target Default. May 27 13:01:01 rawhide systemd[697]: Stopping Basic System. May 27 13:01:01 rawhide systemd[697]: Stopped target Basic System. May 27 13:01:01 rawhide systemd[697]: Stopping Paths. May 27 13:01:01 rawhide systemd[697]: Stopped target Paths. May 27 13:01:01 rawhide systemd[697]: Stopping Timers. May 27 13:01:01 rawhide systemd[697]: Stopped target Timers. May 27 13:01:01 rawhide systemd[697]: Stopping Sockets. May 27 13:01:01 rawhide systemd[697]: Stopped target Sockets. May 27 13:01:01 rawhide systemd[697]: Starting Shutdown. May 27 13:01:01 rawhide systemd[697]: Reached target Shutdown. May 27 13:01:01 rawhide systemd[697]: Starting Exit the Session... May 27 13:01:01 rawhide systemd[697]: Received SIGRTMIN+24 from PID 726 (kill). May 27 13:01:01 rawhide systemd[1]: Stopped User Manager for UID 0. May 27 13:01:01 rawhide systemd[1]: Stopping user-0.slice. May 27 13:01:01 rawhide systemd[1]: Removed slice user-0.slice. May 27 14:01:01 rawhide systemd[1]: Starting user-0.slice. May 27 14:01:01 rawhide systemd[1]: Created slice user-0.slice. May 27 14:01:01 rawhide systemd[1]: Starting User Manager for UID 0... May 27 14:01:01 rawhide systemd[740]: Starting Paths. May 27 14:01:01 rawhide systemd[740]: Reached target Paths. May 27 14:01:01 rawhide systemd[740]: Starting Timers. May 27 14:01:01 rawhide systemd[740]: Reached target Timers. May 27 14:01:01 rawhide systemd[740]: Starting Sockets. May 27 14:01:01 rawhide systemd[740]: Reached target Sockets. May 27 14:01:01 rawhide systemd[740]: Starting Basic System. May 27 14:01:01 rawhide systemd[740]: Reached target Basic System. May 27 14:01:01 rawhide systemd[740]: Starting Default. May 27 14:01:01 rawhide systemd[740]: Reached target Default. May 27 14:01:01 rawhide systemd[740]: Startup finished in 7ms. May 27 14:01:01 rawhide systemd[1]: Started User Manager for UID 0. May 27 14:01:01 rawhide systemd[1]: Stopping User Manager for UID 0... May 27 14:01:01 rawhide systemd[740]: Stopping Default. May 27 14:01:01 rawhide systemd[740]: Stopped target Default. May 27 14:01:01 rawhide systemd[740]: Stopping Basic System. May 27 14:01:01 rawhide systemd[740]: Stopped target Basic System. May 27 14:01:01 rawhide systemd[740]: Stopping Paths. May 27 14:01:01 rawhide systemd[740]: Stopped target Paths. May 27 14:01:01 rawhide systemd[740]: Stopping Timers. May 27 14:01:01 rawhide systemd[740]: Stopped target Timers. May 27 14:01:01 rawhide systemd[740]: Stopping Sockets. May 27 14:01:01 rawhide systemd[740]: Stopped target Sockets. May 27 14:01:01 rawhide systemd[740]: Starting Shutdown. May 27 14:01:01 rawhide systemd[740]: Starting Exit the Session... May 27 14:01:01 rawhide systemd[740]: Received SIGRTMIN+24 from PID 769 (kill). May 27 14:01:01 rawhide systemd[1]: Stopped User Manager for UID 0. May 27 14:01:01 rawhide systemd[1]: Stopping user-0.slice. May 27 14:01:01 rawhide systemd[1]: Removed slice user-0.slice. May 27 14:13:59 rawhide systemd[1]: Starting user-0.slice. May 27 14:13:59 rawhide systemd[1]: Created slice user-0.slice. May 27 14:13:59 rawhide systemd[1]: Starting User Manager for UID 0... May 27 14:13:59 rawhide systemd[798]: Starting Paths. May 27 14:13:59 rawhide systemd[798]: Reached target Paths. May 27 14:13:59 rawhide systemd[798]: Starting Timers. May 27 14:13:59 rawhide systemd[798]: Reached target Timers. May 27 14:13:59 rawhide systemd[798]: Starting Sockets. May 27 14:13:59 rawhide systemd[798]: Reached target Sockets. May 27 14:13:59 rawhide systemd[798]: Starting Basic System. May 27 14:13:59 rawhide systemd[798]: Reached target Basic System. May 27 14:13:59 rawhide systemd[798]: Starting Default. May 27 14:13:59 rawhide systemd[798]: Reached target Default. May 27 14:13:59 rawhide systemd[798]: Startup finished in 8ms. May 27 14:13:59 rawhide systemd[1]: Started User Manager for UID 0.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 05/27/2014 08:30 AM, Reindl Harald wrote:
maybe someone of the server SIG could try to explain the systemd-maintainers that calculation and that this is unacceptable on real-world servers because it burries any interesting information
the way systemd in Rawhide now logs make it unacceptable on production servers and that said from someone running Fedora on a lot of real-world servers for 6 years now
https://bugzilla.redhat.com/show_bug.cgi?id=1072368#c8
if the "Stopping", "Stopped", "Removed", "Starting" and "Reached" messages would only have a prefix to filter them out with rsyslog, currently you can't distinct them between system-wide messages
such flooing up to a self-DOS belongs in a debug level
It seems to me that a more useful (and generic) solution to this would be to create a rules-engine for specifying what messages get sent through the syslog output (and if sent, optionally prefixed).
The internal journal message containing these start/stop notifications have a number of useful structuring elements that would make it easy to filter on, if such a rules engine was devised.
Am 28.05.2014 15:17, schrieb Stephen Gallagher:
On 05/27/2014 08:30 AM, Reindl Harald wrote:
maybe someone of the server SIG could try to explain the systemd-maintainers that calculation and that this is unacceptable on real-world servers because it burries any interesting information
the way systemd in Rawhide now logs make it unacceptable on production servers and that said from someone running Fedora on a lot of real-world servers for 6 years now
if the "Stopping", "Stopped", "Removed", "Starting" and "Reached" messages would only have a prefix to filter them out with rsyslog, currently you can't distinct them between system-wide messages
such flooing up to a self-DOS belongs in a debug level
It seems to me that a more useful (and generic) solution to this would be to create a rules-engine for specifying what messages get sent through the syslog output (and if sent, optionally prefixed).
The internal journal message containing these start/stop notifications have a number of useful structuring elements that would make it easy to filter on, if such a rules engine was devised.
hm - they are *all* un-needed because you have the information redundant and i have already rsyslog rules to not clutter /var/log/messages on F19/F20
all that log records are only interesting most of the time for a systemd-developer or in case of debug while "replay" a bootlog without any hint that it is triggered just by a cronjob isn't that helpful in general
that the systemd developers want that messages and point to journald and filtering is nice, but they have to accept that there are workflows which are using classical syslog even if it is only because mysql-logging
/var/log/secure: May 28 15:05:01 localhost systemd-logind[381]: New session 42457 of user root. May 28 15:05:01 localhost systemd-logind[381]: Removed session 42457. May 28 15:05:01 localhost su: pam_unix(su:session): session opened for user wwwcron by (uid=0) May 28 15:05:01 localhost su: pam_unix(su:session): session closed for user wwwcron
/var/log/cron: May 28 15:05:01 localhost CROND[1315]: (wwwcron) CMD (*************) ___________________________________
# Log systemd-logind to /var/log/secure :programname, isequal, "systemd-logind" -/var/log/secure :programname, isequal, "systemd-logind" ~ :msg, contains, "Starting Session" ~ :msg, contains, "Started Session" ~ :msg, contains, "Stopping Session" ~ :msg, contains, "Stopped Session" ~
server@lists.fedoraproject.org
-
Reindl Harald -
Stephen Gallagher