[systemd-devel] journald disk space usage

[Bill Lipa]

Hello,

I have a Rails application that produces quite a bit of log output -
about 500MB per day, maybe 3-4 million lines.  Currently this is going
into a normal file with daily rotation.

I tried dumping this into journald via STDOUT so that I could see
everything in one place.  On a standard Google Cloud Platform
instance, this used about 10% extra CPU.  I was willing to live with
that, but more of a problem was the rapid increase in storage used for
the log.  It was growing at about 10x the rate as a flat file for the
2 hours I ran the experiment.  That is, after 2 hours, the usage
reported by 'sudo journalctl --disk-usage' was over 400MB, which is
not much less than I would normally see for an entire day's worth of
logging.

I am wondering if this is to be expected due to journald's extra
functionality and complexity, or does this seem incorrect?  I'm using
systemd 229 on Ubuntu 16.04.

Thank you,
Bill Lipa
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] How to have systemd --user instance share the same environment variables as the X server?

[Lennart Poettering]

On Sun, 26.02.17 21:10, Patrick Schleizer (patrick-mailingli...@whonix.org) 
wrote:

> Being on Debian stretch (Qubes). The display manager there does not yet
> get started by systemd --user.
> 
> I find it useful to convert /etc/xdg/autostart/app.desktop files to
> systemd --user unit files.
> 
> Therefore the environment variables have to be sorted out. On any Linux
> we would have to set at least DISPLAY as well as XAUTHORITY.
> 
> On Qubes however, we need a few more environment variables. We need also
> QT_X11_NO_MITSHM=1 and may need a few others ones.
> 
> Now, before I go through them manually and then have this break in
> future when more/different environment variables are needed...
> 
> Is there a way to have the systemd --user session share the same
> variables as the X server? Writing a parser for /etc/X11/Xsession.d/
> seems wrong. Am I missing some tool to do that?
> 
> Would I add something like this?
> 
> ExecStartPre=dbus-update-activation-environment --systemd --all

I am not sure I follow what you are trying to do, and I'd strongly
recommend to avoid pushing env vars from privileged code into
unprivileged code, but do note that there's "systemctl
import-environment" for importing env vars set for you.

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] Failed to get journal fields: Bad message

[Lennart Poettering]

On Mon, 27.02.17 08:29, Krzysztof Błaszkowski (k...@sysmikro.com.pl) wrote:

> > The journal file format is primarily an append-based format (though
> > some fields at the front are updated, to link the new additions
> > up). This makes it not too bad when it comes to disk corruptions, and
> > data up to the point of corruption should be readable pretty nicely
> > still.
> 
> well, the most interesting information is located beyond that point
> very often. 

Well, note that journald will stop writing to journal files as soon as
it notices a corruption of any kind, and will start new journal files,
leaving the old ones the way they are (thus not making them worse). We
also start new journal files in regular intervals, after a fixed time
interval or after a certain number of bytes wirtten, for whatever
comes first.

With that in place I am pretty sure our behaviour when it comes to
real-life corruptions these days isn't that bad: when something bad
happens, then we'll conserve in time what has been written already,
and if you destroy one file entirely what you loose will be bounded
both in time and in size.

But anyway, I get the impression that you don't like the journal out
of principle, and I am not sure I want to try to convince you
otherwise. My recommendation would be: if you don't like it don't use
it, set Storage=no in journald.conf and use whatever you like
better. You'll still benefit from journald and systemd collecting
all service stdout/stderr and early boot stuff for you, over plain
sysvinit/syslog, but it won't store anything on disk for you anymore.

> > Anyway, if you have a corrupted journal file and current journalctl
> > can't read it, then please file a bug, attach the journal file, and
> > we'll look into improving journalctl.
> > 
> 
> journalctl --verify
> PASS: /var/log/journal/52f04da61fa8108cd5f48bca586164a2/user-
> 1105.journal 
> PASS: /var/log/journal/52f04da61fa8108cd5f48bca586164a2/system@0005495e
> 2bb26863-aa72c6a8a7437123.journal~
> PASS: /var/log/journal/52f04da61fa8108cd5f48bca586164a2/system@0005455b
> e5e6181f-8616123458bd2b50.journal~
> PASS: /var/log/journal/52f04da61fa8108cd5f48bca586164a2/system@00054956
> b0c61ef7-6f0ef8bfd59ad5e8.journal~
> PASS: /var/log/journal/52f04da61fa8108cd5f48bca586164a2/user-1000@00054
> 95e2c558675-4af46c2d79464765.journal~
> 549f50: Invalid entry item (7/9 offset:
> 00
> 549f50: Invalid object contents: Bad
> message  
> File corruption detected at /var/log/journal/52f04da61fa8108cd5f48bca58
> 6164a2/system@0005495abfa1c9d8-cf2df0a23044.journal~:549f50 (of
> 8388608 bytes, 66%).
> FAIL: /var/log/journal/52f04da61fa8108cd5f48bca586164a2/system@0005495a
> bfa1c9d8-cf2df0a23044.journal~ (Bad message)
> PASS: /var/log/journal/52f04da61fa8108cd5f48bca586164a2/user-1000@00054
> 55bfdbeb23d-1ff3046498e945ad.journal~
> PASS: /var/log/journal/52f04da61fa8108cd5f48bca586164a2/system@0005495e
> 3d56c587-44f1967167aac5a3.journal~
> PASS: /var/log/journal/52f04da61fa8108cd5f48bca586164a2/system@65bee6e3
> 4f3c4b77b265431a1dd2a6df-0001-0005459b8fd2a11e.journal
> c84f48: Invalid entry item (8/24 offset:
> 00   
> c84f48: Invalid object contents: Bad
> message  
> File corruption detected at /var/log/journal/52f04da61fa8108cd5f48bca58
> 6164a2/system@0005459b8ff5e32b-620437abf7009d7d.journal~:c84f48 (of
> 16777216 bytes, 78%).
> FAIL: /var/log/journal/52f04da61fa8108cd5f48bca586164a2/system@0005459b
> 8ff5e32b-620437abf7009d7d.journal~ (Bad message)
> PASS: /var/log/journal/52f04da61fa8108cd5f48bca586164a2/user-
> 1000.journal 
> PASS: /var/log/journal/52f04da61fa8108cd5f48bca586164a2/user-1000@00054
> 95e3de63208-bbc6d86046b94014.journal~
> PASS: /var/log/journal/52f04da61fa8108cd5f48bca586164a2/user-1105@2a1f1
> b3f5241431483971743eded852c-d6d6-000547f91700222b.journal
> PASS: /var/log/journal/52f04da61fa8108cd5f48bca586164a2/user-1000@00054
> 59b907b630d-a25c081908a032be.journal~
> PASS: /var/log/journal/52f04da61fa8108cd5f48bca586164a2/system@0005495e
> 8db292fb-cb1d4cbe87b5093f.journal~
> PASS: /var/log/journal/52f04da61fa8108cd5f48bca586164a2/user-1001@1dd4c
> 9dcd66446b483e91ea564f6f1b6-43c6-0005478f1ea62cb4.journal
> PASS:
> /var/log/journal/52f04da61fa8108cd5f48bca586164a2/system.journal   
>  
> 3a86e0: Invalid
> object 
>    
> File corruption detected at /var/log/journal/52f04da61fa8108cd5f48bca58
> 6164a2/user-1000@0005495ac03d6f02-bc5bf9a6b1d16fec.journal~:3a86e0 (of
> 8388608 bytes, 45%).
> FAIL: /var/log/journal/52f04da61fa8108cd5f48bca586164a2/user-1000@00054
> 95ac03d6f02-bc5bf9a6b1d16fec.journal~ (Bad message)
> PASS: 

Re: [systemd-devel] [PATCH] hostnamed: regard convertible chassis type as laptop

[Jani Nikula]

On Mon, 27 Feb 2017, David Herrmann  wrote:
> Turned into a github PR [1]. Can we continue the discussion there?

Sure thing. Thanks, David!

BR,
Jani.

-- 
Jani Nikula, Intel Open Source Technology Center
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] [PATCH] hostnamed: regard convertible chassis type as laptop

[David Herrmann]

Hey Jani!

On Fri, Feb 24, 2017 at 4:16 PM, Jani Nikula  wrote:
> On Fri, 24 Feb 2017, Jani Nikula  wrote:
>> While both the DMI and ACPI data are regarded as unreliable in hostnamed
>> source, consumers of the chassis type use it to make rather drastic
>> policy decisions.
>
> BTW, since the implementation seems to think the data is unreliable,
> perhaps it would be prudent to say so in hostnamectl documentation, so
> the consumers of the data might be more thoughtful about what to use it
> for?

Turned into a github PR [1]. Can we continue the discussion there?

Thanks
David

[1] https://github.com/systemd/systemd/pull/5475
___
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?

[Reindl Harald]

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?

[lejeczek]

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] [PATCH] add LIB_ARCH_TUPLE for tilegx-linux-gnu

[Martin Pitt]

Helmut Grohne [2017-02-27 16:51 +0100]:
> The following changes since commit 3c3fff44b2c46818bc240e3237925ad927b2831e:
> 
>   man: fix typo (#5468) (2017-02-27 13:59:11 +0100)
> 
> are available in the git repository at:
> 
>   git://git.subdivi.de/~helmut/systemd.git tilegx
> 
> for you to fetch changes up to c05c6e9cedf20b64b22249f88af514a70b6edd4b:
> 
>   add LIB_ARCH_TUPLE for tilegx-linux-gnu (2017-02-27 16:21:06 +0100)

Imported into https://github.com/systemd/systemd/pull/5474

Thanks!

Martin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] [PATCH] add LIB_ARCH_TUPLE for tilegx-linux-gnu

[systemd github import bot]

Patchset imported to github.
To create a pull request, one of the main developers has to initiate one via:


--
Generated by https://github.com/haraldh/mail2git
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] [PATCH] add LIB_ARCH_TUPLE for tilegx-linux-gnu

[Helmut Grohne]

The following changes since commit 3c3fff44b2c46818bc240e3237925ad927b2831e:

  man: fix typo (#5468) (2017-02-27 13:59:11 +0100)

are available in the git repository at:

  git://git.subdivi.de/~helmut/systemd.git tilegx

for you to fetch changes up to c05c6e9cedf20b64b22249f88af514a70b6edd4b:

  add LIB_ARCH_TUPLE for tilegx-linux-gnu (2017-02-27 16:21:06 +0100)

This commit fixes a build failure on the tilegx architecture. A
downstream bug report is located at https://bugs.debian.org/856306.


Helmut Grohne (1):
  add LIB_ARCH_TUPLE for tilegx-linux-gnu

 src/basic/architecture.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/basic/architecture.h b/src/basic/architecture.h
index d6b8603b0..b0a7de5dc 100644
--- a/src/basic/architecture.h
+++ b/src/basic/architecture.h
@@ -187,7 +187,7 @@ int uname_architecture(void);
 #  define LIB_ARCH_TUPLE "m68k-linux-gnu"
 #elif defined(__tilegx__)
 #  define native_architecture() ARCHITECTURE_TILEGX
-#  error "Missing LIB_ARCH_TUPLE for TILEGX"
+#  define LIB_ARCH_TUPLE "tilegx-linux-gnu"
 #elif defined(__cris__)
 #  define native_architecture() ARCHITECTURE_CRIS
 #  error "Missing LIB_ARCH_TUPLE for CRIS"
___
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?

[Lennart Poettering]

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] udev virtio by-path naming

[Michal Sekletar]

On Fri, Feb 24, 2017 at 10:56 AM, Viktor Mihajlovski
 wrote:
> On 20.02.2017 17:00, Cornelia Huck wrote:
>> On Mon, 20 Feb 2017 15:34:49 +0100
>> Viktor Mihajlovski  wrote:
>>
>>> Hi,
>>>
>>> with systemd > v229 all virtio block devices will receive persistent
>>> device names in the format /dev/disk-by/virtio-pci-, the
>>> last component being the udev built-in path_id.
>>>
>>> This naming introduces some issues.
>>>
>>> First and obvious, there are virtio implementations not based
>>> on PCI, like virtio-ccw (currently only on s390) and virtio-mmio
>>> (for which I can't speak). This results in persistent names like
>>> /dev/disk-by/virtio-pci-0.0.0001, where the bus id is a CCW id.
>>> One seemingly obvious remedy would be to make the path_id return
>>> virtio-ccw- or more generally virtio--,
>>> both easily done with small patches to systemd-udev.
>>>
>>> But then, I find this naming scheme somewhat weird.
>>> A virtio disk shows up as a regular PCI function on the PCI
>>> bus side by side with other (non-virtio) devices. The naming otoh
>>> suggests that virtio-pci is a subsystem of its own, which is simply
>>> incorrect from a by-path perspective.
>>
>> From the ccw perspective, this is quite similar: The virtio proxy
>> device shows up on the ccw bus, just like e.g. a dasd device shows up
>> on the ccw bus.
>>
>>>
>>> Using just the plain PCI path id is actually sufficient to identify
>>> a virtio disk by its path. This would be in line with virtio
>>> network interface path names which use the plain PCI naming.
>>
>> Same for ccw: The id on the ccw bus (devno) is already unique and
>> persistent.
>>
>>>
>>> One could argue about back-level compatibility, but virtio by-path
>>> naming has changed multiple times. We have seen virtio-pci-virtio
>>> (not predictable), pci- and virtio-pci- already. It
>>> might be a good time now to settle on a common approach for all
>>> virtio types.
>>>
>>> For the reasons above, I'd vote for -, which
>>> would work for PCI and CCW, not sure about ARM MMIO though.
>>> Opinions?
>>
>> I'm not sure whether there is any reason to make virtio special,
>> although this depends upon what virtio-mmio looks like in the Linux
>> device model (any arm folks here?)
>>
>> In the end, I'd be happy with any naming scheme that does not include
>> 'pci' for non-pci devices.
>>
> Michal, as author of commit f073b1b3c0f4f0df1b0bd61042ce85fb5d27d407
> that introduced this behavior: can you comment on the reasoning for
> prepending virtio- to the bus, i.e. why would pci- not
> sufficiently identify the device?

As with many things, it looked like a good idea at the time. In commit
message I referenced discussion on upstream mailing list. In that
thread we got reassured that there is one-to-one correspondence
between virtio and pci devices. IIRC, we had bugs for RHEL and CentOS
7 were users requested these symlinks. Hence we went ahead with above
naming scheme.

Your argument about virtio being first component of the path makes
sense to me, but then again, we wanted to distinguish these devices
(because of user demands).

In retrospect what we did wasn't probably the best we could.
Nevertheless, I'd not change the naming. After all, these symlinks are
for users and since then I didn't hear complains about them. I'd only
adjust the code so that we produce correctly named symlinks for
different parent buses (pci, ccw, mmio). IOW we would remove hardcoded
"pci" string.

Michal
>
> --
>
> Mit freundlichen Grüßen/Kind Regards
>Viktor Mihajlovski
>
> IBM Deutschland Research & Development GmbH
> Vorsitzender des Aufsichtsrats: Martina Köderitz
> Geschäftsführung: Dirk Wittkopp
> Sitz der Gesellschaft: Böblingen
> Registergericht: Amtsgericht Stuttgart, HRB 243294
>
___
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?

[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.


-- 
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?

[lejeczek]

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?

[Reindl Harald]

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?

[Reindl Harald]

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

[systemd-devel] how make systemd NOT to clutter dmesg?

[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...

but basically seems like the whole lot, into the dmesg?
I have one box which has clean dmesg and the other which has 
everything from systemd, I cannot figure what makes this 
different behaviour.


many thanks,
L.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel