[systemd-devel] systemd coredumps

[Zbigniew Jędrzejewski-Szmek]

On Thu, Jan 01, 2015 at 01:13:30PM -0500, Dave Reisner wrote:
> On Thu, Jan 01, 2015 at 07:05:04PM +0100, Zbigniew Jędrzejewski-Szmek wrote:
> > On Thu, Jan 01, 2015 at 05:57:43PM -0000, Markus Moeller wrote:
> > > Hi,
> > > 
> > >  How can I find out why systemd core dumps  and requires system
> > > reboot :-( ?
> > > 
> > > I just did
> > > 
> > > # systemctl status sockd-1.5.0
> > > Failed to issue method call: Did not receive a reply. Possible
> > > causes include: the remote application did not send a reply, the
> > > message bus security policy blocked the reply, the reply timeout
> > > expired, or the network connection was broken.
> > > # systemctl status sockd-1.5.0
> > > Failed to get D-Bus connection: Failed to connect to socket
> > > /run/systemd/private: Connection refused
> > > 
> > > 2015-01-01T17:52:01.625495+00:00 opensuse12 systemd[1]: Accepted
> > > connection on private bus.
> > > 2015-01-01T17:52:01.626333+00:00 opensuse12 systemd[1]: Running GC...
> > > 2015-01-01T17:52:01.627976+00:00 opensuse12 systemd[1]: Got D-Bus
> > > request: org.freedesktop.DBus.Properties.GetAll() on
> > > /org/freedesktop/systemd1/unit/sockd_2d1_2e5_2e0
> > > 2015-01-01T17:52:01.636546+00:00 opensuse12 systemd[1]: Assertion
> > > 'endswith(path, ".service")' failed at src/core/service.c:1077,
> > > function service_load_sysv_name(). Aborting.
> > The reason is given right here. A failed assertion, i.e. a programming
> > error.
> > 
> > Please open a bug on bugs.freedesktop.org and attach the core if you can
> > and describe the steps to trigger this.
> 
> Hrmm? The OP is using a build of systemd v195. It's unlikely this is
> reproducible at HEAD, or any recent release. The referenced function was
> removed in v214 (see commit 817e224bbce3ed) when sysv unit handling was
> moved off to a generator.
Good point, I didn't look at the version. Indeed, the bug is long fixed.

Zbyszek