Pete:
Here is a copy of the dialog between my engineer and Pavel. Maybe there is something in here that will help you further...top to bottom = oldest to most recent:
According to the forwarded email you're running PHP 4.3.9 on the
>>>>> system.
>> >>>>>>> All that needs to be done to get PHP upgraded is to download PHP
>>>>> 5.1.6-3
>> >>>>>>> RPMs from
>>>>>
http://isoredirect.centos.org/centos/4/centosplus/i386/RPMS/
>> >>>>>>> and installed them on the system using the "rpm -Uvh php*5.1.6-
>>>>> 3*rpm"
>> >>>>>>> command.
>> >>>>>>>
>> >>>>>>> Thanks,
>> >>>>>>> Pavel
========================================
>>>> Hi Pavel,
>>>> >>>>>>
>>>> >>>>>> Thank you for getting back to us.
>>>> >>>>>>
>>>> >>>>>> I have downloaded the RPMs to upgrade PHP and PEAR on this Plesk
>>> >>>>> node.
>>>> >>>>>> However, there I have run in to an issue.
>>>> >>>>>>
>>>> >>>>>> The php-pear-1.4.11-1.el4s1.1 RPM depends upon a different
>> version
>>> >>>>> of
>>>> >>>>>> the MySQL client library than what is installed on the server.
>> The
>>>> >>>>>> failed dependency is for libmysqlclient.so.15; the versions
>> >>>> available
>>> >>>>> on
>>>> >>>>>> our server are /usr/lib/mysql/libmysqlclient.so.10 and
>>>> >>>>>> /usr/lib/mysql/libmysqlclient.so.14. Additionally, none of the
>>>> >>>>>> mysqlclient RPMs at the URL you provided inclued the newer
>>>> >>>>>> libmysqlclient.so.15 version of this library.
>>>> >>>>>>
>>>> >>>>>> Any ideas where we need to go from here?
>>>> >>>>>>
>>>> >>>>>> Thanks
===================================
>>>> Never mind. The updated MySQL client library is included with the
>>> >>>> base
>>>> >>>>> MySQL RPM, mysql-5.0.27-1.el4. So, in order to upgrade PHP on
> this
>>>> >>>>> server we will also need to upgrade MySQL. Will there be any
>>>> >>>>> repercussions from doing this? Will this break any dependencies
> >> for
>>>> >>>>> Plesk? Do we need to upgrade the MySQL server package as well as
> >> the
>>>> >>>>> MySQL client utilities package?
>>>> >>>>>
>>>> >>>>> Thanks
==================================
Interesting... Looks like they rebuild latest PHP for MySQL 5.x. I
>>> >>>> checked another PHP build available at the same link - it depends
> on
>>> >>>> MySQL client libs v4.1:
>>> >>>>
>>> >>>> # rpm -qp php-mysql-5.1.6-1.2.1.centos.i386.rpm --requires
>>> >>>> config(php-mysql) = 5.1.6-1.2.1.centos
>>> >>>> libc.so.6
>>> >>>> libc.so.6(GLIBC_2.0)
>>> >>>> libc.so.6(GLIBC_2.1.3)
>>> >>>> libcrypt.so.1
>>> >>>> libcrypto.so.4
>>> >>>> libm.so.6
>>> >>>> libmysqlclient.so.14
>>> >>>> libmysqlclient.so.14(libmysqlclient_14)
>>> >>>> libnsl.so.1
>>> >>>> libssl.so.4
>>> >>>> libz.so.1
>>> >>>> php = 5.1.6-1.2.1.centos
>>> >>>> php-pdo
>>> >>>> php-pdo-abi = %{pdoabi}
>>> >>>> rpmlib(CompressedFileNames) <= 3.0.4-1
>>> >>>> rpmlib(PayloadFilesHavePrefix) <= 4.0-1
>>> >>>>
>>> >>>>
>>> >>>> Grab PHP 5.1.6-1.2.1 RPMs from there, they should work better.
>>> >>>>
>>> >>>> Thanks,
>>> >>>> Pavel
=================================
> Hi Pavel,
> >>>
> >>> Thanks for figuring out that there is a PHP 5.x package we can use
>> with
> >>> the existing MySQL 4.x packages.
> >>>
> >>> Unfortunately, I have found another obstacle. The php-mysql-5.1.6-
>> 1.2.1
> >>> package depends on the php-pdo package, which in turn depends on
> >>> development libraries from SQLite version 3. The current version of
> >>> SQLite installed on the server is 2.8.17, provided by the
> >>> sqlite2-2.8.17-200608292131 RPM. Nothing seems to depend on this
> >>> current SQLite package, but I wanted to be sure it was safe to
>> upgrade
> >>> with the CentOS sqlite-3.3.3-1.2.i386.rpm package. Please let me
>> know.
> >>> Thanks
==================================
> Hi Pavel,
> >>
> >> SiteBuilder won't even publish dynamic content to a Plesk node that
> >> does
> >> not have the php-sqlite2-1.0.2-200608291848.i386 RPM installed. That
> >> RPM depends upon a PHP package >= 4.3 and <= 4.4. Therefore, it seems
> >> an upgrade to 5.x would not be feasible.
> >>
> >> I tried to do the upgrade anyhow, based on your recommendation. I had
> >> to pass the "--nodeps" option to the RPM upgrade command to get around
> >> the failed dependency for the php-sqlite2-1.0.2-200608291848.i386
> >> package. After some minor config file tweaks and restarting Apache,
> >> websites on the Plesk node were working with the 5.1.6-1.2.1 RPMs of
> >> PHP. However, now the eShop module complained about the SQLite
> >> extension not being available. Also, no pages that used dynamic
> >> content
> >> were working at this point (the blog module, the news module, etc.).
> >>
> >> To try to get around this, I attempted to load the sqlite.so module
> >> from
> >> the php-sqlite2-1.0.2-200608291848.i386 package. As I expected this
> >> did
> >> not work. Also, this version of PHP was compiled with the
> >> "--without-sqlite" option. It does not look like the CentOS provided
> >> RPMs of PHP 5.1.6 will work.
> >>
> >> I have had to revert to version 4.3.9 of PHP for the time being so
> >> customers have websites that function to some degree.
> >>
> >> From what I can tell the problems we are experiencing with the eShop
> >> module stem from a change the PHP developers made to the way
> parameters
> >> are allowed to be passed to functions. This change was made
> >> approximately a year and a half ago. If that is indeed the case, why
> >> has this not yet been resolved by SWSoft? Shouldn't SWSoft provide
> >> working packages of either the eShop module or PHP for customers who
> >> want to publish from SiteBuilder to Plesk? Or at the very least
> SWSoft
> >> should be able to provide a suitable workaround to the problem. Thus
> >> far we have not been given any definitive responses on how to get this
> >> particular module to work on our Plesk nodes. We have only been
> given
> >> advice that seems like guesswork.
> >>
> >> If I am missing something when doing the PHP upgrade, please let me
> >> know. It is possible I have made some mistake along the way. If this
> >> is the case, we need to know about it. We need to have everything
> >> working properly soon.
> >>
> >> Thank you
===================================
This sounds quite strange as I do remember number of customers who used
> PHP 5.1.x RPMs from CentOS Plus repository to update their systems.
> In this case the next step to get this resolves would be to wait until
> development team will come up with a solution for eShop module which
> will allow it to work properly on the system with PHP 4.3.9.
>
> Thanks,
> Pavel
======================================
Hi Pavel,
I don't consider waiting for the development team to rewrite the eShop
module to be a viable option. The modules provided with SiteBuilder
should work with default installations of Plesk. Rather than wait, I
have compiled PHP 5.2.1 with the necessary extension support. The eShop
and other dynamic modules appear to be working correctly now. This is
far from an ideal solution, as the point of using software like those
sold by SWSoft is to lessen the burden of system administration so that
hosting providers may concentrate on running their businesses. Having
to maintain our own software just to make sure components sold by SWSoft
function correctly detracts from the benefits of running hosting
automation software.
Facebook
Twitter
