The file client.domain.backup.php is part of Plesk distribution.

[LennyB]

Hello,

Since I have tried to update my plesk to 9.2.1 version, I have the following error clicking on domain name through "Manage domains" link : The file client.domain.backup.php is part of Plesk distribution. It cannot be run outside of Plesk environment. , same thing when I try to setup the firewall : The file index.php is part of Plesk distribution. It cannot be run outside of Plesk environment. .

You can find the update report attaching to this post.

Thanks for your help

Best regards

Lenny

 

[Flagg]

LennyB,

Is Parallels Plesk Panel by any chance running on a container in Parallels Virtuozzo Containers? You may be exceeding resource limits for it. Please check the following article on how to fix this:

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

 

[LennyB]

Plesk is running on a dedicated server.

Thanks again for the help.

 

[LennyB]

Is it possible de make a fresh install of Plesk on a dedicated server keeping the current database and the actuals settings ?

 

[LennyB]

Up Any clue on this ?

 

[danliker]

have you checked free disk space ?

 

[LennyB]

/dev/md1
3.7 GB sur 9.8 GB utilisé ; 5.7 GB disponible
/dev/md2
14.8 GB sur 65.2 GB utilisé ; 47.1 GB disponible

It seems to be good

I have tried to update to plesk version 9.2.2, same problem...

 

[LennyB]

Since yesterday, I have noticed that the Plesk Updater status is :
Installation is running / Autoinstaller busy

Should I restart my server ?

 

[realaaa@]

your log file says that the update has failed - and if you have a mix of Plesk packages for different versions then such error is not the worst thing that can happen

I recommend you to check what Plesk packages are currently installed:

# rpm -qa | grep psa-

And at first you should make sure that you have properly completed the upgrade, usually this solves most problems. That's easier to say than do though, so if you don't know where to start consider finding a good Plesk technician.

 

[LennyB]

Here is the result of the # rpm -qa | grep psa- command

psa-api-8.0.1-fc4.build80060904.19
psa-hotfix4-8.0.1-fc4.build80060727.19
psa-imp-4.1.1-fc4.build80060613.20
psa-ingo-1.1.1-fc4.build80060613.20
psa-turba-2.1.1-fc4.build80060613.20
psa-bf1942-1.0.0-fc4.build80060613.20
psa-manual-custom-skin-guide-9.0.1-0.279670
psa-ftputil-2.1.1-9.98077
psa-api-9.2.1-fc4.build92090422.13
psa-api-rpc-9.2.1-fc4.build92090422.13
psa-logrotate-3.7-fc4.build92090714.19
psa-proftpd-xinetd-1.3.1-fc4.build92090714.19
psa-api-rpc-9.2.2-fc4.build92090714.19
psa-courier-imap-add-8.0.1-fc4.build80060613.20
psa-8.0.1-fc4.build80060613.20
psa-hotfix1-8.0.1-fc4.build80060618.11
psa-horde-3.1.3-fc4.build80061018.17
psa-hotfix5-8.0.1-fc4.build80060903.14
psa-hotfix7-8.0.1-fc4.build80061018.17
psa-tomcat-configurator-8.0.1-fc4.build80060615.20
psa-spamassassin-8.0.1-fc4.build80060613.20
psa-kronolith-2.1.1-fc4.build80060613.20
psa-passwd-3.0-fc4.build80060613.20
psa-autoinstaller-3.4.1-090204.18
psa-qmail-1.03-fc4.build92090422.13
psa-selinux-9.2.2-fc4.build92090714.19
psa-proftpd-1.3.1-fc4.build92090714.19
psa-locale-base-en-US-9.2.2-09071013
psa-migration-manager-8.0.1-fc4.build80060904.19
psa-agent-1.4.1-80060613.20
psa-firewall-1.0.1-fc4.build80060713.16
psa-vpn-2.0.1-fc4.build80060613.20
psa-bf2-1.0.0-fc4.build80060613.20
psa-watchdog-2.0.1-fc4.build80060613.20
psa-sbm3-1.0-46
psa-coldfusion-support-8.0.1-fc4.build80060613.20
psa-php5-configurator-1.5.1-fc4.build92090422.13
psa-locale-base-en-US-9.2.1-09042016
psa-mail-driver-common-9.2.1-fc4.build92090422.13
psa-migration-manager-9.2.1-fc4.build92090422.13
psa-migration-manager-9.2.2-fc4.build92090714.19
psa-locale-base-en-US-8.0.1-fc4.build80061018.17
psa-libpam-plesk-8.0.1-fc4.build80060613.20
psa-hotfix2-8.0.1-fc4.build80060713.16
psa-hotfix6-8.0.1-fc4.build80060928.14
psa-mailman-configurator-8.0.1-fc4.build80060613.20
psa-qmail-rblsmtpd-0.70-fc4.build80060613.20
psa-mnemo-2.1-fc4.build80060613.20
psa-api-rpc-8.0.1-fc4.build80060904.19
psa-backup-manager-8.0.1-fc4.build80060904.19
psa-fileserver-1.0.0-fc4.build80060613.20
psa-atis-1.0-34
psa-mail-qc-driver-1.0.0-fc4.build92090422.13
psa-9.2.1-fc4.build92090422.13
psa-pylibplesk-9.2.2-fc4.build92090714.19
psa-api-9.2.2-fc4.build92090714.19
psa-9.2.2-fc4.build92090714.19

 

[realaaa@]

that's what I was afraid of - you have Plesk main packages installed from three different branches:

psa-8.0.1-fc4.build80060613.20
psa-9.2.1-fc4.build92090422.13
psa-9.2.2-fc4.build92090714.19

as well as some other packages, but this one is the most important.

Usually it happens when upgrade fails in the middle of psa package upgrade - in such cases some files are upgraded to 9.2 some are left from 8.0, of course it leads to all kinds of weird problems. More than this - Plesk database is usually half-upgraded too in this case.

Well - I probably scared you enough by now Good thing is that this can be fixed actually, but it requires some experience in fixing failed Plesk upgrades.

At first I recommend you to create a copy of all Plesk database backups from /var/lib/psa/dumps/

After that usual steps are:

1) Get latest preupgrade or daily backup of Plesk database from /var/lib/psa/dumps/
2) Restore it to return Plesk database to preupgrade 8.0 state
3) Run the upgrade - check Plesk upgrade logs in /tmp/ to see why it failed.
4) Fix the cause of that problem and return to step 1.

At some point you will know each and every cause of those upgrade failure so you can fix them all and run the upgrade last time.

Of course you should understand that this is a very brief explanation of common procedure, it might be a little or totally different in your case. The only thing I can say for sure now is that you have packages from different versions of Plesk installed and this should be fixed by upgrading all packages to the latest version.

Sorry, have to go now. Good luck and let us know how it goes!

 

[LennyB]

Thanks a lot for your help, I will check this out

 

[LennyB]

Should I backup my plesk.key, if so where I can find it ?
My key is renewed every month along with my dedicated server

 

[realaaa@]

license key is usually in /etc/psa/ but there is no need to backup it - upgrade does not delete it, the worst thing it can do with license is automatically upgrade it from 8.x to 9.x license format.