Thanks Tobias for all of the responses. Yes, I am using plain, unaliased
jounalctl on Arch Linux with systemd 216. In fact, I see absolutely no
"Starting" "Stopping" service messages outside of standard triggers. Is
something wrong with my distro? :/ Was the logging changed in 216?
-Alex
On Mon, Sep 22, 2014 at 8:37 PM, Tobias Geerinckx-Rice <
tobias.geerinckx.r...@gmail.com> wrote:
> On 23 September 2014 01:10, Alexander Groleau <awg...@xbetanet.com> wrote:
> > Hmm,
> >
> > This is a fresh installation of arch linux with systemd. What else might
> be
> > terminating my daemons or how might I be able to figure that out?
>
> A cursory search linked that suspicious EOF error message to libvirtd
> crashing. If that's what's happening here, libvirtd could already be
> dead while systemd is correctly handling ExecStop=. Does this error
> message appear when manually stopping or restarting just
> libvirtd.service?
>
> There may be other hints somewhere in the logs. I just don't
> understand why yours don't contain or show those "Stopping..."
> messages that mine are full of [1]. You are using plain, unaliased
> journalctl, right?
>
> Also, focus on getting "systemd {stop,start,restart} libvirt.service"
> to work first, without all the extra complexity (and potential races,
> and time) of a full shut-down.
>
> Regards,
>
> T G-R
>
> [1] Messages which are being fiercely attacked elsewhere on this list.
> Hurry! ;-)
>
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
