[systemd-devel] Unit failed to load: Cannot allocate memory.

[Lennart Poettering]

On Sat, 20.08.11 15:21, Mike Kazantsev (mk.fraggod at gmail.com) wrote:

> On Thu, 18 Aug 2011 16:20:20 +0200
> Lennart Poettering <lennart at poettering.net> wrote:
> 
> > On Tue, 09.08.11 07:02, Mike Kazantsev (mk.fraggod at gmail.com) wrote:
> > 
> > > Good day,
> > > 
> > > Updating to systemd-33 (with "include missing.h" patch) seem to give me
> > > the following errors on boot:
> > > 
> > >   [   27.024525] systemd[1]: Cannot add dependency job for unit fossil_echo.service, ignoring: Unit fossil_echo.service failed to load: Cannot allocate memory. See system logs and 'systemctl status fossil_echo.service' for details.
> ...
> > 
> > Any chance you can bisect this?
> > 
> 
> Reexec reacts on these units right before "Deserializing state..." msg,
> with the same messages.
> I'll check whether they go away on reexec to 32 and reappear in 33, and
> if that's the case, will have results shortly.

Can you reproduce this issue when you run "systemd --test --system" as
normal user after boot?

> [   49.043632] systemd[1]:      /lib64/systemd/system

Unrelated to your issue, but this looks very broken. /lib64 is for
secondary arch files, such as 64bit versions of the libraries and
stuff. systemd unit files are no different for the secondary archs and
they belong in /lib/systemd/system regardless which secondary arch is
used.

Lennart

-- 
Lennart Poettering - Red Hat, Inc.