Bug#789796: systemd[1]: Looping too fast. Throttling execution a little.

[Michael Biebl]

Am 18.07.2016 um 19:01 schrieb Martin von Wittich:
> So as far as I'm concerned, this update can be released.

Thanks a lot Martin for the very thorough testing.
Very much appreciated.

Regards,
Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#789796: systemd[1]: Looping too fast. Throttling execution a little.

[Martin von Wittich]

Hi,

the promised update (I know, I'm a little late):

I ran the following two commands on all the servers I listed in my 
previous mail to count the amount of "BUG" and "Looping too fast" 
messages in the past 5 days:


zgrep Loop 
/var/log/syslog{-20160714.gz,-20160715.gz,-20160716.gz,-20160717,} | wc -l
zgrep BUG 
/var/log/syslog{-20160714.gz,-20160715.gz,-20160716.gz,-20160717,} | wc -l


I've counted a grand total of 0 "BUG" and 0 "Looping too fast" (I made 
sure that my grep commands actually work by replacing the pattern with 
"." because I thought I was doing something wrong ^^).


No complaints from our developers either, and all VMs have an uptime of 
at least 5 days, so apparently there haven't been any unexpected or 
desperate reboots. I also looked into htop on each machine; no systemd 
process was hogging the CPU, and used CPU time of the systemd processes 
was between a few seconds (for a machine that really does nothing 
useful), ~16 minutes (most normal machines), and one had 50 minutes (our 
most busy machine).


So as far as I'm concerned, this update can be released.

--
Mit freundlichen Grüßen,
Martin von Wittich

IServ GmbH
Bültenweg 73
38106 Braunschweig

Telefon:   0531-2243666-0
Fax:   0531-2243666-9
E-Mail:i...@iserv.eu
Internet:  iserv.eu

USt-IdNr. DE265149425 | Amtsgericht Braunschweig | HRB 201822
Geschäftsführer: Benjamin Heindl, Jörg Ludwig

Bug#789796: systemd[1]: Looping too fast. Throttling execution a little.

[Martin von Wittich]

Hi,

here are the results so far:

Domain-0: systemd 215-17+deb8u4


xendev.iserv.eu ~ # zgrep Loop /var/log/syslog* | wc -l
0
xendev.iserv.eu ~ # zgrep BUG /var/log/syslog* | wc -l
0
xendev.iserv.eu ~ # zgrep Loop /var/log/syslog{-20160712.gz,-20160713,} | wc -l
0
xendev.iserv.eu ~ # zgrep BUG /var/log/syslog{-20160712.gz,-20160713,} | wc -l
0


build-i386: systemd 215-17+deb8u4


build-i386.iserv.eu ~ # zgrep Loop /var/log/syslog* | wc -l
0
build-i386.iserv.eu ~ # zgrep BUG /var/log/syslog* | wc -l
1
build-i386.iserv.eu ~ # zgrep Loop /var/log/syslog{-20160712.gz,-20160713,} | 
wc -l
0
build-i386.iserv.eu ~ # zgrep BUG /var/log/syslog{-20160712.gz,-20160713,} | wc 
-l
0


dev2: systemd 215-17+deb8u4


dev2.iserv.eu ~ # zgrep Loop /var/log/syslog* | wc -l
232
dev2.iserv.eu ~ # zgrep BUG /var/log/syslog* | wc -l
412
dev2.iserv.eu ~ # zgrep Loop /var/log/syslog{-20160712.gz,-20160713,} | wc -l
0
dev2.iserv.eu ~ # zgrep BUG /var/log/syslog{-20160712.gz,-20160713,} | wc -l
0


tim: systemd 215-17+deb8u4


tim.mein-iserv.de ~ # zgrep Loop /var/log/syslog* | wc -l
0
tim.mein-iserv.de ~ # zgrep BUG /var/log/syslog* | wc -l
46
tim.mein-iserv.de ~ # zgrep Loop /var/log/syslog{-20160712.gz,-20160713,} | wc 
-l
0
tim.mein-iserv.de ~ # zgrep BUG /var/log/syslog{-20160712.gz,-20160713,} | wc -l
8


dev3: systemd 215-17+deb8u5~1.gbp51d6e1


dev3.iserv.eu ~ # zgrep Loop /var/log/syslog* | wc -l
0
dev3.iserv.eu ~ # zgrep BUG /var/log/syslog* | wc -l
755
dev3.iserv.eu ~ # zgrep Loop /var/log/syslog{-20160712.gz,-20160713,} | wc -l
0
dev3.iserv.eu ~ # zgrep BUG /var/log/syslog{-20160712.gz,-20160713,} | wc -l
18


janis: systemd 215-17+deb8u5~1.gbp51d6e1


janis.mein-iserv.de ~ # zgrep Loop /var/log/syslog* | wc -l
0
janis.mein-iserv.de ~ # zgrep BUG /var/log/syslog* | wc -l
64
janis.mein-iserv.de ~ # zgrep Loop /var/log/syslog{-20160712.gz,-20160713,} | 
wc -l
0
janis.mein-iserv.de ~ # zgrep BUG /var/log/syslog{-20160712.gz,-20160713,} | wc 
-l
4


gunnar: systemd 215-17+deb8u5~1.gbp51d6e1


gunnar.mein-iserv.de ~ # zgrep Loop /var/log/syslog* | wc -l
0
gunnar.mein-iserv.de ~ # zgrep BUG /var/log/syslog* | wc -l
26
gunnar.mein-iserv.de ~ # zgrep Loop /var/log/syslog{-20160712.gz,-20160713,} | 
wc -l
0
gunnar.mein-iserv.de ~ # zgrep BUG /var/log/syslog{-20160712.gz,-20160713,} | 
wc -l
5


jerg: systemd 215-17+deb8u5~1.gbp51d6e1


jerg.mein-iserv.de ~ # zgrep Loop /var/log/syslog* | wc -l
0
jerg.mein-iserv.de ~ # zgrep BUG /var/log/syslog* | wc -l
46
jerg.mein-iserv.de ~ # zgrep Loop /var/log/syslog{-20160712.gz,-20160713,} | wc 
-l
0
jerg.mein-iserv.de ~ # zgrep BUG /var/log/syslog{-20160712.gz,-20160713,} | wc 
-l
34


dominik: systemd 215-17+deb8u5~1.gbp51d6e1


dominik.mein-iserv.de ~ # zgrep Loop /var/log/syslog* | wc -l
8560
dominik.mein-iserv.de ~ # zgrep BUG /var/log/syslog* | wc -l
34
dominik.mein-iserv.de ~ # zgrep Loop /var/log/syslog{-20160712.gz,-20160713,} | 
wc -l
0
dominik.mein-iserv.de ~ # zgrep BUG /var/log/syslog{-20160712.gz,-20160713,} | 
wc -l
6


florian: systemd 215-17+deb8u5~1.gbp51d6e1


florian.mein-iserv.de ~ # zgrep Loop /var/log/syslog* | wc -l
4124
florian.mein-iserv.de ~ # zgrep BUG /var/log/syslog* | wc -l
620
florian.mein-iserv.de ~ # zgrep Loop /var/log/syslog{-20160712.gz,-20160713,} | 
wc -l
0
florian.mein-iserv.de ~ # zgrep BUG /var/log/syslog{-20160712.gz,-20160713,} | 
wc -l
7


max: systemd 215-17+deb8u5~1.gbp51d6e1


max.mein-iserv.de ~ # zgrep Loop /var/log/syslog* | wc -l
0
max.mein-iserv.de ~ # zgrep BUG /var/log/syslog* | wc -l
32
max.mein-iserv.de ~ # zgrep Loop /var/log/syslog{-20160712.gz,-20160713,} | wc 
-l
0
max.mein-iserv.de ~ # zgrep BUG /var/log/syslog{-20160712.gz,-20160713,} | wc -l
1


redmine: systemd 215-17+deb8u5~1.gbp51d6e1


redmine.iserv.eu ~ # zgrep Loop /var/log/syslog* | wc -l
0
redmine.iserv.eu ~ # zgrep BUG /var/log/syslog* | wc -l
0
redmine.iserv.eu ~ # zgrep Loop /var/log/syslog{-20160712.gz,-20160713,} | wc -l
0
redmine.iserv.eu ~ # zgrep BUG /var/log/syslog{-20160712.gz,-20160713,} | wc -l
0


joerg: systemd 215-17+deb8u5~1.gbp51d6e1


joerg.mein-iserv.de ~ # zgrep Loop /var/log/syslog* | wc -l
21483
joerg.mein-iserv.de ~ # zgrep BUG /var/log/syslog* | wc -l
30
joerg.mein-iserv.de ~ # zgrep Loop /var/log/syslog{-20160712.gz,-20160713,} | 
wc -l
0
joerg.mein-iserv.de ~ # zgrep BUG /var/log/syslog{-20160712.gz,-20160713,} | wc 
-l
0


As you can see, there wasn't a single "Looping too fast" message in the 
last 3 syslogs (2016-07-12 0:00 to 2016-07-14 ~2:00) [zgrep Loop 
/var/log/syslog{-20160712.gz,-20160713,} output], although most VMs had 
been affected by this issue in the past [zgrep Loop /var/log/syslog* 
output].


Unfortunately this is true both for VMs with systemd 
215-17+deb8u5~1.gbp51d6e1 and for VMs with systemd 215-17+deb8u4, so in 
the last three days, not even the old version of systemd had this issue. 
Maybe the bug is exacerbated by CPU starvation, so that in the past it 
started on a single VM, and then spread like a domino effect 

Bug#789796: systemd[1]: Looping too fast. Throttling execution a little.

[Martin von Wittich]

Hi Michael,

> I pulled the patch mentioned in this bug report into our jessie branch
> [1]. This means it will be part of the next stable release which is
> scheduled for the upcoming 8.6 point release.
> 
> I created debs which you can get from [2]. I versioned them so that the
> package will nicely upgrade once the final 215-17+deb8u5 reaches the
> stable archive.
> It would be great if you install and test those packages and report back.

Thanks! I've installed the new systemd packages on 10 of our 12 development 
VMs; I couldn't install them on the other two because those are i386. If you 
could provide i386 builds, I'll install them on those machines too.

It didn't take longer than a day for that issue to occur on at least one 
machine, so testing this shouldn't take too long. I've set up reminders on 
Wednesday and Friday so that I won't forget to report back.

Martin

Bug#789796: systemd[1]: Looping too fast. Throttling execution a little.

[Michael Biebl]

Hi Martin

Am 11.07.2016 um 09:54 schrieb Martin von Wittich:
> Any update on this? Debian 8.5 has been released in June, but we're
> still seeing this bug on our VMs.

I pulled the patch mentioned in this bug report into our jessie branch
[1]. This means it will be part of the next stable release which is
scheduled for the upcoming 8.6 point release.

I created debs which you can get from [2]. I versioned them so that the
package will nicely upgrade once the final 215-17+deb8u5 reaches the
stable archive.
It would be great if you install and test those packages and report back.

Regards,
Michael


[1] http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/log/?h=jessie
[2] https://people.debian.org/~biebl/systemd/jessie/
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#789796: systemd[1]: Looping too fast. Throttling execution a little.

[Martin von Wittich]

Any update on this? Debian 8.5 has been released in June, but we're
still seeing this bug on our VMs.

-- 
Mit freundlichen Grüßen
Martin v. Wittich

IServ GmbH
Bültenweg 73
38106 Braunschweig

Telefon:   0531-2243666-0
Fax:   0531-2243666-9
E-Mail:i...@iserv.eu
Internet:  iserv.eu

USt-IdNr. DE265149425 | Amtsgericht Braunschweig | HRB 201822
Geschäftsführer: Benjamin Heindl, Jörg Ludwig

Bug#789796: systemd[1]: Looping too fast. Throttling execution a little

[Stefanos Harhalakis]

Hi,

Can this be uploaded to jessie?

It would be of great help and, in a sense, having to run containers with 
full privileges is a security issue.


Thanks,
Stefanos

Bug#789796: systemd[1]: Looping too fast. Throttling execution a little.

[Alexander Barton]

FYI, we are seeing this here as well:

---
Oct 07 10:11:21 testhost systemd[1]: Looping too fast. Throttling execution a 
little.
Oct 07 10:11:22 testhost systemd[1]: Looping too fast. Throttling execution a 
little.
Oct 07 10:11:23 testhost systemd[1]: Looping too fast. Throttling execution a 
little.
Oct 07 10:11:25 testhost systemd[1]: Looping too fast. Throttling execution a 
little.
Oct 07 10:11:26 testhost systemd[1]: Looping too fast. Throttling execution a 
little.
Oct 07 10:11:27 testhost systemd[1]: Looping too fast. Throttling execution a 
little.
Oct 07 10:11:28 testhost systemd[1]: Looping too fast. Throttling execution a 
little.
Oct 07 10:11:29 testhost systemd[1]: Looping too fast. Throttling execution a 
little.
Oct 07 10:11:30 testhost systemd[1]: Looping too fast. Throttling execution a 
little.
Oct 07 10:11:31 testhost systemd[1]: Looping too fast. Throttling execution a 
little.
Oct 07 10:11:33 testhost systemd[1]: Looping too fast. Throttling execution a 
little.
---

Debian 8, systemd 215 (215-17+deb8u2).

Thanks!
Alex

Bug#789796: systemd[1]: Looping too fast. Throttling execution a little.

[Alexander Barton]

Am 07.10.2015 um 13:12 schrieb Michael Biebl :
 
> Am 07.10.2015 um 10:13 schrieb Alexander Barton:
> > FYI, we are seeing this here as well:
> > 
> > ---
> > Oct 07 10:11:21 testhost systemd[1]: Looping too fast. Throttling execution 
> > a little.
> > Oct 07 10:11:22 testhost systemd[1]: Looping too fast. Throttling execution 
> > a little.
> > Oct 07 10:11:23 testhost systemd[1]: Looping too fast. Throttling execution 
> > a little.
> > Oct 07 10:11:25 testhost systemd[1]: Looping too fast. Throttling execution 
> > a little.
> > Oct 07 10:11:26 testhost systemd[1]: Looping too fast. Throttling execution 
> > a little.
> > Oct 07 10:11:27 testhost systemd[1]: Looping too fast. Throttling execution 
> > a little.
> > Oct 07 10:11:28 testhost systemd[1]: Looping too fast. Throttling execution 
> > a little.
> > Oct 07 10:11:29 testhost systemd[1]: Looping too fast. Throttling execution 
> > a little.
> > Oct 07 10:11:30 testhost systemd[1]: Looping too fast. Throttling execution 
> > a little.
> > Oct 07 10:11:31 testhost systemd[1]: Looping too fast. Throttling execution 
> > a little.
> > Oct 07 10:11:33 testhost systemd[1]: Looping too fast. Throttling execution 
> > a little.
> > ---
> > 
> > Debian 8, systemd 215 (215-17+deb8u2).
> 
> Can you reproduce the problem?

Up to now I can't reproduce the problem: after rebooting the system everything
seems to work just fine …

The shutdown hung at first, after issuing "systemctl daemon-reexec" it
continued; probably "systemctl daemon-reexec" would have "solved" the problem
in the first place? Don't know … I wasn't fast enough and failed to cancel the
shutdown in time.

> Are you willing to test a package with the patch applied from upstream?

If I find a way to reproduce the problem (or it reappears by itself) I can test
the package, sure.
 
> If so, I can provide you such packages. What architecture is that, i386,
> amd64?

amd64.

Regards
Alex

Bug#789796: systemd[1]: Looping too fast. Throttling execution a little.

[Michael Biebl]

Hi,

Am 07.10.2015 um 10:13 schrieb Alexander Barton:
> FYI, we are seeing this here as well:
> 
> ---
> Oct 07 10:11:21 testhost systemd[1]: Looping too fast. Throttling execution a 
> little.
> Oct 07 10:11:22 testhost systemd[1]: Looping too fast. Throttling execution a 
> little.
> Oct 07 10:11:23 testhost systemd[1]: Looping too fast. Throttling execution a 
> little.
> Oct 07 10:11:25 testhost systemd[1]: Looping too fast. Throttling execution a 
> little.
> Oct 07 10:11:26 testhost systemd[1]: Looping too fast. Throttling execution a 
> little.
> Oct 07 10:11:27 testhost systemd[1]: Looping too fast. Throttling execution a 
> little.
> Oct 07 10:11:28 testhost systemd[1]: Looping too fast. Throttling execution a 
> little.
> Oct 07 10:11:29 testhost systemd[1]: Looping too fast. Throttling execution a 
> little.
> Oct 07 10:11:30 testhost systemd[1]: Looping too fast. Throttling execution a 
> little.
> Oct 07 10:11:31 testhost systemd[1]: Looping too fast. Throttling execution a 
> little.
> Oct 07 10:11:33 testhost systemd[1]: Looping too fast. Throttling execution a 
> little.
> ---
> 
> Debian 8, systemd 215 (215-17+deb8u2).

Can you reproduce the problem? Are you willing to test a package with
the patch applied from upstream?

If so, I can provide you such packages. What architecture is that, i386,
amd64?

Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#789796: systemd[1]: Looping too fast. Throttling execution a little.

[Michael Biebl]

Am 07.10.2015 um 13:41 schrieb Alexander Barton:
> Am 07.10.2015 um 13:12 schrieb Michael Biebl :
>  
>> Am 07.10.2015 um 10:13 schrieb Alexander Barton:
>>> FYI, we are seeing this here as well:
>>>
>>> ---
>>> Oct 07 10:11:21 testhost systemd[1]: Looping too fast. Throttling execution 
>>> a little.
>>> Oct 07 10:11:22 testhost systemd[1]: Looping too fast. Throttling execution 
>>> a little.
>>> Oct 07 10:11:23 testhost systemd[1]: Looping too fast. Throttling execution 
>>> a little.
>>> Oct 07 10:11:25 testhost systemd[1]: Looping too fast. Throttling execution 
>>> a little.
>>> Oct 07 10:11:26 testhost systemd[1]: Looping too fast. Throttling execution 
>>> a little.
>>> Oct 07 10:11:27 testhost systemd[1]: Looping too fast. Throttling execution 
>>> a little.
>>> Oct 07 10:11:28 testhost systemd[1]: Looping too fast. Throttling execution 
>>> a little.
>>> Oct 07 10:11:29 testhost systemd[1]: Looping too fast. Throttling execution 
>>> a little.
>>> Oct 07 10:11:30 testhost systemd[1]: Looping too fast. Throttling execution 
>>> a little.
>>> Oct 07 10:11:31 testhost systemd[1]: Looping too fast. Throttling execution 
>>> a little.
>>> Oct 07 10:11:33 testhost systemd[1]: Looping too fast. Throttling execution 
>>> a little.
>>> ---
>>>
>>> Debian 8, systemd 215 (215-17+deb8u2).
>>
>> Can you reproduce the problem?
> 
> Up to now I can't reproduce the problem: after rebooting the system everything
> seems to work just fine …

How often did you run into the issue? Just once?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#789796: systemd[1]: Looping too fast. Throttling execution a little.

[Michael Biebl]

Am 29.09.2015 um 13:33 schrieb Michael Biebl:
> Hi
> 
> Am 24.06.2015 um 16:25 schrieb A Mennucc:
>> Package: systemd
>> Version: 215-17+deb8u1
>> Severity: normal
>>
>> Dear Mantainer,
>>
>> systemd is logging a lot of error messages as in the attached log
> 
> 
> See
> http://lists.freedesktop.org/archives/systemd-devel/2015-September/034356.html
> 
> Can you reproduce the problem of systemd looping too fast?
> If so, could you try this patch:
> 
> https://github.com/systemd/systemd/commit/8046c4576a68977a1089d2585866bfab8152661b
> 
> and report back

Fwiw, this looks like a patch which we might want to cherry-pick and
backport for jessie.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#789796: systemd[1]: Looping too fast. Throttling execution a little.

[Michael Biebl]

Hi

Am 24.06.2015 um 16:25 schrieb A Mennucc:
> Package: systemd
> Version: 215-17+deb8u1
> Severity: normal
> 
> Dear Mantainer,
> 
> systemd is logging a lot of error messages as in the attached log


See
http://lists.freedesktop.org/archives/systemd-devel/2015-September/034356.html

Can you reproduce the problem of systemd looping too fast?
If so, could you try this patch:

https://github.com/systemd/systemd/commit/8046c4576a68977a1089d2585866bfab8152661b

and report back

Thanks,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#789796: systemd[1]: Looping too fast. Throttling execution a little.

[A Mennucc1]

Il 24/06/2015 21:41, Marco d'Itri ha scritto:
 Can you clarify what you are complaining about exactly?
sure.

Yesterday systemd was filling its own logs with the message 
systemd[1]: Looping too fast. Throttling execution a little (as you can
see in the attached log sy_po_log.txt.xz ).

BTW to create the attachment I used  journalctl   sy_po_log.txt then 
deleted some private lines, then  compressed and attached it

Moreover I add this fact. I use the  tool  Mate System Monitor, that
graphs the CPU usage. Yesterday the graph was flat but for a recurring
spike of activity. IMHO the spike of activity was due to systemd crazy
looping, and then noticing it, and then throttling, up t the next crazy
loop.

This seems some sort of bug, or at least a misbehavior.

(In the end I rebooted the notbook, and it all went back to normal — but
on production servers this may be quite annoying)

This kind of problem was already reported in
  
http://lists.freedesktop.org/archives/systemd-devel/2015-February/028541.html
where they say:
 THis is happens if for some reason the event loop entered a busy
 loop. It's simply a protection against eating up all CPU forever. It's
 a symptom of another bug, which is the one to track down.
In the above post they suggest to use 'strace -p 1' ; I did that (for 2
seconds) and attached the result to this bug.

This other post
 
http://lists.freedesktop.org/archives/systemd-devel/2014-December/025867.html
suggests that the problem may occur after heavy swapping. This is
exactly what happened here two days ago: I was trying to compile
'git-annex' but ghc exhausted all the memory. Note though  but the
problem did not start immediately after the swapping; it started when I
put the notebook to sleep, and resumed it next morning.

My hypothesis is that at a certain point some parts of systemd died
because of lack of memory, indeed I could spot this
 giu 23 19:41:40 kytty systemd-journal[30249]: Journal started
 giu 23 19:41:40 kytty systemd-journald[227]: Received SIGTERM from PID 1 
 (systemd).
 giu 23 19:41:40 kytty systemd[1]: systemd-journald.service stop-sigterm timed 
 out. Killing.
 giu 23 19:41:40 kytty systemd[1]: systemd-journald.service: main process 
 exited, code=killed, status=9/KILL
 giu 23 19:41:40 kytty systemd[1]: Unit systemd-journald.service entered 
 failed state.
 giu 23 19:41:40 kytty kernel: ghc invoked oom-killer: gfp_mask=0x201da, 
 order=0, oom_score_adj=0
then after I put the notebook to sleep and resumed it, systemd wanted to
use those killed parts, but could not, and hence this triggered the
weird behavior. You may probably see if I am right or wrong by looking
at the strace. (I lack the competence).

A solution of this bug (if my analysis is correct) may be as follows. If
a part of systemd dies because of lack of memory, then, when the
situation is back to normal, systemd should restart it.

Hope this helps, thx

a.




signature.asc
Description: OpenPGP digital signature

Bug#789796: systemd[1]: Looping too fast. Throttling execution a little.

[A Mennucc]

Package: systemd
Version: 215-17+deb8u1
Severity: normal

Dear Mantainer,

systemd is logging a lot of error messages as in the attached log

I also attach the output of strace -p 1

Someone wrote on the Internet that this may happen when the system
runs out of memory. This was my case. In the log you may see

giu 23 19:41:40 kytty systemd-journal[30249]: Journal started
giu 23 19:41:40 kytty systemd-journald[227]: Received SIGTERM from PID 1 
(systemd).
giu 23 19:41:40 kytty systemd[1]: systemd-journald.service stop-sigterm timed 
out. Killing.
giu 23 19:41:40 kytty systemd[1]: systemd-journald.service: main process 
exited, code=killed, status=9/KILL
giu 23 19:41:40 kytty systemd[1]: Unit systemd-journald.service entered failed 
state.
giu 23 19:41:40 kytty kernel: ghc invoked oom-killer: gfp_mask=0x201da, 
order=0, oom_score_adj=0

Bye and thanks,

a.

-- Package-specific info:

-- System Information:
Debian Release: 8.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  acl 2.2.52-2
ii  adduser 3.113+nmu3
ii  initscripts 2.88dsf-59
ii  libacl1 2.2.52-2
ii  libaudit1   1:2.4-1+b1
ii  libblkid1   2.25.2-6
ii  libc6   2.19-18
ii  libcap2 1:2.24-8
ii  libcap2-bin 1:2.24-8
ii  libcryptsetup4  2:1.6.6-5
ii  libgcrypt20 1.6.3-2
ii  libkmod218-3
ii  liblzma55.1.1alpha+20120614-2+b3
ii  libpam0g1.1.8-3.1
ii  libselinux1 2.3-2
ii  libsystemd0 215-17+deb8u1
ii  mount   2.25.2-6
ii  sysv-rc 2.88dsf-59
ii  udev215-17+deb8u1
ii  util-linux  2.25.2-6

Versions of packages systemd recommends:
ii  dbus1.8.18-0+deb8u1
ii  libpam-systemd  215-17+deb8u1

Versions of packages systemd suggests:
pn  systemd-ui  none

-- no debconf information

-- 
Andrea Mennucc
 E' un mondo difficile. Che vita intensa! (Tonino Carotone)


sy_po_log.txt.xz
Description: application/xz


sy_po__strace.txt.xz
Description: application/xz


signature.asc
Description: Digital signature

Bug#789796: systemd[1]: Looping too fast. Throttling execution a little.

[Marco d'Itri]

On Jun 24, A Mennucc mennu...@debian.org wrote:

 systemd is logging a lot of error messages as in the attached log
 
 I also attach the output of strace -p 1
 
 Someone wrote on the Internet that this may happen when the system
 runs out of memory. This was my case. In the log you may see
Can you clarify what you are complaining about exactly?

-- 
ciao,
Marco


pgpZqlbDQB3f6.pgp
Description: PGP signature