when I try to run a yum update on a 5.5 64 bit centos box i get the following:
root@zduaanderson [/home/a]# yum clean all && yum update
Loaded plugins: fastestmirror, priorities
Cleaning up Everything
Cleaning up list of fastest mirrors
On two Centos5 servers, yum gives a segmentation fault error when trying 'yum update' or 'yum check-update' after running 'yum clean' :
[Code]....
The error is the same for the other computer except while attempting to update the rpmforge repository. Nothing has really changed on the servers in some time and 'yum update' worked fine on each yesterday and I have no idea why they would both suddenly fail!
For some reason, when I do a yum check-update I get a list of no changed packages to install. If I follow this immediately with a yum update then it tries to install drbd83. I've tried a yum clean all and repeated the commands and get the same thing. This happens on both the machines that are set up to use DRBD. Just seems weird and I don't understand. Anyone got an explanation?
I have a error when i want to update my system via YUMI execute the next command.sh@ yum -y updateYou could try using --skip-broken to work around the problemYou could try running:package-cleanup --problems package-cleanup --dupes rpm -Va --nofiles --nodigestThe program package-cleanup is found in the yum-utils package.
Just checking to be sure. 5.3>5.4 update went without a hitch:) But a message ran about (/etc/yum.repo.d) CentOS-Base.repo.rpmnew. Comparing CentOS-Base.repo with the new one show the 1st has the correct priorities and .rpmnew does not have the correct priorities. Should I remove the *.rpmnew repo after making sure it otherwise is the same as the original CentOS-Base.repo?
I am an old days RH release user(from 6.x) and just switching back from Debian/Ubuntu to CentOS on some servers, but I can not understand the kernel update strategy currently enabled in CentOS.There are two boxes, with almost identical installation, but recently there was an auto update of kernel on one box. This auto update also seems to issue an auto reboot on the machine, which is unacceptable on server machines.
After some testing for a couple of days, I decided to take the plunge and update all my 5.3 machines. Using the recipe from the release notes:
yum clean all yum update glibc* yum update yum* rpm* python* yum clean all yum update shutdown -r now
I updated some guinea pigs that I had physical access to and didn't have any issues. So I remotely updated a small farm of LAMP machines that handle a couple of million page views per day. It took each machine approximately 5-6 minutes to download/install/reboot.
I have centos 5.3 workin on mini itx atom 330. i have some problem with the network when i use Samba. when i move big files the network goes down. i wanna to install the new kernel on my centos to try to fix the network problem with the new drivers includes on the new kernel.
I have a CentOS server in one of my labs at work that does not have an Internet connection.Is there anyway that I can download the updates on a USB stick and then update the server? If so, what are the procedures?
Is it possible to do an update from fedora to centos without losing everything? in paticular I would like to keep the users and openvpn-as configuration.
I applied the Kernel update that showed in the updater via the GUI.It now won't boot anymore.Memory for crash kernel (0x0 to 0x0) notwithin permissible range.WARNING calibrate_APIC_clock: the APIC timer calibration may be wrong.
I have Centos 5.3 on our server When I log-in in webmin I have a message "Warning - Your system is actually running CentOS Linux version 5.3." In the next line I have a button "Update Detected Operating System" My question is Do I need to click the link and update Detected operating system? If I do, is it going to change any configuration on our server?
Today, I try to update firefox by Package Updater but show error by bellow. "Missing Dependency: xulrunner >= 1.9.0.19-1 is needed by package firefox-3.0.19-1.el5.centos.x86_64 (CentOS5updates)"
Months ago, I posted bug reports related to the GTK in CentOS 5.3 (and RHEL 5.3). Seems clear that RH isn't going to issue a fix (RPM) this problem before RHEL 6. (Note: GTK long ago fixed the bug. If RH would issue a patch, I'd be happy. But as I said, I don't think they will.)
Looks like I'll have to fix the problem myself.
What is the best way to update GTK in CentOS 5.3?
I've made one attempt by downloading and attempting to recompile from source. Manged to recompile glib but it doesn't seem to want to install. (make install, completes without any errors but when I try to ./configure pango it says that it can't find a new enough version of glib).
I was updating my PHP version on my centOS server and it was taking too long updating CUPS, so I killed it, when I tried to run the update again I got the following error message:
Transaction Check Error: file /usr/share/locale/nb/LC_MESSAGES/firstboot.mo from install of firstboot-1.4.27.8-1.el5.centos.i386 conflicts with file from package firstboot-tui-1.4.27.7-1.el5.centos.i386 file /usr/share/locale/no/LC_MESSAGES/firstboot.mo from install of firstboot-1.4.27.8-1.el5.centos.i386 conflicts with file from package firstboot-
I see Centos 5.3 is out, actually i have been seeding for the last 18hrs. Will yum automatically update the box to 5.3 or is there a special way to do it. Am using the centos plus kernel.
I did a yum clean all then yum update and got all the 5.4 stuff at which point I rebooted it gets to the udev entry and dies. Any one have any sugestions on how to fix this?
when I am doing a "yum update" I receive now a long list (~94MB) because of the latest CentOS 5.4 release.I am running CentOS 5.3 on a virtual machine (virtuozzo) and had already problems to install 5.3 before. To not lose the installation I do not want to update to 5.4 but of course I want to get all updates for 5.3.How can I configure my CentOS 5.3 to update the server only with 5.3 patches/releases and how to prevent it to update to 5.4?
Initially installed 5.3 on a 64-bit platform and was able to compile just fine. Foolhardily updated to 5.5. Somewhere in that process I lost the ability to compile even the simplest "hello, world" C program.
$ gcc hello.c In file included from /usr/include/_G_config.h:44, from /usr/include/libio.h:32, from /usr/include/stdio.h:72, from hello.c:1: