Just updated one box without a hitch. Second box has been churning for about 3 hours. By the log on the monitor, I am uup to about 16000 commands????? I am beginning to believe that I am in a mess.
Just updated one box without a hitch. Second box has been churning for about 3 hours. By the log on the monitor, I am uup to about 16000 commands????? I am beginning to believe that I am in a mess.
I presume you did the update by clicking the "Start Upgrade" button on the VB GUI Upgrade page (http://vortexbox/upgrade.php).
Click the "View full log" button on the Upgrade page.
How many packages is the upgrade trying to install?
Is it still installing packages? Cleaning up after the install?
How far has it gotten?
What are the last lines in the log file?
Hard to tell from if the update is hung or if you just have a ton of packages to update and it's taking a long time.
Ron Olsen said:
Also, if your VB is up to date, and you rebooted after the last update, your VB should be running the 3.1.5-6 kernel. Check with "uname -r".
Update:
Everything appears to be working correctly with my VBA, EXCEPT the kernel will not update from 3.1.0-7. *A newer was installed (3.1.5-2) but it would not boot in it. *I removed the newer kernel and did a "yum clean all; yum update" to no avail. *I also tried "yum update kernel" which gave the message "Package(s) kernel available, but not installed."
Some users on a Fedora forum are reporting similar stories about being "stuck" in 3.1.0-7. *So, I think I will have to do a clean ISO install.
The "quick install guide" seems dated, but I have only one question (never done this before):
What will my VBA do when I insert the ISO disc? *Obviously it won't be able to rip it, which it will of course try to do! *Will it automatically boot from the CD upon rebooting?
Marcel
You shouldn't have to do a clean ISO install to fix this problem.
Also, the latest kernel is kernel-PAE-3.1.5-6, not 3.1.5-2.
Try updating your VB again; then enter
rpm -q kernel-PAE
to list the installed kernels.
On my up-to-date VBA, this gives
kernel-PAE-3.1.5-1.fc16.i686
kernel-PAE-3.1.5-2.fc16.i686
kernel-PAE-3.1.5-6.fc16.i686
So upgrade your VBA and see if you get the 3.1.5-6 kernel installed.
If that doesn't work, try
yum install kernel-PAE
If this works, then reboot to see if the VB comes up with this kernel.
If you're still having problems booting the latest kernel, the wiki page*http://fedoraproject.org/wiki/Grub2has info that should help:
1. Find the names of the kernels are available:
grep menuentry /boot/grub2/grub.cfg
On my VBA, this outputs
menuentry 'Fedora (3.1.5-6.fc16.i686.PAE)' –class fedora –class gnu-linux –class gnu –class os {
menuentry 'Fedora (3.1.5-2.fc16.i686.PAE)' –class fedora –class gnu-linux –class gnu –class os {
menuentry 'Fedora (3.1.5-1.fc16.i686.PAE)' –class fedora –class gnu-linux –class gnu –class os {
2. Set the newest kernel as the default:
grub2-set-default 'Fedora (3.1.5-6.fc16.i686.PAE)'
Use the newest kernel in the list of menuentries in this command.
3. Then reboot and see if it uses the new default kernel.
Further research shows that setting the default kernel does not work; here is a bug report: https://bugzilla.redhat.com/show_bug.cgi?id=732058
If you have a monitor and keyboard attached to your VB, try pressing the DEL key when you reboot. That should take you into the GRUB2 menu, where you can select the kernel you want to boot. Try that and see if it allows you to boot the newest kernel.
I've updated a dozen times over the past 2 days, both from the command line and from the GUI, and I've gotten some vortexbox and samba package updates, but no fedora updates.
Prior to to-day "rpm -q kernel-PAE" produced 3.1.0-7 and 3.1.5-2. *I removed the latter (thinking that perhaps it was corrupted thus Fedora was booting into 3.1.0-7) as earlier reported, so now I just have a single kernel:[vortexbox.localdomain ~]# rpm -q kernel-PAE
kernel-PAE-3.1.0-7.fc16.i686[vortexbox.localdomain ~]# yum install kernel-PAE
Loaded plugins: langpacks, presto, refresh-packagekit
Setting up Install Process
Package kernel-PAE-3.1.0-7.fc16.i686 already installed and latest version
Nothing to do
[vortexbox.localdomain ~]# grep menuentry /boot/grub2/grub.cfg
menuentry 'Fedora (3.1.0-7.fc16.i686.PAE)' --class fedora --class gnu-linux*--class gnu --class os {
*
I have the ISO downloaded, and noticed that it contains 3.1.2-1. *Seems odd (or maybe not) that the command-line preupgrade process installed 3.1.0 when a newer kernel was already available.
I think the trick will be "forcing" a download of the fedora and/or updates repository.
Marcel
Looks as if yum is not searching the Fedora Updates repository.
What does
show?Code:yum repolist
[vortexbox.localdomain ~]# yum repolist
Loaded plugins: langpacks, presto, refresh-packagekit
repo id repo name status
atrpms Fedora 16 - i386 - ATrpms 654
fedora Fedora 16 - i386 20,176
updates Fedora 16 - i386 - Updates 3,640+12
vortexbox Packages for VortexBox 42
repolist: 24,512*
The repolist looks good.
What does
show?Code:yum clean all; yum list kernel-PAE
What does
show?Code:cat /etc/yum.conf
[vortexbox.localdomain ~]# yum clean all; yum list kernel-PAE
Loaded plugins: langpacks, presto, refresh-packagekit
Cleaning repos: atrpms fedora updates vortexbox
Cleaning up Everything
No delta-package files removed by presto
Loaded plugins: langpacks, presto, refresh-packagekit
atrpms | 3.5 kB 00:00
atrpms/primary_db | 462 kB 00:02
fedora/metalink | 22 kB 00:00
fedora | 4.2 kB 00:00
fedora/primary_db | 12 MB 00:34
fedora/group_gz | 431 kB 00:01
updates/metalink | 15 kB 00:00
updates | 4.7 kB 00:00
updates/primary_db | 2.6 MB 00:04
updates/group_gz | 431 kB 00:01
vortexbox | 3.6 kB 00:00
vortexbox/primary_db | 49 kB 00:00
vortexbox/group_gz | 1.0 kB 00:00
Loaded plugins: langpacks, presto, refresh-packagekit
Installed Packages
kernel-PAE.i686 3.1.0-7.fc16 installed*[vortexbox.localdomain ~]# cat /etc/yum.conf
[main]
cachedir=/var/cache/yum/$basearch/$releasever
keepcache=0
debuglevel=2
logfile=/var/log/yum.log
exactarch=1
obsoletes=1
gpgcheck=1
plugins=1
installonly_limit=3
# This is the default, if you make this bigger yum won't see if the metadata
# is newer on the remote and so you'll "gain" the bandwidth of not having to
# download the new metadata and "pay" for it by yum not having correct
# information.
# It is esp. important, to have correct metadata, for distributions like
# Fedora which don't keep old packages around. If you don't like this checking
# interupting your command line usage, it's much better to have something
# manually check the metadata once an hour (yum-updatesd will do this).
# metadata_expire=90m
# PUT YOUR REPOS HERE OR IN separate files named file.repo
# in /etc/yum.repos.d*
Posting Permissions
Reply With Quote
Bookmarks