View previous topic :: View next topic |
Author |
Message |
ese002 Tux's lil' helper
Joined: 20 Sep 2006 Posts: 143
|
Posted: Mon Dec 23, 2013 5:33 pm Post subject: [Solved] Systemd does not start d-bus or any other services |
|
|
I must be missing something basic bug I've gone over tons of postings and pages and I'm not seeing it.
I have a new systemd environment converted loosely from a working openrc setup. It boots clean which is to say, nothing is running.
systemctl won't do anything because it can't talk to D-BUS
I can see that dbus isn't running. I can start it with /etc/init.d/dbus but doesn't satisfy systemctl
I don't have any logs because syslog-ng isn't running. I can't start syslog-ng because I can't run systemctl.
Some articles that the problem is that I didn't start systemd from the kernel boot command line but I am:
kernel /vmlinuz-3.10.17-gentoo root=/dev/md22 init=/usr/lib/systemd/systemd resume=swap:/dev/md5 rootfstype=ext4 crashkernel=128M domdadm
I do notice a startup message from openrc on boot. This seems odd. Aren't systemd and openrc incompatible? But if I try to unmerge openrc I get a warning that openrc is required for my profile: default/linux/amd64/13.0/desktop/gnome/systemd
Last edited by ese002 on Tue Dec 24, 2013 1:20 am; edited 1 time in total |
|
Back to top |
|
|
DONAHUE Watchman
Joined: 09 Dec 2006 Posts: 7651 Location: Goose Creek SC
|
Posted: Mon Dec 23, 2013 8:20 pm Post subject: |
|
|
what gnome are you trying to run?
suggest visit https://wiki.gentoo.org/wiki/Systemd and check off point by point
Just for fun:
Code: | ls /usr/lib/systemd/system
systemctl enable dbus
systemctl start dbus |
_________________ Defund the FCC. |
|
Back to top |
|
|
ese002 Tux's lil' helper
Joined: 20 Sep 2006 Posts: 143
|
Posted: Mon Dec 23, 2013 8:59 pm Post subject: |
|
|
This is for gnome-3.8.0-r1, not that I'm getting that far.
systemctl enable dbus
The unit files have no [Install] section. They are not meant to be enabled
using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
_root@crab:/home/ericcrab eric # systemctl start dbus
Failed to get D-Bus connection: No connection to service manager.
_root@crab:/home/ericcrab eric # logout
I've been all over the wiki. It looks like systemd isn't starting at all which would normally mean that there is no init= pointing to systemd. I have that, so I'm rather confused. Could my initramfs somehow clear this? |
|
Back to top |
|
|
DONAHUE Watchman
Joined: 09 Dec 2006 Posts: 7651 Location: Goose Creek SC
|
Posted: Mon Dec 23, 2013 11:49 pm Post subject: |
|
|
boot cd, sysresccd if you have it, mount gentoo partitions, enter chroot, Code: | emerge wgetpaste
emerge --info | wgetpaste
wgetpaste /etc/portage/make.conf
wgetpaste /usr/src/linux/.config
ls -al /usr/lib/systemd/system | wgetpaste
lspci -nnk | wgetpaste | post the url's
did you roll your own initramfs or is it a genkernel product? _________________ Defund the FCC. |
|
Back to top |
|
|
ulenrich Veteran
Joined: 10 Oct 2010 Posts: 1480
|
Posted: Mon Dec 23, 2013 11:57 pm Post subject: |
|
|
cat /proc/cmdline
shows if your init from grub kernel line was kept
Adding to grub kernel line
systemd.unit=emergency.target
(or rescue.target, which additionally mounts rw)
can help you to diagnose further:
systemctl status dbus
journalctl -b
May be your kernel not has enabled options needed for systemd?
What initramfs creator do you use: dracut? |
|
Back to top |
|
|
ese002 Tux's lil' helper
Joined: 20 Sep 2006 Posts: 143
|
Posted: Tue Dec 24, 2013 1:20 am Post subject: |
|
|
It turns out, I needed to use "real_init=" instead of "init=" despite all the documentation that says to use "init=".
Now to figure out why networking and syslog-ng won't come up. The "detail" given by systemctl and journalctl is little more than "it failed" |
|
Back to top |
|
|
|