On Wed, Apr 29, 2015 at 11:46:50AM +0200, Lennart Poettering wrote:
> On Tue, 28.04.15 19:25, John Morrissey (j...@horde.net) wrote:
> > On 18 Feb 2015, at 18:47, Lennart Poettering
> > wrote:
> > > Hmm, this appears to be caused by a timer that is not reset. First the
> > > timer fd is set to th
On Tue, 28.04.15 19:25, John Morrissey (j...@horde.net) wrote:
> On 18 Feb 2015, at 18:47, Lennart Poettering
> wrote:
> > Hmm, this appears to be caused by a timer that is not reset. First the
> > timer fd is set to the earliest possible trigger, then epoll_wait() is
> > entered, which immediat
On 18 Feb 2015, at 18:47, Lennart Poettering wrote:
> Hmm, this appears to be caused by a timer that is not reset. First the
> timer fd is set to the earliest possible trigger, then epoll_wait() is
> entered, which immediately quites. Then the tiemrfd elapse counter is
> read which is 1.
>
> It w
On Tue, Apr 28, 2015 at 07:25:34PM -0400, John Morrissey wrote:
> I noticed this behavior recently on a Debian jessie system running systemd
> 215-17. systemd got itself in a loop like the previous reporter's:
Aaaand of course I forgot the URL to the previous post:
http://lists.freedesktop.org/
Hi,
I've just seen a bug happen similiar to [1] and [2]. My machine was
out of memory (and qemu launched via libvirt was killed by the OOM
killer), and since then I got "Cannot use systemctl after heavy
swapping" a lot in my journal.
strace'ing PID 1 showed this repeating pattern:
clock_gett
> On 18 Feb 2015, at 18:47, Lennart Poettering wrote:
>
> On Wed, 18.02.15 10:41, Thierry Parmentelat (thierry.parmente...@inria.fr)
> wrote:
>
>> root@bigjohn /vservers # journalctl -b -f
>> -- Logs begin at Fri 2014-09-05 04:28:57 CEST. --
>> Feb 18 10:38:25 bigjohn.pl.sophia.inria.fr system
On Wed, 18.02.15 10:41, Thierry Parmentelat (thierry.parmente...@inria.fr)
wrote:
> root@bigjohn /vservers # journalctl -b -f
> -- Logs begin at Fri 2014-09-05 04:28:57 CEST. --
> Feb 18 10:38:25 bigjohn.pl.sophia.inria.fr systemd[1]: Looping too fast.
> Throttling execution a little.
> Feb 18 1
Hi there
---
I am running a fedora21 box that acts as a libvirt host for lxc containers
guests
This is based on vanilla fedora (maybe a little bit behind by a few weeks) and
a locally rebuild libvirt based on 1.2.11
root@bigjohn /var/log # uname -a
Linux bigjohn.pl.sophia.inria.fr 3.18.3-201