[Bug 671525] New: klogd / systemd-kmsg-sy: kernel messages all over the place (not stopping ever, cpu load)
https://bugzilla.novell.com/show_bug.cgi?id=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c0 Summary: klogd / systemd-kmsg-sy: kernel messages all over the place (not stopping ever, cpu load) Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: abittner@stud.fh-heilbronn.de QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:2.0b11) Gecko/20110203 Firefox/4.0b11 i was already on 11.4 rc1 from like two days ago, today i did a zypper ref and zypper dup again (i had this syslog-ng bug, it didnt come up due to some missing characters in the syslog conf files or something). anyways, i checkd if i was getting anything new in /var/log/messages, and thats when i found these zillion kernel messagings getting dumped there.... --------------- rnel[2925]: [ 213.562255] kernel[2925]: [ 213.524767] kernel[2925]: [ 213.501687] kernel[2925]: [ 213.475166] kernel[2925]: [ 213.456092] kernel[2925]: [ 213.433368] kernel[2925]: [ 213.403563] kernel[2925]: [ 213.366622] kernel[2925]: [ 213.327072] kernel[2925]: [ 213.293427] kernel[2925]: [ 213.255928] kernel[2925]: [ 213.232875] kernel[2925]: [ 213.204521] kernel[2925]: [ 213.183374] kernel[2925]: [ 213.165161] kernel[2925]: [ 213.145492] kernel[2925]: [ 213.119132] kernel[2925]: [ 213.100595] kernel[2925]: [ 213.080360] kernel[2925]: [ 213.053905] kernel[2925]: [ 213.011398] kernel[2925]: [ 212.982092] kernel[2925]: [ 212.962341] kernel[2925]: [ 212.936817] kernel[2925]: [ 212.902003] kernel[2925]: [ 212.869311] kernel[2925]: [ 212.813554] kernel[2925]: [ 212.770844] kernel[2925]: [ 212.722579] kernel[2925]: [ 212.686238] kernel[2925]: [ 212.624 Feb 12 13:03:32 localhost kernel: [ 213.846679] kernel[2925]: [ 213.781598] kernel[2925]: [ 213.716124] kernel[2925]: 967] kernel[2925]: [ 212.508 213.402436] kernel[2925]: [ 213.365151] kernel[2925]: [ 213.325580] kernel[2925]: 210.061 Feb 12 13:03:32 localhost kernel: [ 213.863858] kernel[2925]: [ 213.804748] kernel[2925]: [ 213.744000] kernel[2925]: [ 213.691870] kernel[2925]: [ 213.656984] kernel[2925]: [ 213.602834] kernel[2925]: [ 213.559666] kernel[2925]: [ 213.524079] kernel[2925]: [ 213.500835] kernel[2925]: [ 213.474435] kernel[2925]: [ 213.455546] kernel[2925]: [ 213.432805] kernel[2925]: [ 213.402454] kernel[2925]: [ 213.365168] kernel[2925]: [ 213.325596] kernel[2925]: [ 213.290033] kernel[2925]: [ 213.255754] kernel[2925]: [ 213.232470] kernel[2925]: [ 213.204438] kernel[2925]: [ 213.182592] kernel[2925]: [ 213.164635] kernel[2925]: [ 213.145009] kernel[2925]: [ 213.118661] kernel[2925]: [ 213.100166] kernel[2925]: [ 213.079950] kernel[2925]: [ 213.052888] kernel[2925]: [ 213.003911] kernel[2925]: [ 212.981746] kernel[2925]: [ 212.962005] kernel[2925]: [ 212.936143] kernel[2925]: [ 212.901306] kernel[2925]: [ 212.868385] kernel[2925]: [ 212.810053] kernel[2925]: [ 212.770615] kernel[2925]: [ 212.722 Feb 12 13:03:32 localhost kernel: 362] kernel[2925]: [ 212.685 Feb 12 13:03:32 localhost kernel: [ 213.863875] kernel[2925]: 659] kernel[2925]: [ 212.623 Feb 12 13:03:32 localhost kernel: [ 213.863882] kernel[2925]: [ 213.804811] kernel[2925]: 832] kernel[2925]: [ 212.594 Feb 12 13:03:32 localhost kernel: [ 213.863889] kernel[2925]: [ 213.804860] kernel[2925]: [ 213.744118] kernel[2925]: 927] kernel[2925]: [ 212.550 Feb 12 13:03:32 localhost kernel: [ 213.863898] kernel[2925]: [ 213.804912] kernel[2925]: [ 213.744989] kernel[2925]: [ 213.691894] kernel[2925]: [ 213.657007] kernel[2925]: 646] kernel[2925]: [ 212.469 Feb 12 13:03:32 localhost kernel: [ 213.863908] kernel[2925]: [ 213.804964] kernel[2925]: [ 213.745001] kernel[2925]: [ 213.692107] kernel[2925]: [ 213.657013] kernel[2925]: [ 213.602856] kernel[2925]: 401] kernel[2925]: [ 212.449 Feb 12 13:03:32 localhost kernel: [ 213.863917] kernel[2925]: [ 213.805025] kernel[2925]: [ 213.745010] kernel[2925]: [ 213.692116] kernel[2925]: [ 213.657020] kernel[2925]: [ 213.602863] kernel[2925]: [ 213.559687] kernel[2925]: 255] kernel[2925]: [ 212.422 Feb 12 13:03:32 localhost kernel: [ 213.863928] kernel[2925]: [ 213.805082] kernel[2925]: [ 213.745019] kernel[2925]: [ 213.692124] kernel[2925]: [ 213.657027] kernel[2925]: [ 213.602870] kernel[2925]: [ 213.559692] kernel[2925]: [ 213.524100] kernel[2925]: 569] kernel[2925]: [ 212.380 Feb 12 13:03:32 localhost kernel: [ 213.875841] kernel[2925]: [ 213.845347] kernel[2925]: [ 213.779797] kernel[2925]: [ 213.715411] kernel[2925]: [ 213.674438] kernel[2925]: [ 213.633294] kernel[2925]: [ 213.585792] kernel[2925]: [ 213.533477] kernel[2925]: [ 213.506667] kernel[2925]: [ 213.486247] kernel[2925]: 339] kernel[2925]: [ 212.305 Feb 12 13:03:32 localhost kernel: [ 213.876145] kernel[2925]: [ 213.846008] kernel[2925]: [ 213.780456] kernel[2925]: 949] kernel[2925]: [ 212.561 Feb 12 13:03:32 localhost kernel: [ 213.877363] kernel[2925]: [ 213.846661] kernel[2925]: [ 213.781352] kernel[2925]: [ 213.716000] kernel[2925]: [ 213.675568] kernel[2925]: [ 213.634212] kernel[2925]: [ 213.586274] kernel[2925]: [ 213.533795] kernel[2925]: [ 213.507006] kernel[2925]: [ 213.486487] kernel[2925]: [ 213.460824] kernel[2925]: [ 213.441101] kernel[2925]: [ 213.410958] kernel[2925]: [ 213.375975] kernel[2925]: [ 213.334901] kernel[2925]: 440] kernel[2925]: 241] kerne ..... ---------------- never stopping, and top shows llike 100% (on one core) load, in some processes related to the klogd or something.... --------- Tasks: 121 total, 2 running, 119 sleeping, 0 stopped, 0 zombie Cpu(s): 17.8%us, 36.9%sy, 0.0%ni, 18.5%id, 25.7%wa, 0.0%hi, 1.2%si, 0.0%st Mem: 1025540k total, 895012k used, 130528k free, 146692k buffers Swap: 1550236k total, 0k used, 1550236k free, 467712k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 2925 root 20 0 2164 656 352 R 79 0.1 5:19.95 klogd 350 root 20 0 2208 564 464 S 62 0.1 3:46.00 systemd-kmsg-sy 662 root 20 0 101m 62m 4928 S 4 6.3 0:26.21 Xorg 3697 root 20 0 212m 24m 16m S 2 2.4 0:06.97 knotify4 270 root 20 0 0 0 0 D 2 0.0 1:00.89 kjournald 3671 root 20 0 144m 30m 23m S 2 3.0 0:07.19 kwin 3740 root 20 0 131m 21m 15m S 1 2.2 0:03.55 konsole 195 root 20 0 0 0 0 S 1 0.0 0:07.62 kworker/0:2 2899 root 20 0 7988 3964 2220 D 1 0.4 0:49.27 syslog-ng 1033 root 20 0 4140 1052 896 S 0 0.1 0:00.14 hald-addon-inpu 1 root 20 0 4904 3208 1776 S 0 0.3 0:01.46 systemd 2 root 20 0 0 0 0 S 0 0.0 0:00.02 kthreadd 3 root 20 0 0 0 0 S 0 0.0 0:00.24 ksoftirqd/0 6 root RT 0 0 0 0 S 0 0.0 0:00.00 migration/0 7 root RT 0 0 0 0 S 0 0.0 0:00.00 migration/1 9 root 20 0 0 0 0 S 0 0.0 0:00.04 ksoftirqd/1 10 root 20 0 0 0 0 S 0 0.0 0:00.22 kworker/0:1 11 root 0 -20 0 0 0 S 0 0.0 0:00.00 cpuset 12 root 0 -20 0 0 0 S 0 0.0 0:00.00 khelper 13 root 0 -20 0 0 0 S 0 0.0 0:00.00 netns 14 root 20 0 0 0 0 S 0 0.0 0:00.00 sync_supers 15 root 20 0 0 0 0 S 0 0.0 0:00.00 bdi-default 16 root 0 -20 0 0 0 S 0 0.0 0:00.00 kintegrityd 17 root 0 -20 0 0 0 S 0 0.0 0:00.00 kblockd 18 root 0 -20 0 0 0 S 0 0.0 0:00.00 kacpid 19 root 0 -20 0 0 0 S 0 0.0 0:00.00 kacpi_notify 20 root 0 -20 0 0 0 S 0 0.0 0:00.00 kacpi_hotplug 21 root 20 0 0 0 0 S 0 0.0 0:00.00 kseriod 22 root 0 -20 0 0 0 S 0 0.0 0:00.00 md 23 root 0 -20 0 0 0 S 0 0.0 0:00.00 kondemand 24 root 20 0 0 0 0 S 0 0.0 0:00.00 khungtaskd 25 root 20 0 0 0 0 S 0 0.0 0:00.63 kworker/1:1 26 root 20 0 0 0 0 S 0 0.0 0:00.04 kswapd0 27 root 25 5 0 0 0 S 0 0.0 0:00.00 ksmd 28 root 20 0 0 0 0 S 0 0.0 0:00.01 fsnotify_mark -------------- or even higher load.... var/log/messages is constantly being written and growing.... help! ;) (just a test system, no worries.....) localhost:~ # uname -a Linux localhost 2.6.37-22-default #1 SMP 2011-02-09 14:44:19 +0100 i686 athlon i386 GNU/Linux running on virtualbox 4.0.2 on a windows xp machine. localhost:~ # rpm -aq | grep -i kern kernel-default-2.6.37-22.1.i586 localhost:~ # rpm -aq | grep -i virtu virtuoso-drivers-6.1.2-3.1.i586 soprano-backend-virtuoso-2.5.63-4.2.i586 virtualbox-guest-x11-4.0.2-6.1.i586 virtualbox-guest-tools-4.0.2-6.1.i586 virtuoso-server-6.1.2-3.1.i586 virtualbox-guest-kmp-default-4.0.2_k2.6.37.0_20-6.1.i586 -------------- thanks. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c1 Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kasievers@novell.com Component|Kernel |Basesystem AssignedTo|kernel-maintainers@forge.pr |bnc-team-screening@forge.pr |ovo.novell.com |ovo.novell.com --- Comment #1 from Jiri Slaby <jslaby@novell.com> 2011-02-14 09:36:53 UTC --- It looks like systemd is trying to log empty messages forever... -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c3 --- Comment #3 from Kay Sievers <kasievers@novell.com> 2011-02-16 13:42:37 UTC --- If you add "quiet" to the commandline, it goes away? There is a possibly related issue here: https://bugzilla.novell.com/show_bug.cgi?id=672450 -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c4 --- Comment #4 from andreas bittner <abittner@stud.fh-heilbronn.de> 2011-02-16 15:56:34 UTC --- commandline where? on the kernel bootparameter (during grub menu screen) ? those messages get dumped into /var/log/messages on my box.... not onto the real screen or terminal like on that other bug. so actually its not really annoying ;) except for the excessive cpu load and the systems harddisk getting filled with gigabytes of useless trash in /var/log/messages.... so still severe bug in my opinion. maybe its some bug in the recent kernel update packages that arrived in factory during the last week or whenever that was. cheers. -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c5 --- Comment #5 from Kay Sievers <kasievers@novell.com> 2011-02-17 17:36:34 UTC --- Yeah, the kernel commandline in the bootloader. Adding 'quiet' here *could* make all that go away. -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c6 --- Comment #6 from andreas bittner <abittner@stud.fh-heilbronn.de> 2011-02-18 10:17:11 UTC --- dont seem to be experiencing this bug any more at the moment. yesterday or so there were a huge number of updates in the factory repo via zypper ref and zypper up. also some kernel and other ones. maybe the newer kernel package fixed the stuff. i dont have any excess logging by the kernel atm any more. localhost:~ # rpm -aq | grep -i kern kernel-default-2.6.37-22.2.i586 localhost:~ # rpm -aq | grep -i log shared-desktop-ontologies-0.5-1.2.noarch dialog-1.1-41.3.i586 libqdialogsolver1-1.3.0-7.31.i586 syslog-ng-3.2.2-4.1.i586 libevtlog0-0.2.9-5.3.i586 login-4.0-5.2.i586 klogd-1.4.1-729.2.i586 kdialog-4.6.0-4.2.i586 logrotate-3.7.9-4.3.i586 localhost:~ # uname -a Linux localhost 2.6.37-22-default #1 SMP 2011-02-09 14:44:19 +0100 i686 athlon i386 GNU/Linux localhost:~ # cat /etc/SuSE-release openSUSE 11.4 RC 1 (i586) VERSION = 11.4 CODENAME = Celadon localhost:~ # cat /etc/SuSE-brand openSUSE VERSION = 11.4 ---------------- btw, if i remember properly, there was some changes in glibc or so from i686 down to i585. and some days earlier the other way around or so. regards. -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c7 Kay Sievers <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #7 from Kay Sievers <kasievers@novell.com> 2011-02-18 10:25:17 UTC --- Sounds good. Thanks. -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c8 andreas bittner <abittner@stud.fh-heilbronn.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #8 from andreas bittner <abittner@stud.fh-heilbronn.de> 2011-02-24 11:42:59 UTC --- guess what..... im on my rc1 box (virtualbox) again and did a zypper ref and zypper up today.... right now its all the mess as before: -------- [ 3420.802479] kernel[3102]: [ 3420.785069] kernel[3102]: [ 3420.765202] kernel[3102]: [ 3420.747686] kernel[3102]: [ 3420.729903] kernel[3102]: [ 3420.710615] kernel[3102]: [ 3420.692342] kernel[3102]: [ 3420.673129] kernel[3102]: [ 3420.654749] kernel[3102]: [ 3420.623882] kernel[3102]: [ 3420.606752] kernel[3102]: [ 3420.588094] kernel[3102]: [ 3420.569553] kernel[3102]: [ 3420.551494] kernel[3102]: [ 3420.533420] kernel[3102]: [ 3420.514676] kernel[3102]: [ 3420.495140] kernel[3102]: [ 3420.476340] kernel[3102]: [ 3420.457959] kernel[3102]: [ 3420.438736] kernel[3102]: [ 3420.418509] kernel[3102]: [ 3420.396007] kernel[3102]: [ 3420.376768] kernel[3102]: [ 3420.358521] kernel[3102]: [ 3420.339 Feb 24 11:35:44 localhost kernel: 049] kernel[3102]: [ 3420.319 Feb 24 11:35:44 localhost kernel: [ 3421.046756] kernel[3102]: 107] kernel[3102]: 969] kerne Feb 24 11:35:44 localhost kernel: [ 3421.046762] kernel[3102]: [ 3421.014245] kernel[3102]: l[3102]: [ 3419.642 Feb 24 11:35:44 localhost kernel: [ 3421.046779] kernel[3102]: [ 3421.014261] kernel[3102]: [ 3420.990278] kernel[3102]: [ 3420.971324] kernel[3102]: [ 3420.943446] kernel[3102]: [ 3420.925898] kernel[3102]: [ 3420.903720] kernel[3102]: [ 3420.861449] kernel[3102]: [ 3420.843939] kernel[3102]: [ 3420.825737] kernel[3102]: [ 3420.802513] kernel[3102]: [ 3420.785095] kernel[3102]: [ 3420.765202] kernel[3102]: [ 3420.747686] kernel[3102]: [ 3420.729926] kernel[3102]: [ 3420.710641] kernel[3102]: [ 3420.692365] kernel[3102]: [ 3420.673150] kernel[3102]: [ 3420.654758] kernel[3102]: [ 3420.623910] kernel[3102]: [ 3420.606771] kernel[3102]: [ 3420.588112] kernel[3102]: [ 3420.569570] kernel[3102]: [ 3420.551510] kernel[3102]: [ 3420.533435] kernel[3102]: [ 3420.514690] kernel[3102]: [ 3420.495153] kernel[3102]: [ 3420.476353] kernel[3102]: [ 3420.457970] kernel[3102]: [ 3420.438736] kernel[3102]: [ 3420.418519] kernel[3102]: [ 3420.396016] kernel[3102]: [ 3420.376777] kernel[3102]: [ 3420.358533] kernel[3102]: [ 3420.339 Feb 24 11:35:44 localhost kernel: 055] kernel[3102]: [ 3420.319 Feb 24 11:35:44 localhost kernel: [ 3421.046798] kernel[3102]: 113] kernel[3102]: [ 3420.300 Feb 24 11:35:44 localhost kernel: [ 3421.046804] kernel[3102]: [ 3421.014280] kernel[3102]: 435] kernel[3102]: 308] kerne Feb 24 11:35:44 localhost kernel: [ 3421.046810] kernel[3102]: [ 3421.014286] kernel[3102]: [ 3420.990301] kernel[3102]: l[3102]: [ 3419.62 -------------------- zypper was doing the following when this madness started all over again: ----------- Installing: libkonq5-4.6.0-8.1 [done] Installing: libkipi8-4.6.0-9.1 [done] Installing: libkexiv2-9-4.6.0-9.1 [done] Installing: libkdcraw9-4.6.0-9.1 [done] Installing: libgio-2_0-0-2.28.0-6.1 [done] Installing: libblkid1-2.19-6.1 [done] Installing: libakonadi4-4.6.0-7.1 [done] Installing: kernel-default-2.6.37.1-2.1 [done] Additional rpm output: Kernel image: /boot/vmlinuz-2.6.37.1-2-default Initrd image: /boot/initrd-2.6.37.1-2-default Root device: /dev/disk/by-id/ata-VBOX_HARDDISK_VBae6b2a64-26e5f4a8-part2 (/dev/sda2) (mounted on / as ext3) Resume device: /dev/disk/by-id/ata-VBOX_HARDDISK_VBae6b2a64-26e5f4a8-part1 (/dev/sda1) modprobe: Module piix not found. WARNING: no dependencies for kernel module 'piix' found. modprobe: Module ide_pci_generic not found. WARNING: no dependencies for kernel module 'ide_pci_generic' found. Kernel Modules: hwmon thermal_sys thermal libata ata_piix ata_generic processor fan edd rtc-lib rtc-core rtc-cmos pata_pdc202xx_old pata_legacy pata_acpi sata_svw pata_sis sata_sis pata_atp867x pata_efar pata_sl82c105 pata_ninja32 pata_atiixp sata_qstor pata_sil680 sata_sx4 sata_mv pata_mpiix libahci sata_promise ahci_platform pata_hpt366 pata_cs5520 pata_marvell pata_serverworks pcmcia_core pcmcia pata_pcmcia pata_radisys pata_triflex pata_rdc pata_ns87415 pdc_adma pata_cmd64x pata_cs5530 pata_artop pata_hpt3x2n pata_ns87410 pata_opti sata_via pata_piccolo pata_sc1200 sata_uli pata_hpt37x pata_isapnp pata_it821x pata_cs5535 pata_cypress pata_amd sata_sil sata_nv pata_sch pata_netcell pata_ali ahci pata_optidma sata_vsc pata_cs5536 pata_it8213 pata_jmicron sata_sil24 pata_hpt3x3 pata_via pata_pdc2027x pata_oldpiix pata_rz1000 pata_qdi sata_inic162x pata_cmd640 usbcore ohci-hcd ehci-hcd uhci-hcd hid usbhid Features: block usb resume.userspace resume.kernel Bootsplash: openSUSE (1024x768) 42310 blocks .... ------------- my rc1 box was on: localhost:/var/log # uname -a Linux localhost 2.6.37-22-default #1 SMP 2011-02-09 14:44:19 +0100 i686 athlon i386 GNU/Linux and zypper installed that kernel above. is that correct? the klogd and everything went lunatic again and created a gigabyte of useless loggage again. :( havent rebooted yet as zypper is still installing packages (went past the kernel stuff...) localhost:/var/log # cat /etc/SuSE-release openSUSE 11.4 RC 1 (i586) VERSION = 11.4 CODENAME = Celadon its still on rc1 apparently, although new aaa_base and other stuff seems to have gotton installed already. wasnt there an rc2 announcement just some hours ago actually? i received some mail from the -testing list or so. anyways. --------- so klogd and his friends are all again going crazy ever since zypper went to work on that kernel package..... localhost:/var/log # top top - 11:41:43 up 1:03, 4 users, load average: 3.22, 3.24, 3.17 Tasks: 119 total, 3 running, 116 sleeping, 0 stopped, 0 zombie Cpu(s): 16.0%us, 41.0%sy, 0.0%ni, 10.1%id, 32.1%wa, 0.0%hi, 0.7%si, 0.0%st Mem: 1025540k total, 998536k used, 27004k free, 95420k buffers Swap: 1550236k total, 620k used, 1549616k free, 689336k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 3102 root 20 0 2164 676 352 R 83 0.1 45:04.83 klogd 4712 root 20 0 2208 568 464 R 64 0.1 33:29.39 systemd-kmsg-sy 869 root 20 0 88052 45m 3196 S 6 4.6 0:34.85 Xorg 4214 root 20 0 141m 22m 15m S 3 2.3 0:13.79 konsole 13844 root 20 0 14452 6692 1996 D 2 0.7 0:00.22 rpm 4174 root 20 0 277m 21m 13m S 1 2.1 0:50.53 knotify4 4148 root 20 0 144m 24m 18m S 1 2.5 0:06.79 kwin 1 root 20 0 4920 3020 1712 S 0 0.3 0:02.12 systemd 2 root 20 0 0 0 0 S 0 0.0 0:00.00 kthreadd 3 root 20 0 0 0 0 S 0 0.0 0:01.40 ksoftirqd/0 5 root 20 0 0 0 0 S 0 0.0 0:00.01 kworker/u:0 --------------- :( reopen anyone? -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c9 Rainer Hurtado Navarro <publio.escipion.el.africano@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |publio.escipion.el.africano | |@gmail.com Version|Factory |RC 2 --- Comment #9 from Rainer Hurtado Navarro <publio.escipion.el.africano@gmail.com> 2011-03-07 16:32:28 UTC --- RC 2 complains at boot (the very first line, that is not collected into /var/log/messages): "FATAL: Module piix not found." Every time I close the laptop, instead of locking my session, or what-ever it be done according to power saving rules (KDE) in that case, the SO hangs. Are related? I do not require, nor use any foreign module (for video, wireless, etc.), but built in in kernel are enough. So, it is not a problem with proprietary drivers I had installed. -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c10 Kay Sievers <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |abittner@stud.fh-heilbronn. | |de --- Comment #10 from Kay Sievers <kasievers@novell.com> 2011-03-15 13:23:33 UTC --- If you still have the problem, please try the systemd version from Base:System: http://download.opensuse.org/repositories/Base:/System/openSUSE_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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c11 Kay Sievers <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby@novell.com --- Comment #11 from Kay Sievers <kasievers@novell.com> 2011-03-19 18:03:42 UTC --- *** Bug 681069 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=681069 -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c12 Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|abittner@stud.fh-heilbronn. | |de | --- Comment #12 from Jiri Slaby <jslaby@novell.com> 2011-03-19 18:37:10 UTC --- (In reply to comment #11)
*** Bug 681069 has been marked as a duplicate of this bug. ***
Answering the question from there:
Please test the 11.4 systemd version from Base:System.
The bug is still there. -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c13 Kay Sievers <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |jslaby@novell.com --- Comment #13 from Kay Sievers <kasievers@novell.com> 2011-03-19 18:46:08 UTC --- What syslog are you using? -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c14 Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|jslaby@novell.com | --- Comment #14 from Jiri Slaby <jslaby@novell.com> 2011-03-19 18:47:03 UTC --- (In reply to comment #13)
What syslog are you using?
syslog-ng-3.2.2-5.1.x86_64 -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c15 --- Comment #15 from Kay Sievers <kasievers@novell.com> 2011-03-19 18:51:27 UTC --- mind trying rsyslog? that's what we recommend to use for systemd, and work with the rsyslog guy together upstream on the proper integration. -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c16 --- Comment #16 from Jiri Slaby <jslaby@novell.com> 2011-03-19 19:07:42 UTC --- (In reply to comment #15)
mind trying rsyslog? that's what we recommend to use for systemd, and work with the rsyslog guy together upstream on the proper integration.
I've just played with that a bit. And syslog itself doesn't matter. It's klog which makes problem. So when I run klogd it does: stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2246, ...}) = 0 write(1, "<4>Mar 19 19:59:02 kernel: [ 151"..., 1024) = 1024 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2246, ...}) = 0 write(1, "<6>Mar 19 19:59:02 kernel: 682] "..., 57) = 57 # ll /proc/1926/fd/1 lrwx------ 1 root root 64 19. bře 19.55 /proc/1926/fd/1 -> socket:[242641] /lib/systemd/systemd-kmsg-syslogd then does: recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"<4>Mar 19 19:59:40 kernel: [ 155"..., 2048}], msg_controllen=32, {cmsg_len=28, cmsg_level=SOL_SOCKET, cmsg_type=SCM_CREDENTIALS{pid=1926, uid=0, gid=0}}, msg_flags=0}, MSG_DONTWAIT) = 1024 writev(6, [{"<4>", 3}, {"kernel", 6}, {"[1926]: ", 8}, {"[ 1550.984327] kernel[1926]: [ 1"..., 996}, {"\n", 1}], 5) = 1014 in loop. # ll /proc/312/fd/[36] lrwx------ 1 root root 64 19. bře 19.52 /proc/312/fd/3 -> socket:[3412] l-wx------ 1 root root 64 19. bře 19.52 /proc/312/fd/6 -> /dev/kmsg where socket 3412 is: lrwx------ 1 root root 64 19. bře 20.01 /proc/1/fd/26 -> socket:[3412] Socket 242641 (from klogd above): socket(PF_FILE, SOCK_DGRAM, 0) = 4 fcntl(4, F_SETFD, FD_CLOEXEC) = 0 connect(4, {sa_family=AF_FILE, path="/dev/log"}, 10) = 0 Should I try rsyslog still? -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c17 --- Comment #17 from Kay Sievers <kasievers@novell.com> 2011-03-19 19:12:38 UTC --- Yeah, please. Klogd is something from the past and today natively integrated in modern syslogs. -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c18 --- Comment #18 from Jiri Slaby <jslaby@novell.com> 2011-03-19 19:17:25 UTC --- (In reply to comment #17)
Yeah, please. Klogd is something from the past and today natively integrated in modern syslogs.
Ok, done. As rsyslog doesn't run klogd, I don't see the problem anymore. Thanks. -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c19 Bruno Friedmann <bruno@ioda-net.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bruno@ioda-net.ch --- Comment #19 from Bruno Friedmann <bruno@ioda-net.ch> 2011-03-19 21:08:13 UTC --- Kay just a note if we need rsyslog for systemd, why webyast insist to have syslogd-ng ? Could you check with Yast/WebYast group to adjust the whole need and make a good safe selection. zypper rm syslog-ng syslog-ng webyast-base-ui webyast-base-ui-branding-default webyast-base-ui-testsuite webyast-base-ws webyast-base-ws-testsuite webyast-firewall-ui webyast-firewall-ui-testsuite webyast-firewall-ws webyast-firewall-ws-testsuite webyast-firstboot-ws webyast-firstboot-ws-testsuite webyast-kerberos-ui webyast-kerberos-ui-testsuite webyast-kerberos-ws webyast-kerberos-ws-testsuite webyast-language-ui webyast-language-ui-testsuite webyast-language-ws webyast-language-ws-testsuite webyast-ldap-ui webyast-ldap-ui-testsuite webyast-ldap-ws webyast-ldap-ws-testsuite webyast-licenses-ui webyast-licenses-ui-testsuite webyast-licenses-ws webyast-licenses-ws-testsuite webyast-mail-ui webyast-mail-ui-testsuite webyast-mail-ws webyast-mail-ws-testsuite webyast-network-ui webyast-network-ui-testsuite webyast-network-ws webyast-network-ws-testsuite webyast-ntp-ws webyast-ntp-ws-testsuite webyast-permissions-ui webyast-permissions-ui-testsuite webyast-reboot-ui webyast-reboot-ui-testsuite webyast-root-user-ui webyast-root-user-ui-testsuite webyast-root-user-ws webyast-services-ui webyast-services-ui-testsuite webyast-services-ws webyast-services-ws-testsuite webyast-software-ui webyast-software-ui-testsuite webyast-software-ws webyast-software-ws-testsuite webyast-status-ui webyast-status-ui-testsuite webyast-status-ws webyast-status-ws-testsuite webyast-time-ui webyast-time-ui-testsuite webyast-time-ws webyast-time-ws-testsuite webyast-users-ui webyast-users-ui-testsuite webyast-users-ws webyast-users-ws-testsuite -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c20 Kay Sievers <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mt@novell.com AssignedTo|kasievers@novell.com |werner@novell.com Summary|klogd / systemd-kmsg-sy: |klogd+systemd: starting |kernel messages all over |klogd on systemd systems |the place (not stopping |creates loop, need to make |ever, cpu load) |sure it never runs there --- Comment #20 from Kay Sievers <kasievers@novell.com> 2011-03-22 14:34:55 UTC --- klogd must never run on a systemd systemd, it creates a loop in the kernel log buffer logic with the systemd's early syslog bridge. The klogd functionality needs to be integrated into the syslog daemon, not run as its own service. systemd does not support other syslog implementations. Would be nice if we can get rid of the RPM dependencies, so that it is possible to deinstall, or not pull-in klogd by default. Passing to Werner. -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c21 Dr. Werner Fink <werner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |kasievers@novell.com --- Comment #21 from Dr. Werner Fink <werner@novell.com> 2011-03-22 14:51:21 UTC --- Kay: We have 3 syslog daemons and one klogd feeding all three. Why systemd does not support other syslog implementations? I do not see any technical reason for this. Beside this there is already the possiblity not to use the klogd as rsyslogd is also able to use its own klog module. -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c22 Kay Sievers <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|kasievers@novell.com | --- Comment #22 from Kay Sievers <kasievers@novell.com> 2011-03-22 15:07:58 UTC --- (In reply to comment #21)
Kay: We have 3 syslog daemons and one klogd feeding all three.
klogd seems not to run when rsyslog is used, at least not with the same problem. syslog-ng seems to cause the loop, syslog I don't know.
Why systemd does not support other syslog implementations? I do not see any technical reason for this.
Systemd has it's own /dev/log early-syslog-bridge implementation. Any userspace program can just use glibc's syslog() during very early bootup and will write to the kernel log buffer. As soon as the real syslog starts, it takes over the open /dev/log fd from systemd for new messages and reads the kernel log buffer. Klogd feeds the kernels log buffer to /dev/log I guess, and creates a loop that way, reading it's own messages again. There is nothing really in systemd that is non-supporting, but without knowing the details, the thing klogs does doesn't seem to fit into that.
Beside this there is already the possiblity not to use the klogd as rsyslogd is also able to use its own klog module.
That seems to be the case. And systemd systems recommend the use of rsyslog because it is properly integrated from rsyslog upstream. When people switch from syslog-ng to rsyslog, all seems to work, without knowing what really makes the difference between the both, the daemon itself, the configuration, or the init script logic. The long-term plan is to get rid of the init script and have native service files shipped with the upstream syslog tarball, instead of the current magic. Klogd is not in that picture. -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c23 Dr. Werner Fink <werner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |kasievers@novell.com --- Comment #23 from Dr. Werner Fink <werner@novell.com> 2011-03-22 15:42:06 UTC --- (In reply to comment #22)
Systemd has it's own /dev/log early-syslog-bridge implementation. Any userspace program can just use glibc's syslog() during very early bootup and will write to the kernel log buffer. As soon as the real syslog starts, it takes over the open /dev/log fd from systemd for new messages and reads the kernel log buffer.
In other words: systemd encroachs on the kernel message ring buffer by redirecting the user space messages from /dev/log to /dev/kmsg? Why does systemd not use its _own_ ring buffer? Beside this the klogd is started _after_ syslog-ng or syslogd using openlog() and syslog(). At this point /dev/log should belong to syslog-ng or syslogd, shouldn't it? The klogd executed in once mode does not use openlog() nor syslog() and is used in /etc/init.d/boot.klog to write out /var/log/boot.msg -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c24 Kay Sievers <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|kasievers@novell.com | --- Comment #24 from Kay Sievers <kasievers@novell.com> 2011-03-22 16:35:28 UTC --- (In reply to comment #23)
(In reply to comment #22)
In other words: systemd encroachs on the kernel message ring buffer by redirecting the user space messages from /dev/log to /dev/kmsg? Why does systemd not use its _own_ ring buffer?
Because early boot is mostly hardware system/subsystem init, and messages from early boot tools _should_ mix with the kernel messages during that time to be reliably sorted and kernel time-stamped. Today there are lots of kernel components managed from userspace, and they should share the same log buffer during early bootup. Also on embedded-like systems the kernel ring-buffer connected to /dev/log is all what you ever want for "syslog".
Beside this the klogd is started _after_ syslog-ng or syslogd using openlog() and syslog(). At this point /dev/log should belong to syslog-ng or syslogd, shouldn't it?
Yeah, it sounds like it. Not sure what's the problem with syslog-ng here. The systemd bridge maybe needs to be stopped when syslog runs. But as said, I don't know the details, only that rsyslog seems to work fine.
The klogd executed in once mode does not use openlog() nor syslog() and is used in /etc/init.d/boot.klog to write out /var/log/boot.msg
Maybe it's syslog-ng itself that calls klogd somehow? It might be, that this problem can not be solved properly for syslog-ng without using native service files and socket activation. Proper socket passing needs native service files and does not work with compat sysv services. Syslog is special regarding compat handling, because systemd itself dependends on a specific behavior. -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c25 --- Comment #25 from Dr. Werner Fink <werner@novell.com> 2011-03-22 16:45:53 UTC --- (In reply to comment #24) AFAICS from initial comment #0 the syslog-ng had crashed remaining the unix domain socket for logging at systemd. The question is: how can be determined to which process the socket belongs to ... systemd or one of the system loggers. -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c26 --- Comment #26 from Kay Sievers <kasievers@novell.com> 2011-03-22 17:07:54 UTC --- (In reply to comment #25)
The question is: how can be determined to which process the socket belongs to ... systemd or one of the system loggers.
I don't think any tool should try to be smart here about the systemd bridge. The socket will always be owned by systemd and only possibly inherited from started services, which might be none, one, or several. A syslog without socket activation will probably just delete /dev/log and create its own. But we can't really support that longer-term. I thought you might know just what's the difference in the syslogs and the klogd message loop. It might not be worth investigating how the current syslog init magic and syslog-ng fails, and we better just go directly for native systemd service files, and make them working in a way systemd expects them to work. If there is no simple fix for the current syslog logic, feel free to assign it back to me, I'll probably not work on it anytime soon, but I can keep track of it. -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c27 --- Comment #27 from Dr. Werner Fink <werner@novell.com> 2011-03-22 17:21:20 UTC --- IMHO even with native systemd service files for klogd, syslogd or syslog-ng we will see a loop if e.g. syslog-ng fails. This because if syslog-ng fails systemd does forward all messages from /dev/log to /dev/kmsg. In other words, klogd reads with klogctl(2) system call the kernels messages and after parsing them, forwards them to the system logger via syslog() ... now systemd as the syslog-ng has not activated the system logging socket due to an early crash, systemd writes those messages back to the kernels printk ring buffer at /dev/kmsg. -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c28 --- Comment #28 from Kay Sievers <kasievers@novell.com> 2011-03-22 17:34:47 UTC --- But we would run klogd in the post of syslog-ng.service so klogd would only be started if we can start syslog-ng properly? -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c29 --- Comment #29 from Dr. Werner Fink <werner@novell.com> 2011-03-22 17:55:13 UTC --- Yes this can be done with native systemd service files as well as with old init scripts as well. The only problem for the old system v init or better startproc(8)/chekproc(8) is to distinguish an exit status with success from a crashed daemon its selfs later on. I guess that if syslog-ng crashes even with systemd we may run into this loop ... is this correct? Or does systemd ignore syslog messages after syslog-ng has activated the socket but crashed anyway? AFAIK this should not happen after sd_notify(0, "READY=1"), shouldn't it? Is there a way to use e.g. sd_booted() for klogd as well as for syslog-ng or syslogd and wait on the OK from 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c30 --- Comment #30 from Kay Sievers <kasievers@novell.com> 2011-03-22 18:10:36 UTC --- We need socket activation for proper race-free fd hand-over, which can only be done with native service files. I guess it's not really worth the effort to make the compat sysv syslog-ng stuff work with systemd, when it can not provide a full solution in the end anyway. I naively thought there might be a simple fix for the init script. :) The problem with systemd and native service files should be a lot simpler. syslog-ng.service is supposed to stop the systemd kmsg bridge in pre, and start klogd if needed in post. That should prevent the loop without any patched klogd, or crashing syslog-ng. Here is rsyslog's upstream systemd service file which kills the bridge: http://git.adiscon.com/?p=rsyslog.git;a=blob;f=rsyslog.service.in;hb=HEAD -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c31 --- Comment #31 from Marius Tomaschewski <mt@novell.com> 2011-03-22 20:16:06 UTC --- (In reply to comment #22)
(In reply to comment #21)
Kay: We have 3 syslog daemons and one klogd feeding all three.
klogd seems not to run when rsyslog is used, at least not with the same problem.
rsyslog provides a klogd as module -- /etc/rsyslog.conf: $ModLoad imklog.so # kernel logging (may be also provided by /sbin/klogd), # see also http://www.rsyslog.com/doc-imklog.html. $klogConsoleLogLevel 1 # set log level 1 (same as in /etc/sysconfig/syslog). In syslogd case, the external /sbin/klogd is started. syslog-ng is also able /proc/kmsg itself, but traditionally we start /sbin/klogd here as well. (In reply to comment #30)
We need socket activation for proper race-free fd hand-over, which can only be done with native service files.
All syslog daemons are currently using socket activation -- just without syslog.service file.
Here is rsyslog's upstream systemd service file which kills the bridge: http://git.adiscon.com/?p=rsyslog.git;a=blob;f=rsyslog.service.in;hb=HEAD
OK, this means we just need to provide a syslog.service file killing the bridge -- something like this: [Unit] Description=System Logging Service [Service] Type=forking ExecStartPre=/bin/systemctl stop systemd-kmsg-syslogd.service ExecStopPost=/bin/systemctl start systemd-kmsg-syslogd.service ExecStart=/etc/init.d/syslog start ExecReload=/etc/init.d/syslog reload ExecStop=/etc/init.d/syslog stop Sockets=syslog.socket [Install] WantedBy=multi-user.target Do we need some another dependencies, ...? -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c32 --- Comment #32 from Marius Tomaschewski <mt@novell.com> 2011-03-22 20:37:20 UTC --- (In reply to comment #26)
It might not be worth investigating how the current syslog init magic and syslog-ng fails, and we better just go directly for native systemd service files, and make them working in a way systemd expects them to work.
We have to investigate. It is IMO not an option to drop syslog-ng/syslogd. The socket activation in all 3 syslog daemons on 11.4 is basically same. I didn't tested it until now and also not with syslogd yet, but it seems that the external klogd makes the difference. In case of rsyslog (via syslog.service alias init script), systemd seems to detect it and stops systemd-kmsg-syslogd.service (it is stopped on my fresh 11.4 installation here without any changes). -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c33 --- Comment #33 from Kay Sievers <kasievers@novell.com> 2011-03-22 20:41:19 UTC --- (In reply to comment #31)
All syslog daemons are currently using socket activation -- just without syslog.service file.
That was a bug in an earlier systemd version. Socket activation is only available for natively started services, not for sysv compat services.
[Service] ExecStopPost=/bin/systemctl start systemd-kmsg-syslogd.service
It never needs to be started, systemd takes care of it, if syslog goes away and no syslog service startup transaction is pending.
ExecStart=/etc/init.d/syslog start
Never use any sysv init scripts in systemd service files. It will just deadlock. Thei stuff is really not meant to be used that way. We should stick to the upstream way of integrating this.
Do we need some another dependencies, ...?
We need native service files for all syslog implementations with the real name of the package, and leave the multiplexed sysv "syslog" script behind us. Enabling or disabling will be managed by systemd symlinks not by sysconfig magic. -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c34 --- Comment #34 from Kay Sievers <kasievers@novell.com> 2011-03-22 20:45:20 UTC --- (In reply to comment #32)
We have to investigate. It is IMO not an option to drop syslog-ng/syslogd. The socket activation in all 3 syslog daemons on 11.4 is basically same.
They all need to get native service files. There is no way around it in the long run.
I didn't tested it until now and also not with syslogd yet, but it seems that the external klogd makes the difference.
Yeah, *looks* like the issue.
In case of rsyslog (via syslog.service alias init script), systemd seems to detect it and stops systemd-kmsg-syslogd.service (it is stopped on my fresh 11.4 installation here without any changes).
It has had a timeout in the 11.4 release. The recent version does not stop itself anymore, it runs forever. We don't really support systemd on 11.4, development happens in Factory. We will probably just update the 11.4 systemd version when the stuff has stabilized with the upcoming Fedora release. -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c35 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #35 from Dr. Werner Fink <werner@suse.com> 2011-09-02 16:34:09 UTC --- Should be fixed with latest systemd unit service files for syslogd/klogd that menas klogd is bind to syslogd which should stop klogd if syslogd dies -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c36 --- Comment #36 from Patrick Smart <novell@lietar.eu> 2011-09-18 23:36:02 UTC --- Seeing Bug 681069 occur in my recently updated 11.4 system. What update caused it? -- 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=671525 https://bugzilla.novell.com/show_bug.cgi?id=671525#c37 --- Comment #37 from Dr. Werner Fink <werner@suse.com> 2011-09-19 07:49:19 UTC --- (In reply to comment #36) IMHO you should not mix systemd with 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.
participants (1)
-
bugzilla_noreply＠novell.com