Bug#765870: systemd-logind brings system to knees with RAM consumption

[John Goerzen]

I will try this.  It is a bit complicated because the system in question
is also running ZFS and there are some bugs with that boot, but I think
I have worked them out enough.  It may take me a few days to find the
time, however.

On 11/03/2014 08:43 PM, Michael Biebl wrote:
> Am 18.10.2014 um 21:49 schrieb John Goerzen:
>> Package: systemd
>> Version: 215-5+b1
>> Severity: grave
>> Justification: renders package unusable
>>
>> On investigating why my 8GB system, which was suddenly running extremely
>> slow and maxed out on swap, I discovered numerous systemd-logind
>> processes hogging RAM.  Specifically, 41 processes using 4278148KB (or
>> roughly 4GB) of RAM.
>>
>> Here is some output from top:
>>
>
> As John told me on IRC: He is running systemd-logind under systemd-shim
> on this particular system.
> On other systems, where systemd is PID 1 he does not experience this
issue.
> I told him to find out the current running systemd-logind process which
> owns the org.freedesktop.login1 D-Bus name via
> "dbus-send --system --dest=org.freedesktop.DBus --print-reply
> /org/freedesktop/DBus org.freedesktop.DBus.GetConnectionUnixProcessID
> string:org.freedesktop.login1"
>
> and monitor that process via strace while periodically checking with the
> above command, when logind drops off the bus. So we can eventually see
> from the strace what happens at that time.
>
> Unfortunately, when stracing the process, John is no longer able to
> reproduce the issue, as he told on IRC.
>
> John, to narrow down the problem, could you please boot with
> init=/bin/systemd to verify if this issue is indeed related to
systemd-shim.
>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20141109/ec0bbee8/attachment-0002.html>