|
Bugzilla – Full Text Bug Listing |
| Summary: | boot stops with message "systemd don't start" | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 12.1 | Reporter: | Jean-Daniel Dodin <jdd> |
| Component: | Basesystem | Assignee: | Frederic Crozat <fcrozat> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | fcrozat |
| Version: | Factory | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
/var/log/message after successfull boot
messages with augmented logging messages with last zypper up /var/log/messages systemd debug system.conf fromp systemd dmesg with systemd debug |
||
|
Description
Jean-Daniel Dodin
2011-08-12 14:29:07 UTC
boot with systemd.log_target=kmsg systemd.log_level=debug on kernel cmdline and attach syslog (better to strip it before attaching it). Created attachment 445716 [details]
messages with augmented logging
I don't know in fact if systemd is guilty or if it's a totally different component. The computer is not really crashed or stopped, only the message displayed is frightening.
In fact it's enough to type Enter to get to the logging screen.
I can log with any user, (but can launch X only with root).
If I key in "init 5", gdm starts (surprising as init 5 is my default, usually issuing init 5 again don't do anything - at least with systemV init).
But I have no network, rcnetwork restart don't do anything and it seams I have no networkmanager
more soon!
I have the network with "normal" boot (without systemd) and did a zypper up, but this do not change the problem. That said, now, init 5 bdo NOT launch X. root startx do. but still with no network. Created attachment 445780 [details]
messages with last zypper up
August 15, I made zypper up -l and rebooted. No changes. I copy the message file (stripped to thre last boot).
As a side note (I don't know if this have anything related to the bug, but it come now), I had problems connecting to the net. I had to boot without systemd (usual with this bug), but then no network. rcnetwork restart still shows dhcp request not filled.
I got back the netwok removing the net cable plug and pluging it again.
since you copied /var/log/messages, you should use systemd.log_target=syslog-or-kmsg systemd.log_level=debug (kmsg alone is for using dmesg only). I have "LogTarget=syslog-or-kmsg" and "loglevel=debug" in /etc/systemd:system.conf, is that not what you want? - I just uncommented the options in the file (loglevel don't have a "_" in it, is this a problem?) I don't really understand what you mean "attach syslog", is that no /var/log/messages? thanks jdd You can either use options in /etc/systemd/system.conf or on kernel cmdline. But you didn't attach /var/log/messages generated with those options enabled. of course, I did! It's not easy as I have no network on this computer with systemd, I have to copy from screen or usb key. I will try with kernel line, not config file Created attachment 445985 [details]
/var/log/messages
This the todays /var/log/messages. you should find there login with config file debuf enabled, at least one boot without systemd and one boot with kernel option on command line
thanks
I tryed to add the systemd options in kernel command line (at the end): the boot stopped at 1.4s! I tried to remove systemd (zypper rm systemd) and reinstall it just in case, but no change. there is no systemd debug output in the file you attached. please try adding systemd.log_target=syslog-or-kmsg systemd.log_level=debug to kernel command line at boot time Created attachment 446012 [details]
systemd debug
this time I think we are...
I had to type the command in the grub menu.lst to get it (hand typing in kernel command line got crash, and there is a problem with the config file).
It was not that easy, because this computer is not booted by the factory grub but by 11.4 one, don't worry.
Sorry for the delay!
Created attachment 446015 [details]
system.conf fromp systemd
just to show the variables do not have the same syntax as command line ones, so I probably did not use the right syntax when modifying the file yesterday (this one is the original unmodifyed one)
just in case, the menu.lst entry:
title openSUSE factory (sda6 - 3.0 systemd)
root (hd0,5)
kernel /boot/vmlinuz root=/dev/disk/by-id/ata-WDC_WD5000BEVT-00ZAT0_WD-WXNY08N61636-part6 resume=/dev/disk/by-id/ata-IC35L120AVV207-0_VNVD06G4D2PX4L-part5 showopts vga=normal init=/bin/systemd systemd.log_target=syslog-or-kmsg systemd.log_level=debug
initrd /boot/initrd
unfortunately, the logs from /var/log/message are incomplete. We would need output from "dmesg" which are complete. But from what I see, systemd did boot the system properly.. Created attachment 446227 [details]
dmesg with systemd debug
here it is. first time I see that dmesg give more than /var/log/messages !
that said factory boots perfectly without the systemd option.
With systemd, I'm unable to make the network active. rcnetwork start do not makes eth up - only lo is visible in ifconfig. If I run ifconfig eth2 up, I have the interface but dhcp never get an adress (not tried to use fixed IP though).
So, with systemd, the boot stops before showing the console prompt (but no more at the systemd not started error), I have to type CR to get the prompt. There I can log, but I have to reboot without systemd to send this message :-(
in the attached dmesg, I see perfectly a networkmanager error, but I'm not able to understand it :-(
ok, you have the same issue than bnc#712300 it should be fixed with systemd-33-9 or later (available in Factory tonight or tomorrow). Reopen if it doesn't fix the issue. *** This bug has been marked as a duplicate of bug 712300 *** |