On 2012-03-07 08:29, Gary Thomas wrote:
On 2012-03-07 08:22, Gary Thomas wrote:
On 2012-03-07 05:34, Christophe Aeschlimann wrote:
Hi,
On 04.03.2012 13:48, Gary Thomas wrote:
All of the recent images I've built (for beaglebone at least)
fail on boot with these messages:
Starting Journal Service...
Failed to start Journal Service
[FAILED]
See 'systemctl status systemd-journald.service' for details.
Dependency failed. Aborted start of Getty on tty1
[ ABORT]
Dependency failed. Aborted start of Serial Getty on ttyO0
[ ABORT]
Since this is a very early-on failure, nothing runs and I can't get in
to run the status command to figure out what's wrong. Perhaps there is
some way to get more verbose output to the console? I could edit some
config file, etc, offline an try another boot.
This build was for systemd-image, from a 100% scratch setup,
I'm in the same boat except I get access to the serial terminal in the end.
I'm new to systemd so I have to read a little bit about it. In the
meantime the suggested commands returns :
root@ixppci:~# systemctl status systemd-journald.service
Failed to get D-Bus connection: No connection to service manager.
My image is a modified version of systemd-image that uses a modified
version of task-basic which doesn't install the connection manager and
avahi. My image had to be smaller than 14MB to fit in a 16MB chip with
the Kernel (~2MB).
I'll keep you informed if I find anything.
I found out why my system was not coming up - it seems that the avahi
daemon (and dbus component) was not enabled. Looking at the systemd
setup, I found this:
/etc/systemd/system
/etc/systemd/system/sockets.target.wants
/etc/systemd/system/sockets.target.wants/dropbear.socket
/etc/systemd/system/basic.target.wants
/etc/systemd/system/basic.target.wants/timestamp.service
/etc/systemd/system/multi-user.target.wants
/etc/systemd/system/multi-user.target.wants/dropbearkey.service
/etc/systemd/system/multi-user.target.wants/connman.service
/etc/systemd/system/multi-user.target.wants/remote-fs.target
/etc/systemd/system/local-fs.target.wants
/etc/systemd/system/sysinit.target.wants
/etc/systemd/system/getty.target.wants
/etc/systemd/system/getty.target.wants/getty@tty1.service
/etc/systemd/system/getty.target.wants/serial-getty@ttyO0.service
I booted the system manually into just a shell and ran
sh-4.2# systemctl enable avahi-daemon.service
ln -s '/lib/systemd/system/avahi-daemon.service'
'/etc/systemd/system/dbus-org.freedesktop.Avahi.service'
ln -s '/lib/systemd/system/avahi-daemon.service'
'/etc/systemd/system/multi-user.target.wants/avahi-daemon.service'
ln -s '/lib/systemd/system/avahi-daemon.socket'
'/etc/systemd/system/sockets.target.wants/avahi-daemon.socket'
Now, it comes up to a prompt. I'll look into the build logs to figure
out why the avahi-daemon is not being enabled.
I see now in the build log:
Configuring avahi-daemon.
Configuring avahi-systemd.
avahi-systemd.postinst returned 1, marking as unpacked only, configuration
required on target.
But it doesn't look like this runtime initialization ever happened.
It seems that the script /etc/rcS.d/S98configure which is responsible
for running these postinst scripts is not being run at all. Any ideas why?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
_______________________________________________
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
