Hi there,
I’m a little worried about my CentOS/InterWorx server. I have just read that WordPress 3.2 (release due Spring 2011) is going to require PHP 5.2. Will InterWorx/CentOS be supporting 5.2 or greater any time soon? I have always been keen to keep my WordPress installs as up-to-date as possible for security fixes, etc.
Thanks
The “official” position is that we support the version that comes with your OS. The “realistic” position is that we also support the versions from our “unsupported” repo as well.
We’ve been intending to make the integration of this repo a lot simpler, because most people don’t even know about it. We find a lot of support tickets where people have installed the DAG or Atomic repos just to get newer versions of PHP and MySQL, except then during the next automatic upgrade, it blows away Important Things. This is always a Bad Thing.
The sheer popularity of WordPress will make this move higher up the priority list.
Thanks for bringing it to our attention.
Tim
Hello Jabyuk,
Here are instructions on how to run a newer version of PHP in InterWorx.
Thank you both for your responses. Let’s hope CentOS will get their act together and support a later release of PHP - that would be the ideal solution. But, if that doesn’t happen, thanks Jon for the instructions on how to switch to the unsupported/newer repositories.
Shouldn’t CentOS 6 be coming out soon which will most likely support the new PHP?
Although, not sure it’s ever recommend to do an upgrade on a production server for a major version upgrade. So could be kind of pain to setup a new server with CentOS 6 and move all the sties over and stuff just to get PHP 5.2.
Guess I’ll wait it out a bit longer to see what the official position of InterWorx is on PHP 5.2 and if nothing changes, I’ll follow the instructions Jon provided.
Just my 2? worth here. We have been running 5.2.X both on CentOS 4x and CentOS 5x InterWorx servers for a good while now without any issues to speak of.
The reason we where doing it was because of PCI compliance.
And another strong reason to run 5.2.x is WordPress, it is EXTREMELY popular. And because of that it attracts hackers like “poop” attracts flies.
Actually we are in the process of moving our own site to WordPress in the coming weeks.
A side Note for WordPress users. I HIGHLY recommend this Security Plugin to ANY WordPress site: BulletProof Security (great stuff)
Magento DOES require PHP 5.2
FYI, Magento already requires PHP 5.2
Larry Hiscock
AngelicHost
The unsupported repo for 5.2 agrees with me also, particularly since there are issues with 5.3 and Zend encoded scripts, unless the scripts are recompiled for 5.3 and newer releases.
As of this post, no longer running CentOS 4.x but all IW servers have CentOS 5.6 with PHP 5.2.17 no issues.
Hi,
Today I attempted to upgrade my server to PHP 5.2 (as Wordpress 3.2 is now imminent!)
However after running “yum update”, far from receiving a response such as the one you show in your instructions above, where 7 packages will be updated. I instead get a message indicating that 4 packages will be installed, 255 packages will be updated and 1 will be removed.
This makes me a little uncomfortable as I am afraid that proceeding further may prove to do more harm than good. All I am trying to do is to upgrade PHP to version 5.2 but it appears that, if I proceed, I will also upgrade/install/remove a lot more besides.
Please can you take a look at the output in the attached file and let me know if you believe that it will be okay to proceed further with minimum risk to me server environment?
yum_update.txt (41.7 KB)
After sending my response above, I removed the file “iworx-unsupported.repo” to prevent any automatic updates taking place. Then, to see what would happen with this file removed, I ran “yum update” again. This time around I still get:
Install 4 Package(s)
Upgrade 246 Package(s)
Remove 1 Package(s)
Reinstall 0 Package(s)
Downgrade 0 Package(s)
Total size: 367 M
Is this ok [y/N]:
So it seems like these updates are unrelated to the unsupported repo to get PHP 5.2 to work. My server is set to do automatic OS and Iworx updates and it shows a status of “NO SOFTWARE UPDATES ARE PENDING” in the http:/x.x.x.x/nodeworx/updates page.
After hitting the refresh button the list of pending updates appears and the log shows:
Install 4 Package(s)
Upgrade 246 Package(s)
Remove 1 Package(s)
Reinstall 0 Package(s)
Downgrade 0 Package(s)
This looks to me like the system hasn’t been updating properly (or at least automatically) for some time.
Do you hink it is safe to let this happen and then to return to the PHP 5.2 issue?
Well, you can always punch go on the update and if it breaks anything we’ll do our best to help you fix it. Doesn’t look like anything in that list of packages is necessarily damaging to me, though.
I get the following error message from time in my mail, could this be related to the OS and iworx updates not automatically being updatedand, either way, does anyone know how I might resolve it?
Subject: Cron <iworx@ds2> cd /home/interworx/cron ; ./iworx.pex --daily
Transaction Check Error:
file /usr/share/locale/de/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/en/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/en@boldquot/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/en@quot/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/es/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/fr/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/it/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/ja/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/ko/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/nl/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/zh_CN/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/zh_TW/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
re: Jabyuk
It looks like to me you may have InterWorx set to automatically update but, you do not have CentOS automatically updating. You should be absolutely fine updating all the packages it shows.
Regards,
Chris
Drat, beat to my response!
Hi,
Thanks for the feedback and help so far. According to Interworx “Automatic Update Options” are enabled for both InterWorx and OS Updates.
I have now started an install of the pending updates through the Interworx control panel. This is taking some time and is currently at the following stage where it has been for about half an hour now:
Total size: 367 M
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
I’m guessing that, with 327 M of pending updates, that this might be expected to take some time?
Since I do have automatic OS updates turned on could the problem with updates not being installed be related to my earlier post - see below?
I get the following error message from time in my mail, could this be related to the OS and iworx updates not automatically being updatedand, either way, does anyone know how I might resolve it?
Subject: Cron <iworx@ds2> cd /home/interworx/cron ; ./iworx.pex --daily
Transaction Check Error:
file /usr/share/locale/de/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/en/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/en@boldquot/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/en@quot/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/es/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/fr/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/it/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/ja/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/ko/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/nl/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/zh_CN/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/zh_TW/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
Okay, now I know that this error is the problem. The install of pending updates through Iworx never completes and the list of pending updates is, for some reason unknown, periodically disapearing to be replaced with a message indicating that “NO SOFTWARE UPDATES ARE PENDING”. Hitting the “Refresh” button brings back the pending list again.
However if I run “yum update” manually I do get the following error - see below.
Please can someone help me to resolve this? I realise now that the OS has not been updating correctly for a few months now.
Total size: 367 M
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Check Error:
file /usr/share/locale/de/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/en/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/en@boldquot/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/en@quot/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/es/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/fr/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/it/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/ja/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/ko/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/nl/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/zh_CN/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
file /usr/share/locale/zh_TW/LC_MESSAGES/libsmbios-2.2-x86_64.mo from install of libsmbios-2.2.26-6.2.el5.i386 conflicts with file from package libsmbios-2.2.19-10.1.el5.x86_64
jabyuk:
rpm -qa | grep libsmbios
What’s the output of the above command?
Hi,
The output is as follows:
rpm -qa | grep libsmbios
libsmbios-2.2.19-10.1.el5
libsmbios-2.2.19-10.1.el5
It looks like two identical lines to me.
I have found the solution to my problem here: http://www.md3v.com/libsmbios-errors-when-running-yum-update-on-dell-poweredge
There seems to be a compatibility issue between older versions of Dell OpenManage and updates available in the Dell repository. This process will forcefully remove Dell OpenManage followed by a clean install.
To resolve this error cut and paste the following to your command line:
rm -rfv /opt/dell/
yum -y remove libsmbios
yum -y remove dell-omsa-repository-2-5.noarch
yum remove openwsman-server openwsman-client
rpm -e sblim-sfcb
rm /etc/yum.repos.d/dell-omsa-repository.repo -fv
yum clean all
Followed by:
yum -y install srvadmin-all
Then confirm that OpenManage is functioning with:
omreport chassis info
Then complete a full system update:
yum update -y