After installing 4.1, and running yum clean all yum list yum update
It hangs at the point
<snip> (52/57): cups-libs-1.1.22 100% |=========================| 109 kB 00:00 (53/57): bzip2-devel-1.0. 100% |=========================| 35 kB 00:00 (54/57): kdelibs-3.3.1-3. 100% |=========================| 15 MB 00:00 (55/57): zlib-devel-1.2.1 100% |=========================| 94 kB 00:00 (56/57): mod_ssl-2.0.52-1 100% |=========================| 100 kB 00:00 (57/57): fetchmail-6.2.5- 100% |=========================| 581 kB 00:00 Running Transaction Test </snip>
It just sits there. I can ping the box, but I cannot ssh to the box. I can not log into the console either.
On Mon, 22 Aug 2005, Robin Mordasiewicz wrote:
After installing 4.1, and running yum clean all yum list yum update
It hangs at the point
<snip> (52/57): cups-libs-1.1.22 100% |=========================| 109 kB 00:00 (53/57): bzip2-devel-1.0. 100% |=========================| 35 kB 00:00 (54/57): kdelibs-3.3.1-3. 100% |=========================| 15 MB 00:00 (55/57): zlib-devel-1.2.1 100% |=========================| 94 kB 00:00 (56/57): mod_ssl-2.0.52-1 100% |=========================| 100 kB 00:00 (57/57): fetchmail-6.2.5- 100% |=========================| 581 kB 00:00 Running Transaction Test </snip>
It just sits there. I can ping the box, but I cannot ssh to the box. I can not log into the console either.
I installed Centos 4 on another machine and it also hangs, but it hangs at..
(54/57): kdelibs-3.3.1-3. 100% |=========================| 15 MB 00:00 (55/57): zlib-devel-1.2.1 100% |=========================| 94 kB 00:00 (56/57): mod_ssl-2.0.52-1 100% |=========================| 100 kB 00:00 (57/57): fetchmail-6.2.5- 100% |=========================| 581 kB 00:00 Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Updating: zlib 100 % done 1/114
and again this new machine becomes unrepsonsive, but it looks like it has not hung, rather seems to be out of resources. Both of these machines worked fine under Centos 3
I've had this exact same problem, and I uninstalled yum reinstalled it and it work for a day and then back to the same. I've also had it working temporarily by doing a yum clean-all then yum makecache. But next day it went back to doing the same old hang up. I'm not sure if this is a yum problem or a centos problem.
On Mon, 2005-08-22 at 00:28 -0400, Robin Mordasiewicz wrote:
On Mon, 22 Aug 2005, Robin Mordasiewicz wrote:
After installing 4.1, and running yum clean all yum list yum update
It hangs at the point
<snip> (52/57): cups-libs-1.1.22 100% |=========================| 109 kB 00:00 (53/57): bzip2-devel-1.0. 100% |=========================| 35 kB 00:00 (54/57): kdelibs-3.3.1-3. 100% |=========================| 15 MB 00:00 (55/57): zlib-devel-1.2.1 100% |=========================| 94 kB 00:00 (56/57): mod_ssl-2.0.52-1 100% |=========================| 100 kB 00:00 (57/57): fetchmail-6.2.5- 100% |=========================| 581 kB 00:00 Running Transaction Test </snip>
It just sits there. I can ping the box, but I cannot ssh to the box. I can not log into the console either.
I installed Centos 4 on another machine and it also hangs, but it hangs at..
(54/57): kdelibs-3.3.1-3. 100% |=========================| 15 MB 00:00 (55/57): zlib-devel-1.2.1 100% |=========================| 94 kB 00:00 (56/57): mod_ssl-2.0.52-1 100% |=========================| 100 kB 00:00 (57/57): fetchmail-6.2.5- 100% |=========================| 581 kB 00:00 Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Updating: zlib 100 % done 1/114
and again this new machine becomes unrepsonsive, but it looks like it has not hung, rather seems to be out of resources. Both of these machines worked fine under Centos 3 _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I've had this exact same problem, and I uninstalled yum reinstalled it and it work for a day and then back to the same. I've also had it working temporarily by doing a yum clean-all then yum makecache. But next day it went back to doing the same old hang up. I'm not sure if this is a yum problem or a centos problem.
I was having this exact issue recently. Or at least, Yum was hanging at the same stage as what you describe.
It was recommended to me on this list to do the following:
cd /var/lib/rpm rm __db.00* rpm --rebuilddb
This seems to have cleared up the problem for me. It might work for you.
I'm a newbie though, so maybe I'm missing the mark on what your problem is. I hope it helps, though.
Dave
On Mon, 22 Aug 2005, Dave Gutteridge wrote:
I've had this exact same problem, and I uninstalled yum reinstalled it and it work for a day and then back to the same. I've also had it working temporarily by doing a yum clean-all then yum makecache. But next day it went back to doing the same old hang up. I'm not sure if this is a yum problem or a centos problem.
I was having this exact issue recently. Or at least, Yum was hanging at the same stage as what you describe.
It was recommended to me on this list to do the following:
cd /var/lib/rpm rm __db.00* rpm --rebuilddb
This seems to have cleared up the problem for me. It might work for you.
Are you running x86_64 ? Or is anyone here running x86_64 CentOS 4 and having success with yum update ?
On Mon, 2005-08-22 at 13:02 -0400, Robin Mordasiewicz wrote:
On Mon, 22 Aug 2005, Dave Gutteridge wrote:
I've had this exact same problem, and I uninstalled yum reinstalled it and it work for a day and then back to the same. I've also had it working temporarily by doing a yum clean-all then yum makecache. But next day it went back to doing the same old hang up. I'm not sure if this is a yum problem or a centos problem.
I was having this exact issue recently. Or at least, Yum was hanging at the same stage as what you describe.
It was recommended to me on this list to do the following:
cd /var/lib/rpm rm __db.00* rpm --rebuilddb
This seems to have cleared up the problem for me. It might work for you.
Are you running x86_64 ? Or is anyone here running x86_64 CentOS 4 and having success with yum update ? _______________________________________________
I run x86_64 with no problems ...
What kind of install is it, Workstation or Server?
After the upgrade where RPM is upgraded, it is actually a good idea to rebuild the database.
The machine I use to autobuild all updates is an x86_64 machine that runs with 6 chroots.
On Mon, 22 Aug 2005, Johnny Hughes wrote:
On Mon, 2005-08-22 at 13:02 -0400, Robin Mordasiewicz wrote:
On Mon, 22 Aug 2005, Dave Gutteridge wrote:
I've had this exact same problem, and I uninstalled yum reinstalled it and it work for a day and then back to the same. I've also had it working temporarily by doing a yum clean-all then yum makecache. But next day it went back to doing the same old hang up. I'm not sure if this is a yum problem or a centos problem.
I was having this exact issue recently. Or at least, Yum was hanging at the same stage as what you describe.
It was recommended to me on this list to do the following:
cd /var/lib/rpm rm __db.00* rpm --rebuilddb
This seems to have cleared up the problem for me. It might work for you.
Are you running x86_64 ? Or is anyone here running x86_64 CentOS 4 and having success with yum update ?
I run x86_64 with no problems ... What kind of install is it, Workstation or Server? After the upgrade where RPM is upgraded, it is actually a good idea to rebuild the database. The machine I use to autobuild all updates is an x86_64 machine that runs with 6 chroots.
The install was a kickstart install with mostly defaults. I dont think you can specify server/desktop variations in the kickstart, and I dont know if that would make a difference, other than default package selection ?
I did a default install from the DVD and it should not make the mahcine useless to run "yum update"
I would like to figure out what it is that is broken. I am not an expert in this field, and having troubles narrowing it down.
It is definitely not faulty hardware, although it could be hardware incompatibilities, but CentOS-3 worked perfectly fine.
On Mon, 2005-08-22 at 13:22 -0400, Robin Mordasiewicz wrote:
On Mon, 22 Aug 2005, Johnny Hughes wrote:
On Mon, 2005-08-22 at 13:02 -0400, Robin Mordasiewicz wrote:
On Mon, 22 Aug 2005, Dave Gutteridge wrote:
I've had this exact same problem, and I uninstalled yum reinstalled it and it work for a day and then back to the same. I've also had it working temporarily by doing a yum clean-all then yum makecache. But next day it went back to doing the same old hang up. I'm not sure if this is a yum problem or a centos problem.
I was having this exact issue recently. Or at least, Yum was hanging at the same stage as what you describe.
It was recommended to me on this list to do the following:
cd /var/lib/rpm rm __db.00* rpm --rebuilddb
This seems to have cleared up the problem for me. It might work for you.
Are you running x86_64 ? Or is anyone here running x86_64 CentOS 4 and having success with yum update ?
I run x86_64 with no problems ... What kind of install is it, Workstation or Server? After the upgrade where RPM is upgraded, it is actually a good idea to rebuild the database. The machine I use to autobuild all updates is an x86_64 machine that runs with 6 chroots.
The install was a kickstart install with mostly defaults. I dont think you can specify server/desktop variations in the kickstart, and I dont know if that would make a difference, other than default package selection ?
Just wondering if you are installing a bunch of i386 stuff (Open Office, etc., or mostly just x86_64 stuff) It shouldn't matter, you should be able to install packages and upgrade all the items with no issues.
I did a default install from the DVD and it should not make the mahcine useless to run "yum update"
That is true ... useless machines are not part of our goals :)
I would like to figure out what it is that is broken. I am not an expert in this field, and having troubles narrowing it down.
Ok, this sounds like some kind of driver issue with SATA. What kernel are you running (uname -r)?
What kind of machine (model of motherboard and/or machine)?
Do you have the latest BIOS update for the motherboard and the SATA controller.
Is the controller for the hard drive(s) built onto the motherboard or is it a separate controller?
Are you running RAID or LVM2 (or both)?
It is definitely not faulty hardware, although it could be hardware incompatibilities, but CentOS-3 worked perfectly fine.
On Mon, 22 Aug 2005, Johnny Hughes wrote:
On Mon, 2005-08-22 at 13:22 -0400, Robin Mordasiewicz wrote:
On Mon, 22 Aug 2005, Johnny Hughes wrote:
Just wondering if you are installing a bunch of i386 stuff (Open Office, etc., or mostly just x86_64 stuff) It shouldn't matter, you should be able to install packages and upgrade all the items with no issues.
In my kickstart config I have
%packages --resolvedeps @ kde-software-development @ compat-arch-development @ kde-desktop @ web-server @ x-software-development @ legacy-software-development @ french-support @ server-cfg @ system-tools @ editors @ admin-tools @ base-x @ printing @ gnome-desktop @ gnome-software-development @ graphics @ development-tools @ text-internet @ graphical-internet @ compat-arch-support kernel-smp-devel kernel-smp lvm2 e2fsprogs
Ok, this sounds like some kind of driver issue with SATA. What kernel are you running (uname -r)?
Linux rnd21.bullseye.tv 2.6.9-11.ELsmp #1 SMP Wed Jun 8 16:59:12 CDT 2005 x86_64 x86_64 x86_64 GNU/Linux
What kind of machine (model of motherboard and/or machine)?
It is a Tyan with an onboard SATA controller, I do not have the exact specs. I will look it up asap.
Do you have the latest BIOS update for the motherboard and the SATA controller.
yep
Is the controller for the hard drive(s) built onto the motherboard or is it a separate controller?
onboard
Are you running RAID or LVM2 (or both)?
I only have a single drive, so no RAID, but by default CEntOS 4 is using LVM
After doing some more research I tried using the unsupported kernel from the centosplus repo and everything works fine now.
Thanks for the excellent hints on where to look. I would never guessed that it was a kernel incompatiblity problem.
On Mon, 22 Aug 2005, Robin Mordasiewicz wrote:
On Mon, 22 Aug 2005, Johnny Hughes wrote:
After doing some more research I tried using the unsupported kernel from the centosplus repo and everything works fine now.
Thanks for the excellent hints on where to look. I would never guessed that it was a kernel incompatiblity problem.
spoke too soon. I got further in the yum update but it quit with
Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Updating: zlib 100 % done 1/128 /sbin/ldconfig: File /usr/lib/liblapack.so.3.0.3.#prelink#.3qFZHx is empty, not checked.
and on the console I see...
ata3: command 0xca timeout .... ata3: status 0xda { Busy } SCSI error <2 0 0 0 > Current sda: sense key aborted command Additional sense: scsi parity error end_request: I/O error /dev/sda EXT3fs error: ... journal has aborted
On Mon, Aug 22, 2005 at 02:31:08PM -0400, Robin Mordasiewicz wrote:
I got further in the yum update but it quit with
Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Updating: zlib 100 % done 1/128 /sbin/ldconfig: File /usr/lib/liblapack.so.3.0.3.#prelink#.3qFZHx is empty, not checked.
and on the console I see...
ata3: command 0xca timeout .... ata3: status 0xda { Busy } SCSI error <2 0 0 0 > Current sda: sense key aborted command Additional sense: scsi parity error end_request: I/O error /dev/sda EXT3fs error: ... journal has aborted
Well this is clearly some sort of serious hardware or disk driver issue. I can't imagine it being related to yum or rpm other than that what it's currently interfering with.
On Mon, 22 Aug 2005, Alan Hodgson wrote:
On Mon, Aug 22, 2005 at 02:31:08PM -0400, Robin Mordasiewicz wrote:
I got further in the yum update but it quit with
Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Updating: zlib 100 % done 1/128 /sbin/ldconfig: File /usr/lib/liblapack.so.3.0.3.#prelink#.3qFZHx is empty, not checked.
and on the console I see...
ata3: command 0xca timeout .... ata3: status 0xda { Busy } SCSI error <2 0 0 0 > Current sda: sense key aborted command Additional sense: scsi parity error end_request: I/O error /dev/sda EXT3fs error: ... journal has aborted
Well this is clearly some sort of serious hardware or disk driver issue. I can't imagine it being related to yum or rpm other than that what it's currently interfering with.
Well the initial install is fine, it only does this after running yum update, and I have tried it on three separate machines all with the same results, and which all worked fine under CentOS-3
On Mon, Aug 22, 2005 at 02:49:46PM -0400, Robin Mordasiewicz wrote:
Well the initial install is fine, it only does this after running yum update, and I have tried it on three separate machines all with the same results, and which all worked fine under CentOS-3
Which would tend to rule out hardware. So you're left with a driver problem.
Do some other disk-intensive things on those systems, I bet you have similar problems.
On Mon, 22 Aug 2005, Alan Hodgson wrote:
Which would tend to rule out hardware. So you're left with a driver problem.
Do some other disk-intensive things on those systems, I bet you have similar problems.
well currently I have One Centos-4 without the updates running as a file server, and have not had any problems. All my machines are identical Although I am using an attached disk array for serving files.
On Mon, 22 Aug 2005, Robin Mordasiewicz wrote:
On Mon, 22 Aug 2005, Alan Hodgson wrote:
Which would tend to rule out hardware. So you're left with a driver problem.
Do some other disk-intensive things on those systems, I bet you have similar problems.
well currently I have One Centos-4 without the updates running as a file server, and have not had any problems. All my machines are identical Although I am using an attached disk array for serving files.
BIOS update from TYAN did the trick, thanks alot folks.
On Mon, 2005-08-22 at 15:53 -0400, Robin Mordasiewicz wrote:
On Mon, 22 Aug 2005, Robin Mordasiewicz wrote:
On Mon, 22 Aug 2005, Alan Hodgson wrote:
Which would tend to rule out hardware. So you're left with a driver problem.
Do some other disk-intensive things on those systems, I bet you have similar problems.
well currently I have One Centos-4 without the updates running as a file server, and have not had any problems. All my machines are identical Although I am using an attached disk array for serving files.
BIOS update from TYAN did the trick, thanks alot folks.
Cool ... hopefully this fix will continue to work :)
This does not look like a yum error. Your having either file system problems or you have a motherboard/cable/hdd problem.
Robin Mordasiewicz wrote:
On Mon, 22 Aug 2005, Robin Mordasiewicz wrote:
On Mon, 22 Aug 2005, Johnny Hughes wrote:
After doing some more research I tried using the unsupported kernel from the centosplus repo and everything works fine now.
Thanks for the excellent hints on where to look. I would never guessed that it was a kernel incompatiblity problem.
spoke too soon. I got further in the yum update but it quit with
Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Updating: zlib 100 % done 1/128 /sbin/ldconfig: File /usr/lib/liblapack.so.3.0.3.#prelink#.3qFZHx is empty, not checked.
and on the console I see...
ata3: command 0xca timeout .... ata3: status 0xda { Busy } SCSI error <2 0 0 0 > Current sda: sense key aborted command Additional sense: scsi parity error end_request: I/O error /dev/sda EXT3fs error: ... journal has aborted _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos .
Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Updating: zlib 100 % done 1/128 /sbin/ldconfig: File /usr/lib/liblapack.so.3.0.3.#prelink#.3qFZHx is empty, not checked.
and on the console I see...
ata3: command 0xca timeout .... ata3: status 0xda { Busy } SCSI error <2 0 0 0 > Current sda: sense key aborted command Additional sense: scsi parity error end_request: I/O error /dev/sda EXT3fs error: ... journal has aborted
OK, so it's pretty obvious this has nothing whatsoever to do with yum, except for yum causing quite a lot of random-access disk strain and thus causing the hardware or software (or likely the interface between the two) of the HDD to go flaky...
Cheers, MaZe.
On Mon, Aug 22, 2005 at 01:02:23PM -0400, Robin Mordasiewicz wrote:
Are you running x86_64 ? Or is anyone here running x86_64 CentOS 4 and having success with yum update ?
I currently have 5 x86_64 CentOS 4 servers. None have problems with yum or rpm. 3 are dual-CPU. All are Tyan S2881's.
I also installed it several times on various whitebox machines for testing and for building packages before I bought those servers and never saw a problem with yum or rpm.
My php scripts will only run from bash if I run php followed by the script name. Some how I remember having had this setup where it would recognize it was a php file by just running the script itself ex - scriptname.php.
Can someone refresh my memory to tell me what I need to change so it runs just by typing the script name?
thx
centos 3.5
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
On Mon, 22 Aug 2005, Robin Mordasiewicz wrote:
On Mon, 22 Aug 2005, Dave Gutteridge wrote:
I've had this exact same problem, and I uninstalled yum reinstalled it and it work for a day and then back to the same. I've also had it working temporarily by doing a yum clean-all then yum makecache. But next day it went back to doing the same old hang up. I'm not sure if this is a yum problem or a centos problem.
I was having this exact issue recently. Or at least, Yum was hanging at the same stage as what you describe.
It was recommended to me on this list to do the following:
cd /var/lib/rpm rm __db.00* rpm --rebuilddb
This seems to have cleared up the problem for me. It might work for you.
Are you running x86_64 ? Or is anyone here running x86_64 CentOS 4 and having success with yum update
I am running x86_6 and had strange problems twice after running yum update. You didn't state you are using x86 or x86_64 CentOS DVD but I am assuming it is the x86_64 DVD?? I used x86_64
The first time after a system crash (which I caused) the box was unable to compile anything. The second time I had hang problems too. I just nuked the box and am running a non updated CentOS 4.1 x86_64. For me it's no problem. no access to the box is possible and it's not running any services.
On Tue, 23 Aug 2005, Remco Barendse wrote:
On Mon, 22 Aug 2005, Robin Mordasiewicz wrote:
On Mon, 22 Aug 2005, Dave Gutteridge wrote:
I've had this exact same problem, and I uninstalled yum reinstalled it and it work for a day and then back to the same. I've also had it working temporarily by doing a yum clean-all then yum makecache. But next day it went back to doing the same old hang up. I'm not sure if this is a yum problem or a centos problem.
I was having this exact issue recently. Or at least, Yum was hanging at the same stage as what you describe.
It was recommended to me on this list to do the following:
cd /var/lib/rpm rm __db.00* rpm --rebuilddb
This seems to have cleared up the problem for me. It might work for you.
Are you running x86_64 ? Or is anyone here running x86_64 CentOS 4 and having success with yum update
I am running x86_6 and had strange problems twice after running yum update. You didn't state you are using x86 or x86_64 CentOS DVD but I am assuming it is the x86_64 DVD?? I used x86_64
The first time after a system crash (which I caused) the box was unable to compile anything. The second time I had hang problems too. I just nuked the box and am running a non updated CentOS 4.1 x86_64. For me it's no problem. no access to the box is possible and it's not running any services.
This was solved, it turned out that I had a TYAN mother board with onboard SATA controller, which I updated the bios to the latest, and now everything is fine.
On Mon, 22 Aug 2005, Kevin Anderson wrote:
I've had this exact same problem, and I uninstalled yum reinstalled it and it work for a day and then back to the same. I've also had it working temporarily by doing a yum clean-all then yum makecache. But next day it went back to doing the same old hang up. I'm not sure if this is a yum problem or a centos problem.
ok this is definitely not a hardware problem that I have.
This is definitley some kind of bug.
My environment is
1*SATA drive 2*AMD opteron x86_64
CentOS 4.1 installed from DVD
after running yum update the box becomes completely useless, I have seen kernel messages reporting EXT3 problems.
after running yum update I see on the console.
ATA3 BUG: timout without command.
I have 25 identical boxes that I would like to install CentOS on, but I cannot update without the boxes becoming useless. CentOS-3 worked perfectly fine.
-
Alan Hodgson -
Dave Gutteridge -
Johnny Hughes -
Kevin Anderson -
Maciej Żenczykowski -
Michael Rock -
Remco Barendse -
Robin Mordasiewicz -
William Warren