General Discussion of atomic repo and development projects.
Ask for help here with anything else not covered by other forums.
henningl
Forum User
Posts: 37 Joined: Sat Mar 18, 2006 2:04 pm
Unread post
by henningl » Mon Jul 07, 2008 7:21 pm
Hi, I tried upgrading Plesk with yum, and mostly everything seems to have updatet just fine...
Dependency Installed: psa-hotfix3.x86_64 0:8.3.0-cos4.build83080109.18 psa-hotfix4.x86_64 0:8.3.0-cos4.build83080131.20 sw-libxml2.x86_64 0:2.6.27-5.centos43 sw-libxml2-python.x86_64 0:2.6.27-5.centos43 sw-libxslt.x86_64 0:1.1.20-5.centos43 sw-xmlrpc-c.x86_64 0:1.06.10-7.centos43
Updated: PPWSE.x86_64 0:1.1-cos4.build83071218.18 SSHTerm.noarch 0:0.2.2-cos4.build83071218.18 courier-imap.x86_64 0:3.0.8-cos4.build83071218.18 log4cpp-plesk.x86_64 0:0.3.5rc2-cos4.build83071218.18 miva-ssl-stub.i386 0:1.0.1-0.91137 mod_jk-ap20.x86_64 0:1.2.15-42psa.cos4.build83071218.18 perl-Apache-ASP.noarch 0:2.57-cos4.build83071218.18 perl-Font-AFM.noarch 0:1.18-63psa.cos4.build83071218.18 perl-FreezeThaw.noarch 0:0.43-63psa.cos4.build83071218.18 perl-HTML-Format.noarch 0:1.23-53psa.cos4.build83071218.18 perl-HTML-Tree.noarch 1:3.16-cos4.build83071218.18 perl-MLDBM.noarch 0:2.01-63psa.cos4.build83071218.18 perl-MLDBM-Sync.noarch 0:0.30-63psa.cos4.build83071218.18 perl-Text-Iconv.x86_64 0:1.2-24psa.cos4.build83071218.18 psa.x86_64 0:8.3.0-cos4.build83071218.18 psa-api.noarch 0:8.3.0-cos4.build83080131.20 psa-api-rpc.noarch 0:8.3.0-cos4.build83080131.20 psa-autoinstaller.x86_64 0:3.3.0-build33080201.10 psa-awstats-configurator.noarch 0:1.0.0-cos4.build83071218.18 psa-backup-manager.x86_64 0:8.3.0-cos4.build83080131.20 psa-coldfusion-support.noarch 0:8.3.0-cos4.build83071218.18 psa-courier-imap-add.x86_64 0:8.3.0-cos4.build83071218.18 psa-firewall.x86_64 0:1.0.1-cos4.build83071218.18 psa-ftputil.x86_64 0:8.3.0-cos4.build83071218.18 psa-horde.noarch 0:3.1.5-cos4.build83071218.18 psa-imp.noarch 0:4.1.5-cos4.build83071218.18 psa-ingo.noarch 0:1.1.4-cos4.build83071218.18 psa-libpam-plesk.x86_64 0:8.3.0-cos4.build83071218.18 psa-locale-base-en-US.noarch 0:8.3.0-cos4.build83071224.20 psa-logrotate.x86_64 0:3.7-cos4.build83071218.18 psa-mailman-configurator.x86_64 0:8.3.0-cos4.build83071218.18 psa-migration-manager.x86_64 0:8.3.0-cos4.build83080131.20 psa-mimp.noarch 0:1.0.2-cos4.build83071218.18 psa-miva.i386 0:8.3.0-cos4.build83071218.18 psa-mnemo.noarch 0:2.1.1-cos4.build83071218.18 psa-passwd.noarch 0:3.0.1-cos4.build83071218.18 psa-php4-configurator.noarch 0:1.3.0-cos4.build83071218.18 psa-proftpd.x86_64 0:1.3.0-cos4.build83071218.18 psa-proftpd-xinetd.x86_64 0:1.3.0-cos4.build83071218.18 psa-pylibplesk.x86_64 0:8.3.0-cos4.build83071218.18 psa-qmail.x86_64 0:1.03-cos4.build83071218.18 psa-qmail-rblsmtpd.x86_64 0:0.70-cos4.build83071218.18 psa-rubyrails-configurator.x86_64 0:1.1.6-cos4.build83071218.18 psa-sbm3.noarch 0:5.0-11 psa-selinux.noarch 0:8.3.0-cos4.build83071218.18 psa-spamassassin.x86_64 0:8.3.0-cos4.build83071218.18 psa-tomcat-configurator.noarch 0:8.3.0-cos4.build83071219.22 psa-turba.noarch 0:2.1.5-cos4.build83071218.18 psa-updates.noarch 0:8.3.0-cos4.build83080131.20 psa-vpn.x86_64 0:2.0.1-cos4.build83071218.18 psa-watchdog.x86_64 0:2.0.3-cos4.build83080131.20
Complete!
But when accessing the Plesk Control Panel it seems 8.2.1 is still running, and when checking further it seems I have both psa 8.2.1 and 8.3.0 installed? How do I complete the upgrade?
[root@ng ~]# rpm -q --queryformat=%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH} psa
psa-8.2.1-cos4.build82070918.10.x86_64psa-8.3.0-cos4.build83071218.18.x86_64[root@ng ~]#
[root@ng ~]#
DerFalk
Forum User
Posts: 35 Joined: Wed Jun 25, 2008 5:15 am
Location: Good old Germany
Unread post
by DerFalk » Tue Jul 08, 2008 12:42 am
try :
psa stopall
psa startall
... or try to reboot your server
breun
Long Time Forum Regular
Posts: 2813 Joined: Sat Aug 20, 2005 9:30 am
Location: The Netherlands
Unread post
by breun » Tue Jul 08, 2008 9:20 am
Remove the 8.2.1 package. And check the versions of the other Plesk packages and if you have multiple versions of them installed.
henningl
Forum User
Posts: 37 Joined: Sat Mar 18, 2006 2:04 pm
Unread post
by henningl » Tue Jul 08, 2008 12:33 pm
Any Idea's why the 8.2.1-packages wheren't removed automatically?
breun
Long Time Forum Regular
Posts: 2813 Joined: Sat Aug 20, 2005 9:30 am
Location: The Netherlands
Unread post
by breun » Tue Jul 08, 2008 3:22 pm
No, but I've seen things like that a lot. I guess Plesk's autoinstaller/Updater isn't that smart when things go wrong when upgrading Plesk packages.
henningl
Forum User
Posts: 37 Joined: Sat Mar 18, 2006 2:04 pm
Unread post
by henningl » Sun Jul 13, 2008 7:34 pm
Okey.. finally dared removing old psa, then did a stopall and startall.
Plesk control panel still claims version 8.2.1 in the title bar, and "psa v8.2.1_build83080131.20 os_CentOS 4.3" in the desktop "Server information" box. But if I go to the updater it says version 8.3 fully updated and no more updates (except the separate 8.4 one).
So Plesk cant decide what version it is
breun
Long Time Forum Regular
Posts: 2813 Joined: Sat Aug 20, 2005 9:30 am
Location: The Netherlands
Unread post
by breun » Mon Jul 14, 2008 4:34 am
Sounds like you may have multiple versions of some Plesk packages installed and/or your Plesk database may not have been upgraded correctly.
henningl
Forum User
Posts: 37 Joined: Sat Mar 18, 2006 2:04 pm
Unread post
by henningl » Mon Jul 14, 2008 9:41 am
Checked all psa-packages for duplicates, no more found.
Code: Select all
[root@ng psa]# rpm -q --queryformat=%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH} psa
psa-8.3.0-cos4.build83071218.18.x86_64[root@ng psa]#
Code: Select all
[root@ng psa]# cat /usr/local/psa/version
8.2.1 CentOS 4.3 83080131.20
[root@ng psa]#
And I cant seem to find the log from the updater to look for errors
/root/psa contains directories for 8.2.0, 8.3.0, and 8.4.0, but only 8.2.0 contains any rpm's
/home/swsoft contains only 8.2.0
/root/swsoft contains only 8.2.0
It seems like psa stuff are scattered all over the server.
breun
Long Time Forum Regular
Posts: 2813 Joined: Sat Aug 20, 2005 9:30 am
Location: The Netherlands
Unread post
by breun » Mon Jul 14, 2008 9:52 am
Yeah, Plesk switched owners. First it was swsoft and psa and now they're using parallels. You can remove all those directories as the autoinstaller/Plesk Updater will always download any needed RPM's.
It looks like your version file was not upgraded correctly. The version number is also in your psa database. What does mysql -uadmin -p`cat /etc/psa/.psa.shadow` -e"SELECT * FROM psa.misc WHERE param = 'version'" say?
And Plesk does not consist of just one RPM package. Most of them have 'build' in the name (while non-Plesk usually packages do not), so do you see any packages with multiple versions installed when you run rpm -qa | grep build | sort ?
Kalimari
Forum Regular
Posts: 526 Joined: Wed Jan 02, 2008 3:21 pm
Location: United Kingdom
Unread post
by Kalimari » Mon Jul 14, 2008 9:59 am
When running PSA updates using autoinstaller/Plesk Updater, I have got into the habit of removing previously downloaded RPM's first:
Code: Select all
rm -f /var/spool/up2date/psa-*
rm -f /var/spool/up2date/plesk-*
Seems to help avoid a whole world of pain!
breun
Long Time Forum Regular
Posts: 2813 Joined: Sat Aug 20, 2005 9:30 am
Location: The Netherlands
Unread post
by breun » Mon Jul 14, 2008 10:16 am
I have no idea why that would help since the autoinstaller/Plesk Updater does not touch /var/spool/up2date AFAIK. Maybe you have a Plesk repository setup in up2date? But even that shouldn't make a difference (and you wouldn't have to use the autoinstaller/Plesk Updater to update Plesk).
Kalimari
Forum Regular
Posts: 526 Joined: Wed Jan 02, 2008 3:21 pm
Location: United Kingdom
Unread post
by Kalimari » Mon Jul 14, 2008 10:56 am
It worked for me on RHEL4 and until I did this I was unable to go from 8.3 -> 8.4 and it has worked for at least one other on this forum...
Don't have access to SSH log in my current location, but from memory this allowed the PSA GUI/command line update command to complete the update.
I seem to remember also when going from 8.2 -> 8.3 that Plesk reported itself inconsistently in a similar way to henningl.
henningl - you could always list the contents of /var/spool/up2date first and check if there are inconsistently dated/named psa/plesk-* header files.
henningl
Forum User
Posts: 37 Joined: Sat Mar 18, 2006 2:04 pm
Unread post
by henningl » Mon Jul 14, 2008 11:22 am
SELECT * FROM psa.misc WHERE param = 'version' returns "0821"
/var/spool/up2date exists but is empty
rpm -qa | grep build | sort
returns no multiple build packages
To me it seems like the packages where installed, but something went wrong with the db update.
Where is the actual psa-files installed? /usr/local/psa seems to have version 8.2.1 in it.
breun
Long Time Forum Regular
Posts: 2813 Joined: Sat Aug 20, 2005 9:30 am
Location: The Netherlands
Unread post
by breun » Mon Jul 14, 2008 11:41 am
The Plesk files live in /usr/local/psa on Red Hat/CentOS/Fedora, yes. See the output of grep PRODUCT_ROOT_D /etc/psa/psa.conf | awk '{ print $2 }' .
If that seems to have Plesk 8.2.1 and rpm -q psa reports Plesk 8.3, then yes, something seems wrong. What does rpm -V psa say? It also seems your psa database is still at 8.2.1 (0821).
Maybe you can downgrade to Plesk 8.2.1, make sure there are no multiple versions of packages installed and try the upgrade to Plesk 8.3 again. I'd also make sure backups are available.
Kalimari
Forum Regular
Posts: 526 Joined: Wed Jan 02, 2008 3:21 pm
Location: United Kingdom
Unread post
by Kalimari » Mon Jul 14, 2008 11:56 am
henningl wrote: /var/spool/up2date exists but is empty
Well that dispels that myth
Good luck with the update this time round!