Plesk 7.5.1 to 7.5.2 Loop

[iascadmin]

We started the upgrade of the basic Plesk packages and other related packages, such as tomcat, apache, etc on Sunday afternoon and it kept going.

BTW, using psa_7.5.2_RedHat_el3_bui
ld75050130.17 though component info still shows 7.5.1-rhel3.build75041216.14

On Monday morning...

1) no ending email from our server

2) upon logging into plesk via the web [much faster than under 7.5.1] and going to the updater page, a warning message was at the top saying the installation was in progress

checking the logs in /tmp showed that the packages were installed successfully within an hour, but then had gone into the following loop...

===> Autoinstaller: start logging at Sun Feb 6 17:43:54 2005


Downloading list of all available versions and platforms
Downloading http://autoinstall.plesk.com/versions.inf


---
===> Autoinstaller: stopped logging at Sun Feb 6 17:43:55 2005

===> Autoinstaller: start logging at Sun Feb 6 17:44:06 2005

continuing like that until after 10 this morning

No problems in the /temp/psa_7.5.2_RedHat_el3_bui
ld75050130.17_problems.log nor in the psa_7.5.2_RedHat_el3_bui
ld75050130.17_upgrade.log

So checked in top - yep, autointaller there

kill -9 that PID

No more warning in Plesk updater that the installation is in progress but can't get to the list of packages [just says loading after clicking on 7.5.2]

So, then...

[root@elf tmp]# /etc/init.d/psa stop
===> Reading /etc/psa/psa.conf ...
/usr/local/psa/admin/bin/httpsdctl stop: httpd stopped
Stopping Plesk: [ OK ]
[root@elf tmp]# /etc/init.d/psa start
===> Reading /etc/psa/psa.conf ...
Starting psa-spamassassin service: [ OK ]
Two keys with the same key_number='PLSK************' found
/etc/psa/key.d/keyRMcwxH is older; will not be read
Processing config directory: /usr/local/psa/admin/conf/httpsd.*.include
/usr/local/psa/admin/bin/httpsdctl start: httpd started
Starting Plesk: [ OK ]

OK, OK. But still can't read the packages in Plesk to continue the update.

Can any one advise us on how to recover from this? Thanks in advance.

 

[iascadmin]

Ah, well. /sigh. Poor us. [or as my partner would say, kawawa tayo] No answers.

But we have found the solution through deligent searching of this forum and googling and experimentation to validate what we found.

It would appear that during the install that went into a loop, the rpm database became corrupted. This loop, by the way, extended into today, even after killing off autoinstaller and rpm processes as they appeared.

During a lull when no new autoinstaller or rpm processes were found using ps -ef we did the following.

Backup /var/lib/rpm to another directory and downloading those files to another site.

And then, in RHel3, at least, check your OS man pages and configuration to be certain.

rm -f /var/lib/rpm/__db*

Note that those are two underbars before the db

And then rebuild the databases

rpm -vv --rebuilddb

Note that those are two v's in the option switch, giving a very verbose output which you might want to send to a file using > filename.log at the end of that command.

More information can be found at

Repair a rpm database

We hope that others find this helpful.

 

[ChipMonk]

nice help

almost fine, but it didnt solve what is happennig to me.

i still cant see anything on the page

I was upgrading from 7.1.6 to 7.5.2

 

[iascadmin]

When we went from 7.1.6 to 7.5.1, we required a new key.

When you did the update, did you get a success or failure message after completion of the upgrade? Buried in that, or in the logs, may be a message concerning keys.

 

[ChipMonk]

well, it didnt ask me for the key or anyting, but i will look for it in morning with fresh brain....

i asked my service provide to lookinto it, and he asked me to pay 150 dollars

i will update for this in morning

 

[ChipMonk]

all seems to be okay....