Your message dated Mon, 28 Jan 2019 12:51:45 +0000
with message-id <e1go6o9-000ffz...@fasolo.debian.org>
and subject line Bug#920018: fixed in systemd 240-5
has caused the Debian Bug report #920018,
regarding Memory Leak in journald? Failed to write entry (23 items, 500
bytes), ignoring: Cannot allocate memory
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
920018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920018
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 240-4
Severity: important
Hi!
Since systemd_240-4 journald seems to either leak memory or something
strange is going on with my system.
Soon after boot or journald restart, I get messages like this in my
kernel log:
[...]
[31317.206261] systemd-journald[341]: Failed to write entry (29 items, 682
bytes), ignoring: Cannot allocate memory
[31330.715806] systemd-journald[341]: Failed to write entry (21 items, 547
bytes), ignoring: Cannot allocate memory
[31330.756475] systemd-journald[341]: Failed to write entry (21 items, 549
bytes), ignoring: Cannot allocate memory
[31330.756946] systemd-journald[341]: Failed to write entry (21 items, 633
bytes), ignoring: Cannot allocate memory
[31330.757454] systemd-journald[341]: Failed to write entry (21 items, 629
bytes), ignoring: Cannot allocate memory
[31331.070486] systemd-journald[341]: Failed to write entry (22 items, 577
bytes), ignoring: Cannot allocate memory
[31331.070625] systemd-journald[341]: Failed to write entry (22 items, 564
bytes), ignoring: Cannot allocate memory
[31331.103742] systemd-journald[341]: Failed to write entry (22 items, 581
bytes), ignoring: Cannot allocate memory
[31331.103878] systemd-journald[341]: Failed to write entry (22 items, 548
bytes), ignoring: Cannot allocate memory
[31331.104589] systemd-journald[341]: Failed to write entry (22 items, 562
bytes), ignoring: Cannot allocate memory
[31334.787786] systemd-journald[341]: Failed to write entry (24 items, 611
bytes), ignoring: Cannot allocate memory
[31335.992491] systemd-journald[341]: Failed to write entry (23 items, 500
bytes), ignoring: Cannot allocate memory
[...]
Also the committed memory size as recored by munin (see attached image)
spikes quickly. You can clearly spot in the graph, when I upgraded to
systemd_240-4. You can also see the times where I manually restarted
journald.
(Yes, this system is a bit small for all the services running on it,
hence the swap usage.)
I now have downgraded to systemd_240-3 which resolves this issue for me.
Other systems of mine show the same, but because they have more RAM, the
problem is not as visible (yet).
Grüße,
Sven.
-- Package-specific info:
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'unstable'), (500, 'testing'), (200, 'experimental'), (1, 'experimental-debug')
Architecture: i386 (x86_64)
Foreign Architectures: amd64
Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8),
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii adduser 3.118
ii libacl1 2.2.52-3+b1
ii libapparmor1 2.13.2-3
ii libaudit1 1:2.8.4-2
ii libblkid1 2.33.1-0.1
ii libc6 2.28-5
ii libcap2 1:2.25-1.2
ii libcryptsetup12 2:2.0.6-1
ii libgcrypt20 1.8.4-5
ii libgnutls30 3.6.5-2
ii libgpg-error0 1.33-3
ii libidn11 1.33-2.2
ii libip4tc0 1.8.2-3
ii libkmod2 25-2
ii liblz4-1 1.8.3-1
ii liblzma5 5.2.2-1.3
ii libmount1 2.33.1-0.1
ii libpam0g 1.1.8-4
ii libseccomp2 2.3.3-3
ii libselinux1 2.8-1+b1
ii libsystemd0 240-4
ii mount 2.33.1-0.1
ii util-linux 2.33.1-0.1
Versions of packages systemd recommends:
ii dbus 1.12.12-1
ii libpam-systemd 240-4
Versions of packages systemd suggests:
ii policykit-1 0.105-25
pn systemd-container <none>
Versions of packages systemd is related to:
pn dracut <none>
ii initramfs-tools 0.132
ii udev 240-4
-- Configuration Files:
/etc/systemd/journald.conf changed:
[Journal]
Storage=persistent
ForwardToConsole=yes
TTYPath=/dev/tty12
/etc/systemd/logind.conf changed:
[Login]
KillUserProcesses=no
/etc/systemd/system.conf changed:
[Manager]
RuntimeWatchdogSec=60
-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 240-5
We believe that the bug you reported is fixed in the latest version of
systemd, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Martin Pitt <mp...@debian.org> (supplier of updated systemd package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Sun, 27 Jan 2019 21:33:07 +0000
Source: systemd
Architecture: source
Version: 240-5
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers
<pkg-systemd-maintain...@lists.alioth.debian.org>
Changed-By: Martin Pitt <mp...@debian.org>
Closes: 919390 920018
Changes:
systemd (240-5) unstable; urgency=medium
.
[ Felipe Sateler ]
* Revert interface renaming changes. (Closes: #919390)
.
[ Martin Pitt ]
* process-util: Fix memory leak (Closes: #920018)
Checksums-Sha1:
7ca4cf0e5237140b58f79cbd085aefd8d149ccf4 4898 systemd_240-5.dsc
10bd8179fbecdd2e1042dfa0bb3ff7af3b2c542e 165928 systemd_240-5.debian.tar.xz
35957a2ecd9e3d91ab8e2e24e2578302ede86cba 5785 systemd_240-5_source.buildinfo
Checksums-Sha256:
dfd3171ad9a140feaff6719abcd7586e3f4d46e5e5f048c3b04aa8504a8c94d8 4898
systemd_240-5.dsc
85022f13fd97467d10760917ac190f5f2960cf03b2349eed02b84dc3128dcb59 165928
systemd_240-5.debian.tar.xz
8236986f70863b5b8b79adb74a7d1ff789b2df0b3adaa22be11742e4468c0215 5785
systemd_240-5_source.buildinfo
Files:
02768a90ec1bc4eb87b61b7c149f1e54 4898 admin optional systemd_240-5.dsc
3349beba2d35cdbd1e3b4c0601b6bda5 165928 admin optional
systemd_240-5.debian.tar.xz
7d4c1fe5c542be96eeb55ea405d66b24 5785 admin optional
systemd_240-5_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEExkOAo1eT0DvBz+1oxrkYDUvYt64FAlxO9m8ACgkQxrkYDUvY
t67ofxAAiFDXalkQjkYbWccpnthYqiyKhzXfeNB1YOcRjj98RcYFdP6atiFkzbix
SzyE6EbVaUg42lMgBpAQOBlR+3ppDm1sNkTIg5aXv+0oKMOiThLmZDks1itaYj56
6E3qem5R696hneb/bcsnPl8Vk4QFKEsuFDrLM1VaIew+hTgos0jvV748gxggDygl
j4QMWm91WU/QQvltq1ysBzkEsh/hYcJ0+UCBtoCjKhnDdIJ2Oz8py6bAtSkErhZ1
6EThM/b7gfgon0CYO43pYEvFG9ti5QyTbtM9ab13fjQmQSzkr3c0uC3F90lP6d4g
Deo5Ea+ywV6tx+psiXx6SBEJkdnvjSQaVDKR2jmVd2vhueZ3EohonEuRPTHb7YJA
mYVu8buOkI0tR3NhD372gslHxFow3kMKLNvKBUjqsShmDhmBysQdWx+yN9ncxKp7
YYHkyNUuZSxrxs7089943RI1jH1u4s8vmRnLylOTz9pfOU/PFNqBHLJiWNz4tHvq
038Q9InkOw2NBmHAq4qOgymhoOKWPQkrOxD6JJY+W9u30VLkyhMEqWPKifAZdrRA
RjgYh9G5pSGV0WrLRmfDouiQwz3vJIt4QEe84PiKza3KwSx3O7zDRqpih3Yq0AaX
1rGH6QdhO7HHOfeWur7Al5ew2w1iezlRUWNnCxIhJFajrPRkQrs=
=qu6e
-----END PGP SIGNATURE-----
--- End Message ---
