• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

About to update PHP

mike2010

Basic Pleskian
I did a personal FTP backup and server backup (content + configuration) just now.

Any other recommendations before I run 'yum upgrade php' ?

This will be my first time upgrading PHP on a plesk enabled server.
 
thanks. btw, I dont see just PHP on the list. I see PHP I.386 or something like that..

Should I type "yum upgrade php" or "yum upgrade phpI.386" ?

And anything different with mysql ? Thats next after php.
 
I just upgrade with "yum upgrade"

I appreciate the responses , turtle.

But , I dont know what to do anymore. My hosting tech support (aplus.net) recommends I dont even upgrade my PHP. Because of all the recent issues with people upgrading PHP on a Plesk machine. There seems to be a lot of issues. He didnt go into specifics.

Also, before he told me that I did try to upgrade..and got this error.


Error: Missing Dependency: php <= 5.2.0 is needed by package php-sqlite2

I didnt even know I had sqlite2 on there. I use mysql, but I dont know of any programs that use sqlite2..that is seperate from mysql right ? Is it a common error when trying to upgrade php ?

by the way, my current PHP is 5.1.6 ..and mysql is 5.0.45
 
I removed sqlite2 successfully..and did yum upgrade php.

during the install it says :

warning: /etc/php.ini created as /etc/php.ini.rpmnew

am I suppose to rename php.ini.rpmnew to php.ini ? and then restart apache ?

I didnt restart apache yet.. kinda nervous.

Also, I heard when Plesk updates to a newer version, it sometimes updates to a newer mysql version as well... is this correct ?

please answer..i appreciate it very much.
 
sqlite2 is used by sitebuilder. Did you get that when you ran "yum upgrade" or when you ran "yum upgrade php". One of the reasons why you'd use a generic upgrade over a specific one is because it allows yum to be more vigorous in solving dependency issues on its own.

I dont know of any issues with PHP 5.2.x with plesk, if there were you'd probably hear the Fedora folks complaining about it daily since thats what they come with by default :p Sounds like your hoster is just being overly cautious.

By all means if you do run into a problem with PHP 5.2, let me know. We usually get a fix out the same day.
 
sqlite2 is used by sitebuilder. Did you get that when you ran "yum upgrade" or when you ran "yum upgrade php". One of the reasons why you'd use a generic upgrade over a specific one is because it allows yum to be more vigorous in solving dependency issues on its own.

I dont know of any issues with PHP 5.2.x with plesk, if there were you'd probably hear the Fedora folks complaining about it daily since thats what they come with by default :p Sounds like your hoster is just being overly cautious.

By all means if you do run into a problem with PHP 5.2, let me know. We usually get a fix out the same day.

I ran the php upgrade and it worked perfectly. 5.2.9 and no issues. thank god.

But is the thing about MYSQL correct....that occasionally when Plesk updates to a new version, it updates the MYSQL version as well ? This way I wont have to drive myself crazy over updating MYSQL every time when a new version is out. I'd just wait for a new plesk version.

Also, I ran a "yum update" and a "yum upgrade" both seperately. I initially thought doing so, just upgrades the list of services available in the repositories. I didnt know that running "yum update" actually upgrades the CentOs operating system. Is that true ?
And did running "yum upgrade" by itself install other stuff on my server as well ?

sorry for the noobish questions.. I used to be with another hosting company where everything was a simple "vinstall". All this yum stuff is new to me.

If you could answer all, I promise I wont have anymore questions in this thread. very, very much appreciated.
 
But is the thing about MYSQL correct....that occasionally when Plesk updates to a new version, it updates the MYSQL version as well ? This way I wont have to drive myself crazy over updating MYSQL every time when a new version is out. I'd just wait for a new plesk version.

Plesk doesnt update it, thats pulled from the vendor (centos in your case), or a 3rd party repo like mine. CentOS/Redhat doesn't make major updates to the OS often, its a more conserative platform which is why we recommend it for hosting.

Also, I ran a "yum update" and a "yum upgrade" both seperately. I initially thought doing so, just upgrades the list of services available in the repositories. I didnt know that running "yum update" actually upgrades the CentOs operating system. Is that true ?

yum is the updater used by CentOS, RedHat and Fedora. Its a channel based system, that lets 3rd parties like myself add repositories of packages to it. The difference between "update" and "upgrade" is subtle if you're not a packager, long story short "update" does not honor "Obsolete" tags, and "upgrade" does. What that means to you is, use "yum upgrade"


And did running "yum upgrade" by itself install other stuff on my server as well ?

Yes, it will give you a list of all the packages it will upgrade, and log those upgrades to /var/log/yum.log
 
thanks , but I still dont understand fully when running "yum upgrade" (without any extension after)

Why it updates / installs certain things only. How does it decide what needs updating to the server ? And sometimes it seems to install items I didnt specify.

Im just confused on the whole process on what is determined, and how things are determined to be installed when running "yum upgrade".
 
That is something that is explained when you search google for how yum works. Yum is not a plesk component its an updater used by some distro's of plesk. Be aware that you can break your plesk install by using yum if you updated to something that is not supported by plesk. You are best to install the atomic turtle repo's if your distro is supported. Refer to http://www.atomicorp.com/channels/plesk/

Here is alot of info about yum http://yum.baseurl.org/wiki/Guides

Also I think that you should start with the basic's http://linux-newbie.dotsrc.org/
 
We're really going down the rabbit hole now huh :p

The big picture here is that there is a very elaborate package management system going on behind the scenes. At the root level you have a piece of software, like PHP. This is bundled up with the RPM (redhat package management) system, this itself is more than just an archive file like a zip, rar, etc. It also includes metadata about the package, like who made it, the license, actions on instal/delete/upgrade, and most importantly, Dependencies.

When you install php, the first thing it will do is read its depedency list that says "I need apache to work".

So if you think about it this way, RPM's are the bundles of software, or the first level of the pyramid. In days gone by it was up to you the human to go and grab all the RPM's in that dependency list, which was rather cumbersome. There had to be a better way, and so yum came about. Yum itself is a layer above that, it looks at these dependency lists, and automatically downloads and installs them. So, imagine if you will you have a brand new server without plesk, apache, etc installed and you type "yum install php".

Yum will in this order:
1) download the metadata from the update server
2) look up php and list what its Dependencies are, sees that it also needs apache
3) look at what is currently installed on the system, sees that apache is *not* installed
4) downloads/installs apache
5) downloads/installs php

To your question about the upgrade event, it works much like the above, with some additions:
1) download the metadata from the update server
2) look up what is currently installed on the system
3) compares the list of what versions of sofware are installed against what is available from step 1
4) downloads/installs the differences versions

To your questions about why it will update things you didnt specify, the short version is "for your own good". :p One of the key features in the RPM system is the ability to designate what specific versions of a Dependency is required for a package to work. For example, sitebuilder needs the package php-sqlite2 to work, and php-sqlite2 needs the sqlite 2.0 library to work. So when you install sitebuilder yum will actually download and install 3 packages.

Does that help clear things up better for you?
 
Im one of those 'learn as you go' folks...so my bad if the questions seem noobish. I've been managing servers for over 5 years now..Its just different when you go from a mostly managed FreeBSD server.. to CentOs / Yum / Redhat .

That mostly cleared my head...thanks.

But would you consider running "yum upgrade" a safe thing to do....or would it be wiser to do the upgrades individually ? ( ex. yum upgrade kernal , yum upgrade CentOs , etc)

From what you've posted it seems like its 'mostly' a safe bet...since it checks the server beforehand to see what it needs first.

But if something gets screwed up.. like "yum upgrade CentOs" ...is there a way to revert back to the old version or no ?

It seems like a good thing for the most part, but would really suck if one of the updates breaks the server / plesk.

Generally I prefer to update PHP and MYSQL once a year or every 6 months at most. Plesk whenever there are updates...but the other stuff I usually almost never update. (CentOS , Apache2 , etc )
 
Yes, yum supports rollbacks:

http://blog.chris.tylers.info/index...ck-Package-UpdatesInstallation-on-Fedora.html


I always intended for Plesk to work with rather than against the vendor, so I always considered a conflict that plesk had with a vendor update to be a plesk bug. In theory, there should never be a conflict. That being said... theres a plesk bug... with the bind-chroot package :p Just dont install it and you'll never run into it.

That aside there aren't any conflicts out there that I am aware of at this time.
 
depend

Its not all that tricky really, check the wiki page here:

http://www.atomicorp.com/wiki/index.php/PHP

Hi Turtle,

I've tried your script but getting dependency issues. I'm running Plesk 9.0.1 RHEL 5. After the first step in opening the channel, I chose Yes to add to repository ...all seems successful. However, running yum upgrade produced this:

[root@mirage test]# yum update
Loaded plugins: rhnplugin, security
Excluding Packages in global exclude list
Finished
Excluding Packages from Plesk Server Administrator
Finished
Skipping security plugin, no data
Setting up Update Process
Resolving Dependencies
Skipping security plugin, no data
--> Running transaction check
---> Package psa-pylibplesk.i586 0:9.2.1-rhel5.build92090422.13 set to be updated
---> Package php-imap.i386 0:5.2.9-2.el5.art set to be updated
--> Processing Dependency: php-common = 5.2.9-2.el5.art for package: php-imap
......snipped out for post....
---> Package psa-appvault-updates.noarch 0:9.2.1-rhel5.build92090422.13 set to be updated
---> Package psa-backup-manager.i586 0:9.2.1-rhel5.build92090422.13 set to be updated
--> Processing Dependency: libmysqlclient.so.15 for package: psa-backup-manager
---> Package psa-locale-es-ES.noarch 0:9.2.1-09042015 set to be updated
---> Package ntp.i386 0:4.2.2p1-9.el5_3.2 set to be updated
---> Package libicu.i386 0:3.6-5.11.2 set to be updated
---> Package audit-libs-python.i386 0:1.7.7-6.el5_3.3 set to be updated
---> Package svrcore.i386 0:4.0.4-4.el5.art set to be updated
---> Package psa-api.noarch 0:9.2.1-rhel5.build92090422.13 set to be updated
---> Package kpartx.i386 0:0.4.7-23.el5_3.4 set to be updated
---> Package psa-atmail.noarch 1:1.03-2.el5.art set to be updated
---> Package mysql-devel.i386 0:5.0.83-1.el5.art set to be updated
---> Package psa-proftpd.i386 0:1.3.2-6.el5.art set to be updated
---> Package cups-libs.i386 1:1.3.7-8.el5_3.6 set to be updated
---> Package xulrunner.i386 0:1.9.0.11-3.el5_3 set to be updated
---> Package sw-cp-server.i386 0:1.0-5.200902131203.rhel5 set to be updated
---> Package psa-proftpd-xinetd.i586 0:1.3.1-rhel5.build92090422.13 set to be updated
---> Package mozldap.i386 0:6.0.5-5.el5.art set to be updated
---> Package tzdata.noarch 0:2009i-2.el5 set to be updated
---> Package psa-selinux.noarch 0:9.2.1-rhel5.build92090422.13 set to be updated
---> Package psa-qmail-rblsmtpd.i586 0:0.70-rhel5.build92090422.13 set to be updated
---> Package php-gd.i386 0:5.2.9-2.el5.art set to be updated
--> Processing Dependency: php-common = 5.2.9-2.el5.art for package: php-gd
--> Processing Dependency: libt1.so.5 for package: php-gd
---> Package php-pdo.i386 0:5.2.9-2.el5.art set to be updated
--> Processing Dependency: php-common = 5.2.9-2.el5.art for package: php-pdo
---> Package courier-imap.i586 0:3.0.8-rhel5.build92090422.13 set to be updated
---> Package psa-mailman-configurator.i586 0:9.2.1-rhel5.build92090422.13 set to be updated
---> Package psa-api-rpc.noarch 0:9.2.1-rhel5.build92090422.13 set to be updated
---> Package psa-logrotate.i586 0:3.7-rhel5.build92090422.13 set to be updated
---> Package php-mysql.i386 0:5.2.9-2.el5.art set to be updated
--> Processing Dependency: php-common = 5.2.9-2.el5.art for package: php-mysql
---> Package nmap.i386 2:4.85-1.el5.art set to be updated
---> Package psa-firewall.i586 0:1.0.1-rhel5.build92090422.13 set to be updated
---> Package psa-awstats-configurator.noarch 0:1.0.0-rhel5.build92090422.13 set to be updated
---> Package psa-locale-zh-TW.noarch 0:9.2.1-09042015 set to be updated
---> Package mysql.i386 0:5.0.83-1.el5.art set to be updated
---> Package psa-watchdog.i586 0:2.0.3-rhel5.build92090422.13 set to be updated
---> Package psa-locale-fr-FR.noarch 0:9.2.1-09042015 set to be updated
---> Package spamassassin.i386 1:3.2.5-1.el5.art set to be updated
---> Package file.i386 0:4.17-15.el5_3.1 set to be updated
---> Package pango.i386 0:1.14.9-5.el5_3 set to be updated
---> Package psa-locale-ja-JP.noarch 0:9.2.1-09042015 set to be updated
---> Package psa-locale-it-IT.noarch 0:9.2.1-09042015 set to be updated
---> Package sw-engine.i386 0:2.0-3.200903131156.rhel5 set to be updated
---> Package psa-spamassassin.i586 0:9.2.1-rhel5.build92090422.13 set to be updated
---> Package ipsec-tools.i386 0:0.6.5-13.el5_3.1 set to be updated
---> Package psa-locale-ru-RU.noarch 0:9.2.1-09042015 set to be updated
---> Package psa-mail-pc-driver.i586 0:1.0.0-rhel5.build92090422.13 set to be updated
--> Processing Dependency: cyrus-sasl-sqlite3 for package: psa-mail-pc-driver
--> Processing Dependency: cyrus-sasl-md5 for package: psa-mail-pc-driver
--> Processing Dependency: postfix for package: psa-mail-pc-driver
---> Package plesk-skins.noarch 0:9.2.1-0.281812 set to be updated
---> Package sos.noarch 0:1.7-9.16.el5_3.5 set to be updated
---> Package psa-mail-driver-common.i586 0:9.2.1-rhel5.build92090422.13 set to be updated
---> Package device-mapper-multipath.i386 0:0.4.7-23.el5_3.4 set to be updated
---> Package nash.i386 0:5.1.19.6-44.1 set to be updated
---> Package psa-locale-de-DE.noarch 0:9.2.1-09042015 set to be updated
---> Package cscope.i386 0:15.5-15.1.el5_3.1 set to be updated
---> Package psa-qmail.i586 1:1.03-rhel5.build92090422.13 set to be updated
---> Package kexec-tools.i386 0:1.102pre-56.el5_3.2 set to be updated
---> Package psa-updates.noarch 0:9.2.1-rhel5.build92090422.13 set to be updated
---> Package psa.i586 0:9.2.1-rhel5.build92090422.13 set to be updated
---> Package psa-locale-zh-CN.noarch 0:9.2.1-09042015 set to be updated
---> Package psa-locale-base-en-US.noarch 0:9.2.1-09042016 set to be updated
---> Package psa-migration-manager.i586 0:9.2.1-rhel5.build92090422.13 set to be updated
---> Package vsftpd.i386 0:2.0.5-12.el5_3.1 set to be updated
---> Package psa-drweb-configurator.i586 0:9.2.1-rhel5.build92090422.13 set to be updated
---> Package acpid.i386 0:1.0.4-7.el5_3.1 set to be updated
---> Package perl-DBD-MySQL.i386 0:3.0007-2.el5 set to be updated
---> Package openssl097a.i386 0:0.9.7a-9.el5_2.1 set to be updated
---> Package php-xml.i386 0:5.2.9-2.el5.art set to be updated
--> Processing Dependency: php-common = 5.2.9-2.el5.art for package: php-xml
---> Package audit-libs.i386 0:1.7.7-6.el5_3.3 set to be updated
---> Package mkinitrd.i386 0:5.1.19.6-44.1 set to be updated
--> Running transaction check
---> Package t1lib.i386 0:5.1.2-2.el5.art set to be updated
---> Package php-imap.i386 0:5.2.9-2.el5.art set to be updated
--> Processing Dependency: php-common = 5.2.9-2.el5.art for package: php-imap
---> Package php-mbstring.i386 0:5.2.9-2.el5.art set to be updated
--> Processing Dependency: php-common = 5.2.9-2.el5.art for package: php-mbstring
---> Package cyrus-sasl-md5.i386 0:2.1.22-4 set to be updated
---> Package php-gd.i386 0:5.2.9-2.el5.art set to be updated
--> Processing Dependency: php-common = 5.2.9-2.el5.art for package: php-gd
---> Package php-pdo.i386 0:5.2.9-2.el5.art set to be updated
--> Processing Dependency: php-common = 5.2.9-2.el5.art for package: php-pdo
---> Package php-mysql.i386 0:5.2.9-2.el5.art set to be updated
--> Processing Dependency: php-common = 5.2.9-2.el5.art for package: php-mysql
---> Package cyrus-sasl-sqlite3.i386 0:1.0.0-0.279666 set to be updated
---> Package mysql-libs.i386 0:5.0.83-1.el5.art set to be updated
---> Package php-xml.i386 0:5.2.9-2.el5.art set to be updated
--> Processing Dependency: php-common = 5.2.9-2.el5.art for package: php-xml
---> Package postfix.i386 2:2.3.3-2.1.el5_2 set to be updated
--> Finished Dependency Resolution
php-pdo-5.2.9-2.el5.art.i386 from atomic has depsolving problems
--> Missing Dependency: php-common = 5.2.9-2.el5.art is needed by package php-pdo-5.2.9-2.el5.art.i386 (atomic)
php-xml-5.2.9-2.el5.art.i386 from atomic has depsolving problems
--> Missing Dependency: php-common = 5.2.9-2.el5.art is needed by package php-xml-5.2.9-2.el5.art.i386 (atomic)
php-gd-5.2.9-2.el5.art.i386 from atomic has depsolving problems
--> Missing Dependency: php-common = 5.2.9-2.el5.art is needed by package php-gd-5.2.9-2.el5.art.i386 (atomic)
php-imap-5.2.9-2.el5.art.i386 from atomic has depsolving problems
--> Missing Dependency: php-common = 5.2.9-2.el5.art is needed by package php-imap-5.2.9-2.el5.art.i386 (atomic)
php-mysql-5.2.9-2.el5.art.i386 from atomic has depsolving problems
--> Missing Dependency: php-common = 5.2.9-2.el5.art is needed by package php-mysql-5.2.9-2.el5.art.i386 (atomic)
php-mbstring-5.2.9-2.el5.art.i386 from atomic has depsolving problems
--> Missing Dependency: php-common = 5.2.9-2.el5.art is needed by package php-mbstring-5.2.9-2.el5.art.i386 (atomic)
Error: Missing Dependency: php-common = 5.2.9-2.el5.art is needed by package php-mysql-5.2.9-2.el5.art.i386 (atomic)
Error: Missing Dependency: php-common = 5.2.9-2.el5.art is needed by package php-gd-5.2.9-2.el5.art.i386 (atomic)
Error: Missing Dependency: php-common = 5.2.9-2.el5.art is needed by package php-mbstring-5.2.9-2.el5.art.i386 (atomic)
Error: Missing Dependency: php-common = 5.2.9-2.el5.art is needed by package php-imap-5.2.9-2.el5.art.i386 (atomic)
Error: Missing Dependency: php-common = 5.2.9-2.el5.art is needed by package php-xml-5.2.9-2.el5.art.i386 (atomic)
Error: Missing Dependency: php-common = 5.2.9-2.el5.art is needed by package php-pdo-5.2.9-2.el5.art.i386 (atomic)
 
The yum update as apposed to the yum upgrade is not a mistake, both product the same dependancies issues
 
Sorry I'm not following you. What config are you speaking of? I'm just following your wiki instructions. I apologise for the ignorance. Thanks for your feedback.
 
Ok, I upgraded Plesk to 9.2.1. Now I'm getting this:

[root@mirage test]# wget -q -O - http://www.atomicorp.com/installers/atomic.sh | sh

Atomic Archive installer, version 1.1
Configuring the [atomic] yum archive for this system

Installing the Atomic GPG key: OK
Downloading atomic-release-1.0-10.el5.art.noarch.rpm: OK

Would you like to add the Plesk yum repository to the system?

Enable Plesk repository? (y/n) [Default: n]: y

Plesk 8.6 and 9.2 repositories are available:
NOTE: Plesk 9 repos are only available for rhel/centos 4 and 5

Enable Plesk 8.6 or 9.2? (8/9) [Default: 8]: 9


The Atomic Rocket Turtle archive has now been installed and configured for your system
The following channels are available:
atomic - [ACTIVATED] - contains the stable tree of ART packages
atomic-testing - [DISABLED] - contains the testing tree of ART packages
atomic-bleeding - [DISABLED] - contains the development tree of ART packages


[root@mirage test]# yum upgrade
Loaded plugins: rhnplugin, security
Excluding Packages in global exclude list
Finished
Excluding Packages from Plesk Server Administrator
Finished
Skipping security plugin, no data
Setting up Upgrade Process
Resolving Dependencies
Skipping security plugin, no data
--> Running transaction check
---> Package libicu.i386 0:3.6-5.11.2 set to be updated
---> Package psa-locale-zh-TW.noarch 0:9.2.1-09042015 set to be updated
---> Package php-mbstring.i386 0:5.2.9-2.el5.art set to be updated
--> Processing Dependency: php-common = 5.2.9-2.el5.art for package: php-mbstring
---> Package php-imap.i386 0:5.2.9-2.el5.art set to be updated
--> Processing Dependency: php-common = 5.2.9-2.el5.art for package: php-imap
---> Package audit-libs-python.i386 0:1.7.7-6.el5_3.3 set to be updated
---> Package audit.i386 0:1.7.7-6.el5_3.3 set to be updated
---> Package spamassassin.i386 1:3.2.5-1.el5.art set to be updated
---> Package mysql-devel.i386 0:5.0.83-1.el5.art set to be updated
--> Processing Dependency: libndbclient.so.2 for package: mysql-devel
---> Package tzdata.noarch 0:2009i-2.el5 set to be updated
---> Package file.i386 0:4.17-15.el5_3.1 set to be updated
---> Package perl-DBD-MySQL.i386 0:3.0007-2.el5 set to be updated
---> Package cups.i386 1:1.3.7-8.el5_3.6 set to be updated
---> Package ipsec-tools.i386 0:0.6.5-13.el5_3.1 set to be updated
---> Package kexec-tools.i386 0:1.102pre-56.el5_3.2 set to be updated
---> Package php-gd.i386 0:5.2.9-2.el5.art set to be updated
--> Processing Dependency: php-common = 5.2.9-2.el5.art for package: php-gd
--> Processing Dependency: libt1.so.5 for package: php-gd
---> Package psa-proftpd.i386 0:1.3.2-6.el5.art set to be updated
---> Package psa-atmail.noarch 1:1.03-2.el5.art set to be updated
---> Package ntp.i386 0:4.2.2p1-9.el5_3.2 set to be updated
---> Package php-pdo.i386 0:5.2.9-2.el5.art set to be updated
--> Processing Dependency: php-common = 5.2.9-2.el5.art for package: php-pdo
---> Package php-mysql.i386 0:5.2.9-2.el5.art set to be updated
--> Processing Dependency: php-common = 5.2.9-2.el5.art for package: php-mysql
---> Package mysql.i386 0:5.0.83-1.el5.art set to be updated
---> Package audit-libs.i386 0:1.7.7-6.el5_3.3 set to be updated
---> Package openssl097a.i386 0:0.9.7a-9.el5_2.1 set to be updated
---> Package acpid.i386 0:1.0.4-7.el5_3.1 set to be updated
---> Package xulrunner.i386 0:1.9.0.11-3.el5_3 set to be updated
---> Package cups-libs.i386 1:1.3.7-8.el5_3.6 set to be updated
---> Package svrcore.i386 0:4.0.4-4.el5.art set to be updated
---> Package cscope.i386 0:15.5-15.1.el5_3.1 set to be updated
---> Package mkinitrd.i386 0:5.1.19.6-44.1 set to be updated
---> Package vsftpd.i386 0:2.0.5-12.el5_3.1 set to be updated
---> Package psa-mailman-configurator.i586 0:9.2.1-rhel5.build92090422.13 set to be updated
---> Package courier-imap.i586 0:3.0.8-rhel5.build92090422.13 set to be updated
---> Package psa-locale-es-ES.noarch 0:9.2.1-09042015 set to be updated
---> Package nash.i386 0:5.1.19.6-44.1 set to be updated
---> Package psa-locale-fr-FR.noarch 0:9.2.1-09042015 set to be updated
---> Package psa-locale-de-DE.noarch 0:9.2.1-09042015 set to be updated
---> Package device-mapper-multipath.i386 0:0.4.7-23.el5_3.4 set to be updated
---> Package kpartx.i386 0:0.4.7-23.el5_3.4 set to be updated
---> Package nmap.i386 2:4.85-1.el5.art set to be updated
---> Package psa-php5-configurator.noarch 0:1.5.1-rhel5.build92090422.13 set to be updated
---> Package psa-drweb-configurator.i586 0:9.2.1-rhel5.build92090422.13 set to be updated
---> Package sos.noarch 0:1.7-9.16.el5_3.5 set to be updated
---> Package mysql-server.i386 0:5.0.83-1.el5.art set to be updated
---> Package psa-qmail-rblsmtpd.i586 0:0.70-rhel5.build92090422.13 set to be updated
---> Package psa-mail-pc-driver.i586 0:1.0.0-rhel5.build92090422.13 set to be updated
filelists.xml.gz | 14 MB 00:04
Error: failed to retrieve repodata/filelists.xml.gz from rhel-i386-server-5
error was [Errno -1] Metadata file does not match checksum

Any idea what may be causing this?
 
Seems to be a redhat repository issue. Have opened a trouble ticket with The Planet.
 
Back
Top