stuck on upgrade from 7.1.7 to 7.5.4

General Discussion of atomic repo and development projects.

Ask for help here with anything else not covered by other forums.
Galactic Zero
Forum Regular
Forum Regular
Posts: 471
Joined: Mon Dec 06, 2004 10:43 pm

stuck on upgrade from 7.1.7 to 7.5.4

Unread post by Galactic Zero »

Ok, tried to upgrade today and got the following failure message:

error: Failed dependencies:
libgcc_s_plesk.so.1 is needed by psa-7.5.4-rhel3.build75050824.12
libgcc_s_plesk.so.1(GCC_3.0) is needed by psa-7.5.4-rhel3.build75050824.12
libgcc_s_plesk.so.1(GLIBC_2.0) is needed by psa-7.5.4-rhel3.build75050824.12
libstdc++_plesk.so.6 is needed by psa-7.5.4-rhel3.build75050824.12
libstdc++_plesk.so.6(CXXABI_1.3) is needed by psa-7.5.4-rhel3.build75050824.12
libstdc++_plesk.so.6(GLIBCXX_3.4) is needed by psa-7.5.4-rhel3.build75050824.12
plesk-libgcc-3_4 is needed by psa-7.5.4-rhel3.build75050824.12
plesk-libstdc++-3_4 is needed by psa-7.5.4-rhel3.build75050824.12
libgcc_s_plesk.so.1 is needed by psa-hotfix2-7.5.4-rhel3.build75051014.16
libgcc_s_plesk.so.1(GCC_3.0) is needed by psa-hotfix2-7.5.4-rhel3.build75051014.16
libgcc_s_plesk.so.1(GLIBC_2.0) is needed by psa-hotfix2-7.5.4-rhel3.build75051014.16
libstdc++_plesk.so.6 is needed by psa-hotfix2-7.5.4-rhel3.build75051014.16
libstdc++_plesk.so.6(CXXABI_1.3) is needed by psa-hotfix2-7.5.4-rhel3.build75051014.16
libstdc++_plesk.so.6(GLIBCXX_3.4) is needed by psa-hotfix2-7.5.4-rhel3.build75051014.16
libgcc_s_plesk.so.1 is needed by psa-hotfix-7.5.4-rhel3.build75050926.17
libgcc_s_plesk.so.1(GCC_3.0) is needed by psa-hotfix-7.5.4-rhel3.build75050926.17
libgcc_s_plesk.so.1(GLIBC_2.0) is needed by psa-hotfix-7.5.4-rhel3.build75050926.17
libstdc++_plesk.so.6 is needed by psa-hotfix-7.5.4-rhel3.build75050926.17
libstdc++_plesk.so.6(CXXABI_1.3) is needed by psa-hotfix-7.5.4-rhel3.build75050926.17
libstdc++_plesk.so.6(GLIBCXX_3.4) is needed by psa-hotfix-7.5.4-rhel3.build75050926.17
libgcc_s_plesk.so.1 is needed by psa-pre-keyupdate-7.5.4-rhel3.build75050824.12
libgcc_s_plesk.so.1(GCC_3.0) is needed by psa-pre-keyupdate-7.5.4-rhel3.build75050824.12
libgcc_s_plesk.so.1(GLIBC_2.0) is needed by psa-pre-keyupdate-7.5.4-rhel3.build75050824.12
libstdc++_plesk.so.6 is needed by psa-pre-keyupdate-7.5.4-rhel3.build75050824.12
libstdc++_plesk.so.6(CXXABI_1.3) is needed by psa-pre-keyupdate-7.5.4-rhel3.build75050824.12
libstdc++_plesk.so.6(GLIBCXX_3.4) is needed by psa-pre-keyupdate-7.5.4-rhel3.build75050824.12
libgcc_s_plesk.so.1 is needed by psa-qmail-1.03-rhel3.build75050824.12
libgcc_s_plesk.so.1(GCC_3.0) is needed by psa-qmail-1.03-rhel3.build75050824.12
libgcc_s_plesk.so.1(GLIBC_2.0) is needed by psa-qmail-1.03-rhel3.build75050824.12
libstdc++_plesk.so.6 is needed by psa-qmail-1.03-rhel3.build75050824.12
libstdc++_plesk.so.6(CXXABI_1.3) is needed by psa-qmail-1.03-rhel3.build75050824.12
libstdc++_plesk.so.6(GLIBCXX_3.4) is needed by psa-qmail-1.03-rhel3.build75050824.12
psa-security = 7.1 is needed by (installed) psa-agent-1.3.2-2.5
psa = 7.1.7 is needed by (installed) psa-bu-7.1.7-rhel3.build71050228.12

Here is what I have for the libgcc:

[root@gz opt]# locate libgcc |more
/var/cache/yum/base/packages/libgcc-3.2.3-49.i386.rpm
/var/cache/yum/base/headers/libgcc-0-3.2.3-49.i386.hdr
/var/spool/up2date/libgcc-3.2.3-49.i386.hdr
/var/spool/up2date/libgcc-3.2.3-52.i386.hdr
/usr/sbin/libgcc_post_upgrade
/usr/lib/gcc-lib/i386-redhat-linux/3.2.3/libgcc.a
/usr/lib/gcc-lib/i386-redhat-linux/3.2.3/libgcc_eh.a
/usr/lib/gcc-lib/i386-redhat-linux/3.2.3/libgcc_s.so
/usr/lib/gcc-lib/i386-redhat-linux7/2.96/libgcc.a
/lib/libgcc_s.so.1
/lib/ssa/gcc-lib/i386-redhat-linux-gnu/3.5-tree-ssa/libgcc.a
/lib/ssa/gcc-lib/i386-redhat-linux-gnu/3.5-tree-ssa/libgcc_eh.a
/lib/ssa/libgcc_s.so.1
/lib/ssa/libgcc_s.so
/lib/libgcc_s-3.2.3-20040701.so.1
[root@gz opt]# rpm -q libgcc
libgcc-(none)-3.2.3-53
[root@gz opt]# rpm -qa |grep libgcc
libgcc-(none)-3.2.3-53
libgcc-ssa-(none)-3.5ssa-0.20030801.48

And a Yum update for libgcc resulted in :

root@gz opt]# yum update libgcc
Gathering header information file(s) from server(s)
Server: Atomic Rocket Turtle - 3ES - App Vault RPMS
Server: Atomic Rocket Turtle - 3ES - Atomic PSA-Compatible RPMS
Server: Atomic Rocket Turtle - 3ES - Base OS RPMS mirror
Server: Atomic Rocket Turtle - 3ES - SW-Soft PSA 7.1 RPMS
Server: Atomic Rocket Turtle - 3ES - OS Update RPMS mirror
Finding updated packages
Downloading needed headers
libgcc is installed and the latest version.
No actions to take..


So, what do I need to fix please?
Franklyn Halamka
Still learning my way around Linux Security.
http://www.galacticzero.net
Galactic Zero
Forum Regular
Forum Regular
Posts: 471
Joined: Mon Dec 06, 2004 10:43 pm

Unread post by Galactic Zero »

Fixed this..

Seems I needed to update the plesk stuff from the Third_Party_RHel3 dir first..

Would have been nice if they included that in the upgrade instructions from SW-Soft.
Franklyn Halamka
Still learning my way around Linux Security.
http://www.galacticzero.net
scott
Atomicorp Staff - Site Admin
Atomicorp Staff - Site Admin
Posts: 8355
Joined: Wed Dec 31, 1969 8:00 pm
Location: earth
Contact:

Unread post by scott »

Weird, thats definitely in the yum channel.
Galactic Zero
Forum Regular
Forum Regular
Posts: 471
Joined: Mon Dec 06, 2004 10:43 pm

Unread post by Galactic Zero »

Don't know Scott. After upgrading I got a failure on PSA7.5.4 upgrade of:

mysqld (pid 8739) is running...
VERSION MISMATCH:
PLESK DATABASE VERSION: 075
PLESK INSTALLATION VERSION: 071

ERROR while trying to check version match

Aborting...

Looked at SW-Softs forums for a fix and they said it was related to two versions of tomcat being in the PSA DB or that the DB was corrupt. The entries it was speaking about was tomcat and tomcat4. At any rate the fix was to remove those entries from the PSA DB and force install of PSA 7.5.4 Well, that didn't work..

I was showing two versions of PSA installed via rpm -qa psa

[root@gz bin]# rpm -qa psa
psa-(none)-7.5.4-rhel3.build75050824.12
psa-(none)-7.1.7-rhel3.build71050228.12
[root@gz bin]#

Well, I finally opened a ticket with EV1 and they had to get Plesk involved to fix it. Said that the fix was a complicated one, an hour after I opened the ticket the had it fixed. :)

Very Strange.... But happy all is well.
Franklyn Halamka
Still learning my way around Linux Security.
http://www.galacticzero.net
Post Reply