Bug#619000: [systemd] SystemD fails to start system, hangs at Logging Daemon...
Hi Florian, I was looking through some old bugs, and was wondering if you still encounter this issue on a recent sid/wheezy system with systemd 44-5? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#619000: [systemd] SystemD fails to start system, hangs at Logging Daemon...
Package: systemd Version: 19-1 Severity: normal --- Please enter the report below this line. --- Today I wanted to take a look at systemd and was stopped early. At first it look as if systemd hung after cryptsetup from initrd but after using some kernel command line options to increase the verbosity of systemd I found that systemd hung when starting rsyslog (if I interpret Logging Daemon correctly). Here are the last lines: Starting /tmp... Starting Remoount API VFS... Starting Runtime Directory... Starting File System Check on Root Device... Starting Lock Directory... Starting Logging Daemon... I then pressed Ctrl-Alt-Del, which lead to console fonts and keymap initialization and some error messages. --- System information. --- Architecture: amd64 Kernel: Linux 2.6.38-1-amd64 Debian Release: wheezy/sid 500 unstablewww.debian-multimedia.org 500 unstableftp.de.debian.org 500 testing ftp.de.debian.org 100 experimental-snapshots qt-kde.debian.net 1 experimentalftp.de.debian.org --- Package information. --- Depends(Version) | Installed -+-== libaudit0| 1.7.13-1+b2 libc6 (= 2.10) | 2.11.2-13 libcap2(= 2.10) | 1:2.20-1 libcryptsetup1(= 2:1.2) | 2:1.2.0-2 libdbus-1-3 (= 1.1.1) | 1.4.6-1 libpam0g (= 0.99.7.1) | 1.1.2-2 libselinux1 (= 2.0.65) | 2.0.96-1 libudev0(= 154) | 166-1 util-linux (= 2.17.2-5) | 2.17.2-9.1 Recommends (Version) | Installed =-+-=== libpam-systemd| 19-1 Suggests (Version) | Installed ==-+-=== systemd-gui| 19-1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#619000: [systemd] SystemD fails to start system, hangs at Logging Daemon...
Am 20.03.2011 12:33, schrieb Florian Kriener: Package: systemd Version: 19-1 Severity: normal --- Please enter the report below this line. --- Today I wanted to take a look at systemd and was stopped early. At first it look as if systemd hung after cryptsetup from initrd but after using some kernel command line options to increase the verbosity of systemd I found that systemd hung when starting rsyslog (if I interpret Logging Daemon correctly). Here are the last lines: Starting /tmp... Starting Remoount API VFS... Starting Runtime Directory... Starting File System Check on Root Device... Starting Lock Directory... Starting Logging Daemon... I then pressed Ctrl-Alt-Del, which lead to console fonts and keymap initialization and some error messages. Do you have any special setup (cryptsetup, LVM, partition layout like /usr on a separate partition)? Could you boot with systemd.log_level=debug and systemd.log_target=kmsg please and check if that reveals more. It's most likely not a rsyslog related issue. Logging Daemon is systemd's internal logger service provided by systemd-logger.service. My guess is that systemd is waiting for some devices to show up. You could wait for at least a minute to wait for the timeout and check if the boot process continues. If you then can login, check the status with systemctl list-jobs and systemctl --full --all | grep failed. If you are able to connect to your system via a serial console to the a full log of the boot process, that would be most helpful. Michael Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#619000: [systemd] SystemD fails to start system, hangs at Logging Daemon...
On Sunday 20 March 2011 13:12:26 Michael Biebl wrote: Do you have any special setup (cryptsetup, LVM, partition layout like /usr on a separate partition)? My setup is this: One hdd with two partitions sda1: /boot, ext2 sda2: luks encrypted with lvm on top and two lvs for / and /home, both ext4 Could you boot with systemd.log_level=debug and systemd.log_target=kmsg please and check if that reveals more. It's most likely not a rsyslog related issue. Logging Daemon is systemd's internal logger service provided by systemd-logger.service. You are right. This has nothing to to with rsyslog. The kernel command line I used was the above and it did not show more. However... My guess is that systemd is waiting for some devices to show up. You could wait for at least a minute to wait for the timeout and check if the boot process continues. If you then can login, check the status with systemctl list-jobs and systemctl --full --all | grep failed. I took your advice went for a shower and a shave after fiering up a systemd boot. When I came back I found, that there must have been some timeout and the boot process had continued. However, the next message wasn't very comforting: Apparently systemd failed to start udev. The rest of the messages was more or less irrelevant and I don't remember them. Logging in was not possible. If you are able to connect to your system via a serial console to the a full log of the boot process, that would be most helpful. Sadly, that is not possible as my notebook misses a serial interface. But I could present you with some hand made screen captures (aka digital still images) if that could help you. I don't see a lot of usefull stuff though. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#619000: [systemd] SystemD fails to start system, hangs at Logging Daemon...
Am 20.03.2011 14:34, schrieb Florian Kriener: On Sunday 20 March 2011 13:12:26 Michael Biebl wrote: Do you have any special setup (cryptsetup, LVM, partition layout like /usr on a separate partition)? My setup is this: One hdd with two partitions sda1: /boot, ext2 sda2: luks encrypted with lvm on top and two lvs for / and /home, both ext4 Any special cryptsetup options? Or is this a standard LVM+cryptsetup installation as setup by the debian-installer? In your initial email you had Starting /tmp... which looks like /tmp would be on a different partition? Could you boot with systemd.log_level=debug and systemd.log_target=kmsg please and check if that reveals more. It's most likely not a rsyslog related issue. Logging Daemon is systemd's internal logger service provided by systemd-logger.service. You are right. This has nothing to to with rsyslog. The kernel command line I used was the above and it did not show more. However... Have your removed quiet from the command line? with systemd.log_level=debug you should get a a *lot* more output. My guess is that systemd is waiting for some devices to show up. You could wait for at least a minute to wait for the timeout and check if the boot process continues. If you then can login, check the status with systemctl list-jobs and systemctl --full --all | grep failed. I took your advice went for a shower and a shave after fiering up a systemd boot. When I came back I found, that there must have been some timeout and the boot process had continued. However, the next message wasn't very comforting: Apparently systemd failed to start udev. The rest of the messages was more or less irrelevant and I don't remember them. Logging in was not possible. If you are able to connect to your system via a serial console to the a full log of the boot process, that would be most helpful. Sadly, that is not possible as my notebook misses a serial interface. But I could present you with some hand made screen captures (aka digital still images) if that could help you. I don't see a lot of usefull stuff though. Try to explain in as much detail as possible how your installation differs from a standard installation, and custom configurations. Having screenshots of the boot process would be fine. Don't forget to get as much of the scrollback as possible. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#619000: [systemd] SystemD fails to start system, hangs at Logging Daemon...
]] Florian Kriener | Having screenshots of the boot process would be fine. Don't forget to | get as much of the scrollback as possible. | | Here you go, beautifully assembled console picture. :-) Thanks for this. Which version of the lvm2 package do you have installed? regards, -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#619000: [systemd] SystemD fails to start system, hangs at Logging Daemon...
Am 20.03.2011 20:22, schrieb Tollef Fog Heen: ]] Florian Kriener | Having screenshots of the boot process would be fine. Don't forget to | get as much of the scrollback as possible. | | Here you go, beautifully assembled console picture. :-) Thanks for this. Which version of the lvm2 package do you have installed? Given that systemd 19-1 has Breaks against older versions of lvm2, I think the version should be recent enough. There might be an issue with initrd not being up-to-date (Florian, could you try to run update-initramfs -u), but I somehow doubt that But seeing that even the ttys fail to start and the udev.service times out, I'm wondering if it isn't actually a udev related problem. Florian, how exactly did you tweak your initramfs? Do you have any custom udev rules/configuration? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#619000: [systemd] SystemD fails to start system, hangs at Logging Daemon...
On Sunday 20 March 2011 20:50:14 you wrote:
Which version of the lvm2 package do you have installed?
Given that systemd 19-1 has Breaks against older versions of lvm2, I
think the version should be recent enough.
Thats right, it's 2.02.84-2.
There might be an issue
with initrd not being up-to-date (Florian, could you try to run
update-initramfs -u), but I somehow doubt that.
I'll try that, but I recently installed 2.6.38, so it should be okay.
But seeing that even the ttys fail to start and the udev.service
times out, I'm wondering if it isn't actually a udev related
problem.
Florian, how exactly did you tweak your initramfs?
Do you have any custom udev rules/configuration?
What I did to the initramfs is hardly called tweaking, I just put the
string i915 into /etc/initramfs-tools/modules. It's the only
uncommented string in there.
I don't have custom udev rules and udev works fine so far. The only
problem is, that the hp driver generates some warnings at startup
(SYSFS={} will be removed ...). However, I do not see these warnings,
when I boot with systemd but maybe the corresponding rules get loaded
later.
What I am wondering about is that I do not see a line saying Starting
LVM. I was expecting something along those lines, since vgchange -a y
should be run quite early.
And then there is this thread on the systemd-devel list [1]. I don't
know how that is related, but the solution there does not work for me
(using the lvm.service file from [2]).
[1] http://thread.gmane.org/gmane.comp.sysutils.systemd.devel/1272
[2] http://article.gmane.org/gmane.linux.lvm.devel/6138
Cheers,
Florian.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
