Upgrade to 7.5.4 failed All webpage gone

[CBiLL]

Thanks,

Basic Package installed sucessfully.

Removing the maildrop did the trick but Tomcat had me puzzled because I dont have it install at all.

And no it wasn't live server yet when I was trying out the package so I didn't think it left behind some packages when I am sure I had removed it before I put it into production beside it ran fine for almost a year and all those Plesk past upgrade had never complained about it unitl now.



Bill

 

[jamesyeeoc]

No problem. Tomcat may have been installed by the 7.5.2 updater at some time in the past. Who can really say?

 

[aernative]

--------------------------------------------------------
'/usr/kerberos/lib/libcom_err.so.3' -> `/home/httpd/vhosts/chroot/lib/libcom_err.so.3'
`/lib/i686/libc.so.6' -> `/home/httpd/vhosts/chroot/lib/libc.so.6'
`/usr/kerberos/lib/libgssapi_krb5.so.2' -> `/home/httpd/vhosts/chroot/lib/libgssapi_krb5.so.2'
`/lib/libdl.so.2' -> `/home/httpd/vhosts/chroot/lib/libdl.so.2'
`/etc/termcap' -> `/home/httpd/vhosts/chroot/etc/termcap'
done
Trying to apply 7.5.4 changes to database... done
Trying to generate Admin server configuration... Generating Admin server configuration... done

===> Installing Quotas
Trying to change mount options in /etc/fstab... done
/home has a xfs type. The quotacheck is not needed.
Trying to update component 'tomcat' in Components table... ERROR 1062 at line 1: Duplicate entry 'tomcat' for key 1

ERROR while trying to update component 'tomcat' in Components table

Aborting...
--------------------------------------------------------



I got this error aswell - Duplicate entry 'tomcat' - error, the common thing here is i am also updating from 7.5.2 to 7.5.4....

Heeeelllppp....

 

[by88]

I'm experiencing the same problem with Tomcat (and it's installed and upgraded) and I'm locked at 7.5.2 version.

===> Installing Quotas
Trying to change mount options in /etc/fstab... done
Run quotacheck. This may take some time.
Trying to check for quota support... done
Trying to update component 'tomcat' in Components table...
ERROR while trying to update component 'tomcat' in Components table
Check the error reason(see log file: /tmp/psa_7.5.4_FedoraCore_1_build75050824.12_upgrade.log), fix and try again

Aborting...

error: %post(psa-7.5.4-fc1.build75050824.12) scriptlet failed, exit status 1


Great problems! all sites display the default Apache FC1 page!

Any help from sw-soft for this bug?

 

[aernative]

oh my god - i didn't check that - thank you sw-soft, my whole server is now down and evey site on it....

HELP please!

 

[aernative]

right - ive found a temp fix, but i dont know what else needs looking at -

goto -
/etc/httpd/conf

i renamed the current httpd.include and httpd.conf files to http.include.afterupdate and httpd.conf.afterupdate.

Then sort files by date and rename one of the bakups there to the origional file names.

Restart apache and all seems to be working.

I have submitted a ticket with sw-soft so i'll post again when i get the official line

 

[aernative]

SW-Soft are quick!!! just got this back from them -
--------------------------------------------------------------------

Please run the following one-line command and restart the upgrade:

# mysql -uadmin -p`cat /etc/psa/.psa.shadow` psa -e"delete from Components where name='tomcat'"

--------------------------------------------------------------------

will let you know how i got on! 10/10 to sw-soft for getting back so quickly...

WOOOHOO! just worked!

Update of system was succesfully completed.

Short update summary:

 

[by88]

I opened a ticket too and I received the same answer of course:

> Hello,
>
> Please run the following one-line command and restart the upgrade:
>
> # mysql -uadmin -p`cat /etc/psa/.psa.shadow` psa -e"delete from Components
> where name='tomcat'"

It worked for me.

Thanks.

 

[CBiLL]

yeah I had remove the tomcat to get it sucessfully upgraded and I wonder why it got put in there in the first place thou.


I also had to keep spamassassin at 2.63 to keep my Plesk spam assassin support but the new training looks much better and more understandable to use however I haven't mess with it yet.



Bill

 

[CiViX]

I had the same problem as described in the first post, but fixed it using the mysql-command that PLESK-support recommended.

I also ended up with an (almost) empty http.include-file, and had to copy back a backup-file a few hours old :-(

Anyway, everything seems to work now, except that PLESK still shows 7.5.3 as the version... I have three servers, two of them failed on the tomcat-component-error, one didn't. The server that upgraded sucessfully on the first try shows 7.5.4, the other two show 7.5.3, although the Updater shows that all packages are upgraded.

Any idea how to fix this?

 

[panaman]

mine is showing the same thing....

[root@geekempirehosting base]# rpm -qa psa
psa-7.5.4-rhel3.build75050824.12
psa-7.5.2-rhel3.build75050130.17

 

[CiViX]

Here's something that fixed it for me:

Check if you have two versions of psa installed after the failed upgrade:
# rpm -qa psa

If the result is something like:

psa-7.5.3-rhel3.build75050506.13
psa-7.5.4-rhel3.build75050824.12

then you need to remove the 7.5.4 from the rpm database:

# rpm -e --justdb --noscripts --nodeps
psa-7.5.4-rhel3.build75050824.12

(The exact name might vary if you have older/newer build. Check with the output from the first command.)

Check that only one instance of psa is left:

# rpm -qa psa
psa-7.5.3-rhel3.build75050506.13

Then you must remove some tomcat-stuff from the psa database:

# mysql -uadmin -p`cat /etc/psa/.psa.shadow` psa -e"delete from Components where name='tomcat'"

and also:

# mysql -uadmin -p`cat /etc/psa/.psa.shadow` psa -e"delete from Components where name='tomcat4'"

At last force an upgrade to 7.5.4 again:

# rpm -Ufh --force psa-7.5.4-rhel3.build75050824.12.i586.rpm

Again the exact filename might vary.

If you upgraded from the webinterface then you'll find the rpm under /root/psa/PSA_7.5.4/ somewhere.

I use RHEL3, so my psa-rpm is in:
/root/psa/PSA_7.5.4/rpm_RedHat_el3/base/

I hope this helps others with this upgrade-problem!

 

[Cranky]

CiViX, in some cases that will work, but in many cases psa database is partially upgraded to version 750, or other times plesk files are upgraded without the database being upgraded, in both these cases your instructions will not fix the problem.

You don't need to run the following:

# mysql -uadmin -p`cat /etc/psa/.psa.shadow` psa -e"delete from Components where name='tomcat4'"

You should just run:

# mysql -uadmin -p`cat /etc/psa/.psa.shadow` psa -e"delete from Components where name='tomcat"

The entry for tomcat4 is correct. Your post is helpful, don't get me wrong, but it can also potentially cause more complicated problems.

 

[CiViX]

You don't need to run the following:

# mysql -uadmin -p`cat /etc/psa/.psa.shadow` psa -e"delete from Components where name='tomcat4'"

You should just run:

# mysql -uadmin -p`cat /etc/psa/.psa.shadow` psa -e"delete from Components where name='tomcat"

The entry for tomcat4 is correct. Your post is helpful, don't get me wrong, but it can also potentially cause more complicated problems.

In my case it was not enough to just remove "tomcat", I also needed to remove "tomcat4". First when I removed both of these from the Components-table I was able to complete the upgrade.

I was instructed by PLESK to do this, so I guess it should be safe.

 

[panaman]

this is kind of wierd...

I log into my plesk interface this morning and now it says I am running 7.5.4

I still have both 7.5.4 and 7.5.2 rpms installed though

 

[fhosting]

Hello!
Bu tI have problem with upgrade from plesk 7.5.3 to 7.5.4:

rpm -i psa-7.5.4-rh9.build75050824.12.i586.rpm
===> Updating /etc/psa/psa.conf...

Trying to define super-server internet daemon type... xinetd
Trying to check if xinetd daemon is running... done


===> Checking for previous installation ... found.
Trying to stop MySQL server... done
Trying to start MySQL server... done
Trying to establish test connection... connected
Making some checks before upgrading

Now BIND server shutting down...

Trying to stop BIND server... done
Trying to start BIND server... done

BIND server starts Ok.


===> Checking for the necessary system accounts
Checking for the system groups and users necessary for Qmail...
Checking for the group 'nofiles'...
Group 'nofiles' already exists

Checking for the user 'alias'...
User 'alias' already exists

Checking for the user 'qmaild'...
User 'qmaild' already exists

Checking for the user 'qmaill'...
User 'qmaill' already exists

Checking for the user 'qmailp'...
User 'qmailp' already exists

Checking for the group 'qmail'...
Group 'qmail' already exists

Checking for the user 'qmailq'...
User 'qmailq' already exists

Checking for the user 'qmailr'...
User 'qmailr' already exists

Checking for the user 'qmails'...
User 'qmails' already exists

Checking for the group 'popuser'...
Group 'popuser' already exists

Checking for the user 'popuser'...
User 'popuser' already exists

Checking for the system groups and users necessary for MySQL...
Checking for the group 'mysql'...
Group 'mysql' already exists

Checking for the user 'mysql'...
User 'mysql' already exists

Checking for the system groups and users necessary for admin server...
Checking for the group 'psaadm'...
Group 'psaadm' already exists

Checking for the user 'psaadm'...
User 'psaadm' already exists

Checking for the system groups and users necessary for Apache...
Checking for the group 'apache'...
Group 'apache' already exists

Checking for the user 'apache'...
User 'apache' already exists

Checking for the group 'psaftp'...
Group 'psaftp' already exists

Checking for the user 'psaftp'...
User 'psaftp' already exists

Checking for the group 'psaserv'...
Group 'psaserv' already exists

Checking for the group 'psaserv'...
Trying to add supplementary group 'psaserv' for user 'apache'... already there
Checking for the group 'psaserv'...
Trying to add supplementary group 'psaserv' for user 'psaftp'... already there
Checking for the group 'psaserv'...
Trying to add supplementary group 'psaserv' for user 'psaadm'... already there
group psacln already exists
Standard build detected. Upgrading canceled, because only
5.0.x versions supported for upgrading from Standard to RPM
builds.

error: %pre(psa-7.5.4-rh9.build75050824.12) scriptlet failed, exit status 1
error: install: %pre scriptlet failed (2), skipping psa-7.5.4-rh9.build75050824.12


And if I run rpm -qa psa i have no packages installed!
How to solve these problem?

 

[madsere]

CiViX

I had the exact same problem you described and recoved using your guide.

Great job, thanks!

 

[matteveryday]

I tried doing this fix without removing tomcat4. When I tried to upgrade to 7.5.4 I got this error message:

===> Installing psa database
Trying to check psa database... Trying to find psa database...

ERROR while trying to mysql datadir not found
Check the error reason(see log file: /tmp/psa_7.5.4_FedoraCore_2_build75050824.1 2_upgrade.log), fix and try again

Aborting...

error: %post(psa-7.5.4-fc2.build75050824.12) scriptlet failed, exit status 1