Latest updates, system never completes boot process.

[glennzo]

It seems that the latest round of updates may have hosed my F15 Alpha install. All was well last night but couldn't finish booting the system this morning. So, since I don't really give a hoot about any of my systems I did a complete reinstall of F15A and then a full yum update. Rebooted and again can't complete the boot. Never reaches the desktop. Maybe I should go get some details but meanwhile, anyone else having issues booting Fedora 15 Alpha this fine morning?

[flokip]

See http://lists.fedoraproject.org/piper...ch/097931.html
"Alternatively, reset your system, boot into runlevel 1, start networking
(systemctl start network.service), yum downgrade rsyslog, and reboot."

[Fenrin]

tuxor posted two solutions in this thread: http://forums.fedoraforum.org/showth...=259897&page=4

[Boricua]

See http://lists.fedoraproject.org/piper...ch/097931.html
"Alternatively, reset your system, boot into runlevel 1, start networking
(systemctl start network.service), yum downgrade rsyslog, and reboot."

Hi, I tried this one and worked, thanks . This happened to me with a Thinkpad T60 and suffered exactly the same fate as the original poster. After the recent updates and before this incident I was having some difficulties shouting down the machine, forcing me to force it. Nos sure if it's related.

[glennzo]

Yes, I have to force shutdown also.

OK. Flokip's suggestion worked for me. I was his suggestion, no? Anyhow, I booted to runlevel 1, started networking and downgraded rsyslog and rebooted. Here I am. Thank you Flokip.

[kiddokun]

I have a problem... I am unable to start networking. And I obviously can't run "yum downgrade rsyslog" without a network connection.

I tried "ifup eth0" and "dhclient eth0", but they fail since there is no eth0. When I do a "ifconfig", I only see "lo". I also tried "sysctl start networking.service" to no avail.

I'm stumped. Ideas?

[tox]

im also finding Systemd or whatever it is does not always complete loading of all services

[Lebenskuenstler]

I have a problem... I am unable to start networking. And I obviously can't run "yum downgrade rsyslog" without a network connection.

I tried "ifup eth0" and "dhclient eth0", but they fail since there is no eth0. When I do a "ifconfig", I only see "lo". I also tried "sysctl start networking.service" to no avail.

I'm stumped. Ideas?

Hi,

use the LiveCD or Netinst in Rescue-Mode.

In both cases, you will have to mount your root partition with something like this

mount /dev/mapper/vg_XYZ_root /mnt

and then

chroot /mnt

then

yum downgrade rsyslog


LK

[GoinEasy9]

Isn't this the same problem that was talked about in this thread from post 49 to the end? If you add "systemd.unit=rescue.target" to the end of the kernel line in grub it boots, then executing:
# grep rsyslogd /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp
allows F15 to boot normally again. Saves the hassle of downgrading.

[kiddokun]

Lebenskuenstler's solution above worked for me. I booted the F15 alpha livecd, used nautilus to mount temporarily my / partition, chrooted into it and ran "yum downgrade rsyslog". The system now boots. Hurray!

[Ard Righ]

I have a problem... I am unable to start networking. And I obviously can't run "yum downgrade rsyslog" without a network connection.

I tried "ifup eth0" and "dhclient eth0", but they fail since there is no eth0. When I do a "ifconfig", I only see "lo". I also tried "sysctl start networking.service" to no avail.

I'm stumped. Ideas?

Fedora 15 Alpha renames the connections on my PC.

Have a look in /etc/sysconfig/network-scripts/ for the ifcfg-* files.

Mine get renamed to something like "pc8ia" or something wierd

I am not sure but it does this during the bootup process. You can also look through 'dmesg' log to see what happens with the network service

generally 'ifup pc8ia' works on my machine (using the newly renamed config)

[DCOH]

It seems to be caused by selinux. Test list says to set selinux to permissive and it will boot up.

[tuxor]

It's only indirectly caused by selinux. Actually it has its origin in systemd and rsyslog.

[bbfuller]

Thank goodness for this thread!

Quite takes you back to the old times when main Fedora was really cutting edge doesn't it.

[smr54]

Hrrm, unneeded, over complicated things that break the basics? Yeah, it does.