Re: [systemd-devel] how make systemd NOT to clutter dmesg?
On 27/02/17 16:43, Reindl Harald wrote: Am 27.02.2017 um 17:18 schrieb lejeczek: yes, correct, something did, in /etc/grub2.cfg systemd.log_level=debug systemd.log_target=kmsg even tough nothing of above is to be found in /etc/default/grub What I found and messaged Centos list about, long agao, but it might be interesting to anybody who.. uses Oracle's kernel-uek which a long time ago I'm pretty sure put: MAKEDEBUG=yes into /etc/sysconfig/kernel but what I've had commented out for long long time, and many new kernels installed since then. I'll get rid of UEK for peace of mind's sake it has *nothing* to do with UEK one of the last CentOS updates here did the same *only* on one machine however, next time when you report issues start by mentioning you operating system, the patch-level and version of your operating system and uncutted loglines which you are talking about in the initial post with that informations i would have been able to point you directly to /etc/sysconfig/kernel - you can't assume that anybody is guessing what you are talking about when you hold back any informations gee, sorry, maybe I made it vague? I just said it was NOT sysconfig/kernel but /etc/grub2.cfg I mentioned sysconfig/kernel and that "I've had commented out for long long time" and UEK because I believed UEK put it MAKEDEBUG=yes and tampered with /etc/grub2.cfg ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] how make systemd NOT to clutter dmesg?
Am 27.02.2017 um 17:18 schrieb lejeczek: yes, correct, something did, in /etc/grub2.cfg systemd.log_level=debug systemd.log_target=kmsg even tough nothing of above is to be found in /etc/default/grub What I found and messaged Centos list about, long agao, but it might be interesting to anybody who.. uses Oracle's kernel-uek which a long time ago I'm pretty sure put: MAKEDEBUG=yes into /etc/sysconfig/kernel but what I've had commented out for long long time, and many new kernels installed since then. I'll get rid of UEK for peace of mind's sake it has *nothing* to do with UEK one of the last CentOS updates here did the same *only* on one machine however, next time when you report issues start by mentioning you operating system, the patch-level and version of your operating system and uncutted loglines which you are talking about in the initial post with that informations i would have been able to point you directly to /etc/sysconfig/kernel - you can't assume that anybody is guessing what you are talking about when you hold back any informations ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] how make systemd NOT to clutter dmesg?
On 27/02/17 12:04, Lennart Poettering wrote: On Mon, 27.02.17 11:03, lejeczek (pelj...@yahoo.co.uk) wrote: On 27/02/17 10:10, Reindl Harald wrote: Am 27.02.2017 um 10:55 schrieb lejeczek: hi there I'm trying to solve problem which to you guys must be trivial, but it's a puzzle to me. I've searched the net & man pages but ... failed to find how/where systemd is told to put stuff like: Got message type... seriously - could you at least post *one* uncutted message I said, it seemed the whole lot went there.. does it not make it simpler? I did not want to clutter the mailing list, here: [67142.383939] systemd[1]: Got notification message for unit httpd.service [67142.383956] systemd[1]: httpd.service: Got notification message from PID 7722 (READY=1, STATUS=Total requests: 0; Current requests/sec: 0; Current traffic: 0 B/sec) Seems something turned on debug logging for you. There are multiple ways how you might have turned it on. systemd.log_level=debug on the kernel cmdline (just "debug" works too). There's also a config option in system.conf. You can even turn it off and on dynamically with "systemd-analyze set-log-level"... How you turned it on I have no idea, but note that systemd will never turn debug logging on on its own, so it's clearly your admin (or some tool he used) on your system that is at fault. Lennart yes, correct, something did, in /etc/grub2.cfg systemd.log_level=debug systemd.log_target=kmsg even tough nothing of above is to be found in /etc/default/grub What I found and messaged Centos list about, long agao, but it might be interesting to anybody who.. uses Oracle's kernel-uek which a long time ago I'm pretty sure put: MAKEDEBUG=yes into /etc/sysconfig/kernel but what I've had commented out for long long time, and many new kernels installed since then. I'll get rid of UEK for peace of mind's sake. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] how make systemd NOT to clutter dmesg?
On Mon, 27.02.17 11:03, lejeczek (pelj...@yahoo.co.uk) wrote: > > > On 27/02/17 10:10, Reindl Harald wrote: > > > > > > Am 27.02.2017 um 10:55 schrieb lejeczek: > > > hi there > > > > > > I'm trying to solve problem which to you guys must be trivial, but > > > it's > > > a puzzle to me. > > > I've searched the net & man pages but ... failed to find how/where > > > systemd is told to put stuff like: > > > > > > Got message type... > > > > seriously - could you at least post *one* uncutted message > > I said, it seemed the whole lot went there.. does it not make it simpler? > I did not want to clutter the mailing list, here: > > > [67142.383939] systemd[1]: Got notification message for unit httpd.service > [67142.383956] systemd[1]: httpd.service: Got notification message from PID > 7722 (READY=1, STATUS=Total requests: 0; Current requests/sec: 0; Current > traffic: 0 B/sec) Seems something turned on debug logging for you. There are multiple ways how you might have turned it on. systemd.log_level=debug on the kernel cmdline (just "debug" works too). There's also a config option in system.conf. You can even turn it off and on dynamically with "systemd-analyze set-log-level"... How you turned it on I have no idea, but note that systemd will never turn debug logging on on its own, so it's clearly your admin (or some tool he used) on your system that is at fault. Lennart -- Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] how make systemd NOT to clutter dmesg?
On Mon, Feb 27, 2017 at 11:03:09AM +, lejeczek wrote: > > > On 27/02/17 10:10, Reindl Harald wrote: > > > > > > Am 27.02.2017 um 10:55 schrieb lejeczek: > > > hi there > > > > > > I'm trying to solve problem which to you guys must be trivial, but > > > it's > > > a puzzle to me. > > > I've searched the net & man pages but ... failed to find how/where > > > systemd is told to put stuff like: > > > > > > Got message type... > > > > seriously - could you at least post *one* uncutted message > > I said, it seemed the whole lot went there.. does it not make it simpler? > I did not want to clutter the mailing list, here: > > > [67142.383939] systemd[1]: Got notification message for unit httpd.service > [67142.383956] systemd[1]: httpd.service: Got notification message from PID > 7722 (READY=1, STATUS=Total requests: 0; Current requests/sec: 0; Current > traffic: 0 B/sec) > [67142.383963] systemd[1]: httpd.service: got READY=1 > [67142.383972] systemd[1]: httpd.service: got STATUS=Total requests: 0; > Current requests/sec: 0; Current traffic: 0 B/sec Looks like you have debugging enabled (increased log level). Get back to normal level and those message won't appear. -- Tomasz Torcz ,,If you try to upissue this patchset I shall be seeking xmpp: zdzich...@chrome.pl an IP-routable hand grenade.'' -- Andrew Morton (LKML) ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] how make systemd NOT to clutter dmesg?
On 27/02/17 10:10, Reindl Harald wrote: Am 27.02.2017 um 10:55 schrieb lejeczek: hi there I'm trying to solve problem which to you guys must be trivial, but it's a puzzle to me. I've searched the net & man pages but ... failed to find how/where systemd is told to put stuff like: Got message type... seriously - could you at least post *one* uncutted message I said, it seemed the whole lot went there.. does it not make it simpler? I did not want to clutter the mailing list, here: [67142.383939] systemd[1]: Got notification message for unit httpd.service [67142.383956] systemd[1]: httpd.service: Got notification message from PID 7722 (READY=1, STATUS=Total requests: 0; Current requests/sec: 0; Current traffic: 0 B/sec) [67142.383963] systemd[1]: httpd.service: got READY=1 [67142.383972] systemd[1]: httpd.service: got STATUS=Total requests: 0; Current requests/sec: 0; Current traffic: 0 B/sec [67142.384152] systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/unit/httpd_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=212382 reply_cookie=0 error=n/a [67142.384245] systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/unit/httpd_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=212383 reply_cookie=0 error=n/a [67142.384902] systemd-logind[4006]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/httpd_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=212382 reply_cookie=0 error=n/a [67142.385056] systemd-logind[4006]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/httpd_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=212383 reply_cookie=0 error=n/a [67144.428328] systemd[1]: Got notification message for unit php-fpm.service [67144.428343] systemd[1]: php-fpm.service: Got notification message from PID 4054 (READY=1, STATUS=Processes active: 0, idle: 5, Requests: 0, slow: 0, Traffic: 0req/sec) [67144.428349] systemd[1]: php-fpm.service: got READY=1 [67144.428359] systemd[1]: php-fpm.service: got STATUS=Processes active: 0, idle: 5, Requests: 0, slow: 0, Traffic: 0req/sec [67144.429383] systemd-logind[4006]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/php_2dfpm_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=212384 reply_cookie=0 error=n/a [67144.429520] systemd-logind[4006]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/php_2dfpm_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=212385 reply_cookie=0 error=n/a [67152.394629] systemd[1]: Got notification message for unit httpd.service [67152.394645] systemd[1]: httpd.service: Got notification message from PID 7722 (READY=1, STATUS=Total requests: 0; Current requests/sec: 0; Current traffic: 0 B/sec) [67152.394653] systemd[1]: httpd.service: got READY=1 [67152.394662] systemd[1]: httpd.service: got STATUS=Total requests: 0; Current requests/sec: 0; Current traffic: 0 B/sec [67152.394843] systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/unit/httpd_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=212386 reply_cookie=0 error=n/a [67152.394936] systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/unit/httpd_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=212387 reply_cookie=0 error=n/a [67152.396849] systemd-logind[4006]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/httpd_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=212386 reply_cookie=0 error=n/a [67152.396906] systemd-logind[4006]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/httpd_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=212387 reply_cookie=0 error=n/a [67152.397988] systemd[1]: Got notification message for unit systemd-logind.service [67152.397997] systemd[1]: systemd-logind.service: Got notification message from PID 4006 (WATCHDOG=1) [67152.398004] systemd[1]: systemd-logind.service: got WATCHDOG=1 [67152.398416] systemd[1]: Got notification message for unit systemd-machined.service [67153.547185] systemd-logind[4006]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/ctdb_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=212389 reply_cookie=0 error=n/a [67153.547451] systemd-logind[4006]: Got message type=signal sender=:1.0 destination=n/a
Re: [systemd-devel] how make systemd NOT to clutter dmesg?
Am 27.02.2017 um 12:11 schrieb Tomasz Torcz: On Mon, Feb 27, 2017 at 11:03:09AM +, lejeczek wrote: On 27/02/17 10:10, Reindl Harald wrote: Am 27.02.2017 um 10:55 schrieb lejeczek: hi there I'm trying to solve problem which to you guys must be trivial, but it's a puzzle to me. I've searched the net & man pages but ... failed to find how/where systemd is told to put stuff like: Got message type... seriously - could you at least post *one* uncutted message I said, it seemed the whole lot went there.. does it not make it simpler? I did not want to clutter the mailing list, here: [67142.383939] systemd[1]: Got notification message for unit httpd.service [67142.383956] systemd[1]: httpd.service: Got notification message from PID 7722 (READY=1, STATUS=Total requests: 0; Current requests/sec: 0; Current traffic: 0 B/sec) [67142.383963] systemd[1]: httpd.service: got READY=1 [67142.383972] systemd[1]: httpd.service: got STATUS=Total requests: 0; Current requests/sec: 0; Current traffic: 0 B/sec Looks like you have debugging enabled (increased log level). Get back to normal level and those message won't appear since the OP did not find it worth to provide any useful infos (distribution, systemd version...) about his environment maybe he was also affected by the last CentOS update which on one out of 5 machines set /etc/sysconfig/kernel to "MAKEDEBUG=yes" for no reason https://bugzilla.redhat.com/show_bug.cgi?id=1398811#c12 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] how make systemd NOT to clutter dmesg?
Am 27.02.2017 um 10:55 schrieb lejeczek: hi there I'm trying to solve problem which to you guys must be trivial, but it's a puzzle to me. I've searched the net & man pages but ... failed to find how/where systemd is told to put stuff like: Got message type... seriously - could you at least post *one* uncutted message ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
