|
Bugzilla – Full Text Bug Listing |
| Summary: | systemd doesn't start dbus service | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 12.1 | Reporter: | Dave Plater <davejplater> |
| Component: | Basesystem | Assignee: | Frederic Crozat <fcrozat> |
| Status: | RESOLVED NORESPONSE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 12.1 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
boot.msg
syslog dmsg / system log Dmesg output product of "systemd --test > systemd.log" |
||
This problem is most probably caused by a stale file or permissions left over from 11.4 which used systemd (I should have reverted to systemV before upgrade) but I've searched bugs and sent messages with no help. I'm attaching boot.msg and messages. Created attachment 481583 [details]
boot.msg
Created attachment 481584 [details]
syslog
please install all available maintenance update and boot with "systemd.log_level=debug systemd.log_target=kmsg" and attach dmesg output. Created attachment 481614 [details]
dmsg / system log
This exercise has given me a possible way to work around but I would love to know what the problem is.
I tried starting dbus from tty1, which is outside of kde, after kde had come up and the "/var/run/dbus/system_bus_socket" message had appeared and I assume yast also operates outside of kde.
From this I assume that "rcdbus start" in after.local will start dbus?
I also had a problem with eth0 not starting (I don't use network manager) and I worked around that with "ifup eth0" in boot.local. I was able to start etho with ifup inside kde4.
I've installed update patches daily in the hope of a miracle and had just updated before I opened this bug.
forgot needinfo you did not attach dmesg output (more probably /var/log/messages). I need dmesg output after your rebooted with "systemd.log_level=debug systemd.log_target=kmsg". Created attachment 481627 [details]
Dmesg output
Sorry, hope this is fine, I did everything else and the kernel command line is permanent atm.
rcdbus start in after.local doesn't work but it does work in boot.local you have three dependency cycles : 9.924637] systemd[1]: Found ordering cycle on basic.target/start [ 9.945747] systemd[1]: Walked on cycle path to sockets.target/start [ 9.966852] systemd[1]: Walked on cycle path to dbus.socket/start [ 9.987732] systemd[1]: Walked on cycle path to sysinit.target/start [ 10.008337] systemd[1]: Walked on cycle path to network.service/start [ 10.028762] systemd[1]: Walked on cycle path to basic.target/start [ 10.048958] systemd[1]: Breaking ordering cycle by deleting job dbus.socket/start [ 10.069271] systemd[1]: Deleting job systemd-logind.service/start as dependency of job dbus.socket/start [ 10.069279] systemd[1]: Deleting job dbus.service/start as dependency of job dbus.socket/start [ 10.069284] systemd[1]: Deleting job avahi-daemon.service/start as dependency of job dbus.socket/start [ 10.069322] systemd[1]: Found ordering cycle on basic.target/start [ 10.089737] systemd[1]: Walked on cycle path to sysinit.target/start [ 10.110075] systemd[1]: Walked on cycle path to network.service/start [ 10.130133] systemd[1]: Walked on cycle path to basic.target/start [ 10.150071] systemd[1]: Breaking ordering cycle by deleting job network.service/start [ 10.170145] systemd[1]: Found ordering cycle on basic.target/start [ 10.190201] systemd[1]: Walked on cycle path to sysinit.target/start [ 10.210334] systemd[1]: Walked on cycle path to irq_balancer.service/start [ 10.230439] systemd[1]: Walked on cycle path to basic.target/start [ 10.250445] systemd[1]: Breaking ordering cycle by deleting job irq_balancer.service/start as a user, could you run : "systemd --test > systemd.log" and attach the file systemd.log Created attachment 481748 [details]
product of "systemd --test > systemd.log"
Note, dbus is running when test executed
my mistake, I was meaning, run as user (not root) : systemd --system --test > systemd.log and attach the log. is it still valid with latest systemd 12.1 update ? If yes, I need "systemd --system --test > systemd.log" and attach the log. no response for 9 months. Closing as noresponse |
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20100101 Firefox/10.0.2 After upgrading via dvd with extra multimedia repos enabled (I maintain multimedia) dbus fails to start when booting to runlevel 5 (kde4 kdm) and also cannot be started from a root (su) konsole but yast runlevel is able to start it, is this a permissions problem?: rcdbus status redirecting to systemctl dbus.service - D-Bus System Message Bus Loaded: loaded (/lib/systemd/system/dbus.service; static) Active: inactive (dead) CGroup: name=systemd:/system/dbus.service # rcdbus restart redirecting to systemctl Mar 15 12:38:07 Arbuthnot dbus-daemon[25486]: Failed to start message bus: No socket received. Mar 15 12:38:07 Arbuthnot systemd[1]: dbus.service: main process exited, code=exited, status=1 Mar 15 12:38:07 Arbuthnot systemd[1]: Unit dbus.service entered failed state. Mar 15 12:38:38 Arbuthnot su: (to root) davepl on /dev/pts/10 Mar 15 12:38:38 Arbuthnot su: pam_apparmor(su:session): Unknown error occurred changing to root hat: Operation not permitted Mar 15 12:38:38 Arbuthnot su: pam_systemd(su:session): Failed to connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory Mar 15 12:38:38 Arbuthnot su: (to root) davepl on /dev/pts/10 Mar 15 12:38:38 Arbuthnot su: pam_apparmor(su:session): Unknown error occurred changing to root hat: Operation not permitted Mar 15 12:38:38 Arbuthnot su: pam_systemd(su:session): Failed to connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory This is after starting with yast and my dvd drive appears as well. Mar 15 13:05:53 Arbuthnot dbus[26430]: [system] Activating service name='org.freedesktop.UPower' (using servicehelper) Mar 15 13:05:53 Arbuthnot dbus-daemon[26430]: dbus[26430]: [system] Activating service name='org.freedesktop.UPower' (using servicehelper) Mar 15 13:05:53 Arbuthnot dbus[26430]: [system] Successfully activated service 'org.freedesktop.UPower' Mar 15 13:05:53 Arbuthnot dbus-daemon[26430]: dbus[26430]: [system] Successfully activated service 'org.freedesktop.UPower' Mar 15 13:05:53 Arbuthnot dbus[26430]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper) Mar 15 13:05:53 Arbuthnot dbus-daemon[26430]: dbus[26430]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper) Mar 15 13:05:53 Arbuthnot polkitd[26476]: started daemon version 0.102 using authority implementation `local' version `0.102' Mar 15 13:05:53 Arbuthnot dbus[26430]: [system] Successfully activated service 'org.freedesktop.PolicyKit1' Mar 15 13:05:53 Arbuthnot dbus-daemon[26430]: dbus[26430]: [system] Successfully activated service 'org.freedesktop.PolicyKit1' Mar 15 13:05:53 Arbuthnot dbus-daemon[26430]: (upowerd:26472): UPower-Linux-WARNING **: failed to open /etc/crypttab: Failed to open file '/etc/crypttab': No such file or direct Reproducible: Always Steps to Reproduce: 1. 2. 3. I've googled "Failed to connect to socket /var/run/dbus/system_bus_socket and haven't found anything of real use, other distributions have had similar problems one solution is to reinstall ConsoleKit