[systemd-devel] Failed units and "Unit type .busname is not supported on this system"

[Lennart Poettering]

On Fri, 06.02.15 17:12, John Lane (systemd at jelmail.com) wrote:

> Good afternoon. I have some errors in the boot sequence of a newly built
> system:
> 
> I see:
> 
>     systemd[1]: Unit type .busname is not supported on this system.

This may be ignored.

.busname units are only supported on kdbus systems.

> 
> then later on:
> 
>     systemd-networkd[278]: Assertion 'bus' failed at
> src/libsystemd/sd-bus/bus-util.c:105, function
> bus_event_loop_with_idle(). Aborting.
>     systemd[1]: Unit systemd-networkd.service entered failed state
>     systemd-networkd.service failed.

This looks like something to fix by Tom. Tom, can you please have a
look at this?

> and
> 
>     systemd-logind[565]: Failed to connect to system bus: No such file
> or directory
>     systemd-logind[565]: Failed to fully start up daemon: No such file
> or directory
>     Failed to start Login Service.

Are you sure you have installed dbus properly?

> 
> My "systemctl status" shows a "degraded" status with 3 failed units being
> 
>       UNIT                     LOAD   ACTIVE SUB    DESCRIPTION
> ● systemd-logind.service   loaded failed failed Login Service
> ● systemd-networkd.service loaded failed failed Network Service
> ● systemd-networkd.socket  loaded failed failed networkd rtnetlink
> socket

The latter is probably fixed by 30ae637af31551f6c3d8f27db4537aaddda462bb

Lennart

-- 
Lennart Poettering, Red Hat