Having problem install Plesk Panel 9

[rhunn71]

Guys,

I have problem install Plesk Panel 9 control panel after I ran yum -y update on CentOS 5.2. Here is the error I got.

Determining the packages that need to be installed.
ERROR: You have a newer version of the php-common package installed on your system.
The installation will not continue.

It seems that you installed latest packages from your operating system vendor's
site. To install the product packages successfully, you need to point the
auto-installer to the vendor's package repository. To do this, create a text
file with name .autoinstallerrc in the /root/ directory on the server, and add
the following line to the file:

ADDITIONAL_SOURCE="<type>, <priority>, <url>, <username>, <password>"

where you should replace <type> with "repomd" value, <priority> with a number from
1 to 999 (999 is the highest priority), and <url> with a URL of the vendor
updates source. The values <username> and <password> are required
only if your vendor's site requires authentication. Save the file and
exit from the text editor. Then run the auto-installer again.
Not all packages were installed.
Please, resolve the above problem and try installing the packages again.
If you cannot resolve the problem on your own, contact product technical support for assistance.


Can you guys help me resolve this issue.

Thanks
Ronnie.

 

[Denis Sirochenko]

Hello Ronnie,

There is a Knowledge Base article on the subject:

http://kb.odin.com/en/6153

In other words, you have some php packages newer than those shipped with Plesk. It seems like it is the php-common package. You should find out from what repository it was installed from and tell Plesk autoinstaller to use this repository instead of 'native' Plesk's one. The procedure of setting autoinstaller to use your repository is described in your post quite clearly.

Would you share what exactly puzzles you?

 

[rhunn71]

Hello,

How do I find out what resposity does centos install so I can point it to Plesk autoinstall.

Thank in advance
Ronnie

 

[Denis Sirochenko]

Hello Ronnie,

A list of available repositories for CentOS can be fount at

http://wiki.centos.org/AdditionalResources/Repositories

Regards,

Denis

 

[dwiggins]

Can someone provide an example for RH Enterprise 4? How about 5?

Suppose someone had a license for RH Enterprise v4, and was using up2date. Or maybe someone built a fresh server off RHEL4 update 8 media.

can you provide a specific example of how to set up the ADDITIONAL_SOURCE line should look?

The only URLs I can find in the up2date configuration file are these:

noSSLServerURL=http://rhn-proxy01.city.host.com/XMLRPC

and

serverURL=https://rhn-proxy01.city.host.com/XMLRPC

I've plugged both of these into the .autoinstallrc file, and neither have the desired effect, as up2date doesn't use standard yum style repos. RHEL4 doesn't even have the OPTION of using yum. RHEL5 has the option of using yum, but if you're renting a server from a hosting company, and they've got RHN stuff set up so that you don't have to worry about updates, then you have to use the up2date protocol (which yum has a plug in to know how to use)

So, for these cases, is there a way to use the built in ability of the autoinstaller to use vendor supplied files, or are RHEL/up2date users stuck with hand resolving a giant stack of dependencies, or waiting for a newer release of plesk to come out that knows about the file revisions that come with the latest version of the OS?

I suppose it's too much to ask that the autoinstaller be modified in such a way is that it could figure out for itself that the system is configured to use vendor updates, and then look at whatever config files the update subsystem is using to figure out where to get the latest versions.

 

[atomicturtle]

RHEL4 does support the old 1.x yum repo format (hdr files), so provided the repo maintainers also create the header data along with the repodata you'll be good to go. The following is an example using the atomic channel for RHEL4:

vim /etc/sysconfig/rhn/sources

paste:

yum atomic http://www.atomicorp.com/channels/atomic/redhat/4/i386/

I actually have a plesk 9 repo for RHEL 4, but I didnt generate the header data You'd have to run yum 2.x or above to take advantage of it. I made a note in the archive wiki to support it

 

[dwiggins]

I guess I asked the wrong question

What I'm looking for is a specific example of how to construct a .autoinstallerrc ADDITIONAL_SOURCES entry that uses an up2date (NOT yum) server. For the THOUSANDS of people that have a PAID FOR license for Redhat Linux, and use up2date (because that's what they are provided), is there ANY WAY AT ALL to make this work?

if it's just not possible, can someone from Parallels please chime in and just straight up say it? While you're at it, go update this thread - http://forum.parallels.com/showthread.php?t=75841 - too.

If it's not currently possible, will it ever happen? Is it on the roadmap?

As it stands, every time RH releases an updated version of the OS (which happens roughly every 6 months), installing Plesk on top of that OS becomes a serious pain. In this instance, there isn't even an option to not do updates until after you've installed Plesk, because the box-stock OS is a later version than the installer knows how to deal with.

If Parallels releases an updated Plesk build, life gets easier for a week or two, until there's an updated version of some file on the RHN up2date servers, and you're back in weeds.

 

[atomicturtle]

I hear ya, and in fact the autoupdater was my idea. So you can blame me Back when I first laid out the featureset for it in 2002 it was never supposed to stick around this long. It was just supposed to be a bridge until things like yum got up to speed.

Ive added the yum 1.x header data so you can add the following plesk repository to up2date:

for RHEL 4 i386 add the following to /etc/sysconfig/rhn/sources

yum plesk http://www4.atomicorp.com/channels/plesk/9.2.1/redhat/4/i386

and for RHEL 4 x86_64 systems:
yum plesk http://www4.atomicorp.com/channels/plesk/9.2.1/redhat/4/x86_64

for RHEL 5 users, please note that up2date has been deprecated, you now use yum. For yum users you can add the plesk repo with:

wget -q -O - http://www.atomicorp.com/installers/atomic |sh

 

[dwiggins]

here's the real answer if you have paid-for RHN/up2date

• We checked that current Autoinstaller 3.4 supports RedHat "up2date"
utility and Parallels Plesk 9.2.2 can be installed on RHEL 4.8 server
if Autoinstaller detects that "up2date" is configured. Please refer to
RedHat documentation about configuring of 'up2date' service.

• To detect if "up2date" is configured Parallels Plesk Autoinstaller
performs the following actions:

1) It checks that "/etc/sysconfig/rhn/systemid" file does exist;
2) It checks that "/etc/sysconfig/rhn/up2date" file contains
networkSetup=1 parameter.

The problem is that this parameter became optional, so Autoinstaller
does not detect if "up2date" is configured, and therefore does not use
it.

You need to check "/etc/sysconfig/rhn/up2date" file and add
networkSetup=1 string if it does not exist.