Re: DVD F14 -> F15 Problems
On Sunday, May 29, 2011 13:44:56 Garry T. Williams wrote: > I think the rpm database gets into a state that needs attention. This > fixed it: > > sudo rm -f /var/lib/rpm/__db.001 /var/lib/rpm/__db.002 \ > /var/lib/rpm/__db.003 /var/lib/rpm/__db.004 > sudo rpm --rebuilddb > > After that, yum operations sped up an order of magnitude. This is not a problem with rpm. The "work-around" above seemed to have fixed the poor performance, but it was back again after any update. The system was grinding away on lots of I/O. Upon further investigation, I think this was a btrfs bug. The problem does not reproduce since I updated to kernel-2.6.38.7-30.fc15.x86_64 from updates-testing. -- Garry Williams -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: DVD F14 -> F15 Problems
On Monday, May 30, 2011 06:44:39 He Rui wrote: > On Sun, 2011-05-29 at 13:44 -0400, Garry T. Williams wrote: > > I upgraded to F15 from F14 using the DVD yeterday. I experienced a > > few glitches: > > 3. The first boot ended at multiuser.target instead of > > graphical.target. > > I don't know why this happened with the DVD upgrade and not with the > > preupgrade upgrade. > > Was your default init level on Fedora-14 3? No. It was 5 on both systems. > Then if you changed the > default runlevel by modifying the file /etc/inittab, those changes > wouldn't affect the configured systemd default target. No, I never touched inittab on either system. The DVD upgrade just installed with multiuser.target as the default for some reason. Although strange, it was no problem correcting it. -- Garry Williams -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: DVD F14 -> F15 Problems
On Sun, 2011-05-29 at 13:50 -0400, Garry T. Williams wrote: > On Sunday, May 29, 2011 13:44:56 Garry T. Williams wrote: > > I upgraded to F15 from F14 using the DVD yeterday. I experienced a > > few glitches: > > 6. Oh, I forgot to mention that there was no operating system log after > the upgrade. That one was fixed with this: > > sudo systemctl enable rsyslog.service > > -- Thanks, it's a known issue: https://bugzilla.redhat.com/show_bug.cgi?id=699198 -- Contacts Hurry FAS Name: Rhe Timezone: UTC+8 TEL: 86-010-62608141 IRC nick: rhe #fedora-qa #fedora-zh -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: DVD F14 -> F15 Problems
On Sun, 2011-05-29 at 13:44 -0400, Garry T. Williams wrote: > I upgraded to F15 from F14 using the DVD yeterday. I experienced a > few glitches: > > 1. I was not asked to include the updates repository during the > update process. Sad. Now I will have to do an update after first > boot. > > 2. This is apparently a general problem not really related to the > specific upgrade. I noticed that the upgrade process was slow. The > disk just churned forever. After booting for the first time, I ran > yum erase on my debuginfos so that the subsequent yum update would not > pull those in. This erase command took way too long. > > I think the rpm database gets into a state that needs attention. This > fixed it: > > sudo rm -f /var/lib/rpm/__db.001 /var/lib/rpm/__db.002 \ > /var/lib/rpm/__db.003 /var/lib/rpm/__db.004 > sudo rpm --rebuilddb > > After that, yum operations sped up an order of magnitude. > > 3. The first boot ended at multiuser.target instead of > graphical.target. When I entered the command > > sudo systemctl isolate graphical.target > > kdm came up and allowed a normal desktop login. > > Hmmm. I compared another system that I upgraded using preupgrade and > that one had the correct graphical.target file linked in > /etc/systemd/system . So I had to do this to correct the problem: > > sudo rm /etc/systemd/system/default.target > sudo ln -s /lib/systemd/system/runlevel5.target \ > /etc/systemd/system/default.target > > I don't know why this happened with the DVD upgrade and not with the > preupgrade upgrade. > Was your default init level on Fedora-14 3? Then if you changed the default runlevel by modifying the file /etc/inittab, those changes wouldn't affect the configured systemd default target. See https://fedoraproject.org/wiki/Common_F15_bugs#Graphical_login_does_not_start_after_upgrade Thanks, Hurry -- Contacts Hurry FAS Name: Rhe Timezone: UTC+8 TEL: 86-010-62608141 IRC nick: rhe #fedora-qa #fedora-zh -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: DVD F14 -> F15 Problems
On Sunday, May 29, 2011 13:44:56 Garry T. Williams wrote: > I upgraded to F15 from F14 using the DVD yeterday. I experienced a > few glitches: 6. Oh, I forgot to mention that there was no operating system log after the upgrade. That one was fixed with this: sudo systemctl enable rsyslog.service -- Garry Williams -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
DVD F14 -> F15 Problems
I upgraded to F15 from F14 using the DVD yeterday. I experienced a few glitches: 1. I was not asked to include the updates repository during the update process. Sad. Now I will have to do an update after first boot. 2. This is apparently a general problem not really related to the specific upgrade. I noticed that the upgrade process was slow. The disk just churned forever. After booting for the first time, I ran yum erase on my debuginfos so that the subsequent yum update would not pull those in. This erase command took way too long. I think the rpm database gets into a state that needs attention. This fixed it: sudo rm -f /var/lib/rpm/__db.001 /var/lib/rpm/__db.002 \ /var/lib/rpm/__db.003 /var/lib/rpm/__db.004 sudo rpm --rebuilddb After that, yum operations sped up an order of magnitude. 3. The first boot ended at multiuser.target instead of graphical.target. When I entered the command sudo systemctl isolate graphical.target kdm came up and allowed a normal desktop login. Hmmm. I compared another system that I upgraded using preupgrade and that one had the correct graphical.target file linked in /etc/systemd/system . So I had to do this to correct the problem: sudo rm /etc/systemd/system/default.target sudo ln -s /lib/systemd/system/runlevel5.target \ /etc/systemd/system/default.target I don't know why this happened with the DVD upgrade and not with the preupgrade upgrade. 4. I then did a yum update and waited a few hours while over 500 packages were downloaded and updated/installed. This was almost 1GB of downloads. Most packages did not have delta rpms. 5. I run KDE and after logging in and starting Kmail, it refused to start, complaining about akonadi not being available: Test 5: ERROR ... InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. Test 10: ERROR ... Akonadi control process not registered at D-Bus. Test 15: ERROR ... No resource agents found. (Wow, this is a fragile piece in kdepim.) The fix for this ended up being: sudo yum --enablerepo=kde-testing update Now the system is operating as expected and all looks good. I'd be happy to open any bugs any of you think should be reported, but I think others have already encountered most of this stuff. Thank you for another excellent Fedora release. -- Garry Williams -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
