Discussion in 'Plesk for Linux - 8.x and Older' started by ferrisr, Nov 20, 2005.
What is the chance of something going wrong with an upgrade from 7.5.2 to 7.5.4?
By the way, I hacked my own custom apache + php installation into the server, symlinking it all in, dunno if that makes a difference or not.
--- ===> Autoinstaller: start logging at Sun Nov 20 17:14:38 2005 Downloading list of all available versions and platforms Downloading http://autoinstall.plesk.com/versions.inf --- ===> Autoinstaller: stopped logging at Sun Nov 20 17:14:38 2005 ===> Autoinstaller: start logging at Sun Nov 20 17:14:38 2005 Preparing for packages installation...Error reading info for conflict check of installed package (null). Error reading info for conflict check of installed package (null). Error reading info for conflict check of installed package (null). ----- begin of output ----- Installing plesk-libgcc-3_4-3.4.3-2.i586.rpm Installing plesk-libstdc++-3_4-3.4.3-2.i586.rpm Installing spamassassin-2.63-0.2.i386.rpm Installing /PSA_7.5.4/rpm_RedHat_9/base/libidn-0.4.2-rh9.build75050824.12.i586.rpm /sbin/ldconfig: /usr/lib/libmysqlclient.so.12 is not a symbolic link /sbin/ldconfig: /usr/lib/libmysqlclient_r.so.12 is not a symbolic link /sbin/ldconfig: /usr/lib/libmysqlclient.so.12 is not a symbolic link /sbin/ldconfig: /usr/lib/libmysqlclient_r.so.12 is not a symbolic link Installing /PSA_7.5.4/rpm_RedHat_9/base/psa-qmail-1.03-rh9.build75050824.12.i586.rpm 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 Stopping : [ OK ] ===> Updating /etc/psa/psa.conf... Trying to set up default qmail permissions... done ===> Installing Qmail server Configuring Qmail... Trying to generate SSL certificates for TLS sessions... done Trying to register service qmail... using /sbin/chkconfig done Trying to start Qmail services... done Trying to register service qmail... using /sbin/chkconfig done Shutting down kernel logger: [ OK ] Shutting down system logger: [ OK ] Starting system logger: [ OK ] Starting kernel logger: [ OK ] Installing /PSA_7.5.4/rpm_RedHat_9/base/psa-proftpd-xinetd-1.2.10-rh9.build75050824.12.i586.rpm warning: /etc/proftpd.conf saved as /etc/proftpd.conf.rpmsave 5864 Reloading configuration: [ OK ] Installing /PSA_7.5.4/rpm_RedHat_9/base/psa-pre-keyupdate-7.5.4-rh9.build75050824.12.i586.rpm Installing /PSA_7.5.4/rpm_RedHat_9/base/psa-logrotate-3.7-rh9.build75050824.12.i586.rpm Installing /PSA_7.5.4/rpm_RedHat_9/base/psa-boost-1.32.0-6.i586.rpm /sbin/ldconfig: /usr/lib/libmysqlclient.so.12 is not a symbolic link /sbin/ldconfig: /usr/lib/libmysqlclient_r.so.12 is not a symbolic link Installing /PSA_7.5.4/rpm_RedHat_9/opt/bu/perl-IO-Ftp-0.05-rh9.build75050824.12.noarch.rpm Installing /PSA_7.5.4/rpm_RedHat_9/opt/bu/perl-MIME-Lite-2.117-rh9.build75050824.12.noarch.rpm Installing /PSA_7.5.4/rpm_RedHat_9/base/Mambo-4.5.2-7505.noarch.rpm Installing /PSA_7.5.4/rpm_RedHat_9/base/psa-7.5.4-rh9.build75050824.12.i586.rpm Installing /PSA_7.5.4/rpm_RedHat_9/base/psa-hotfix-7.5.4-rh9.build75050926.17.i586.rpm Installing /PSA_7.5.4/rpm_RedHat_9/base/psa-hotfix2-7.5.4-rh9.build75051014.16.i586.rpm Installing /PSA_7.5.4/rpm_RedHat_9/base/psa-hotfix3-7.5.4-rh9.build75051115.01.i586.rpm Installing /PSA_7.5.4/rpm_RedHat_9/base/psa-courier-imap-add-7.5.4-rh9.build75050902.17.i586.rpm Installing /PSA_7.5.4/rpm_RedHat_9/base/courier-imap-3.0.8-rh9.build75050824.12.i586.rpm Installing /PSA_7.5.4/rpm_RedHat_9/base/psa-api-common-7.5.4-rh9.build75051014.16.noarch.rpm Installing /PSA_7.5.4/rpm_RedHat_9/base/psa-api-cli-7.5.4-rh9.build75051014.16.noarch.rpm Installing /PSA_7.5.4/rpm_RedHat_9/opt/api/psa-api-rpc-7.5.4-rh9.build75050930.11.noarch.rpm Installing /PSA_7.5.4/rpm_RedHat_9/opt/api/psa-agent-1.3.5-75050930.11.noarch.rpm Installing /PSA_7.5.4/rpm_RedHat_9/base/psa-key-7.5-rh9.build75050824.12.noarch.rpm Installing /PSA_7.5.4/rpm_RedHat_9/base/psa-locale-base-en-US-7.5.4-rh9.build75051115.01.noarch.rpm Installing /PSA_7.5.4/rpm_RedHat_9/opt/bu/psa-bu-7.5.4-rh9.build75050926.17.i586.rpm Installing /PSA_7.5.4/rpm_RedHat_9/opt/migration/psa-migration-manager-7.5.4-rh9.build75050930.11.i586.rpm Installing /PSA_7.5.4/rpm_RedHat_9/opt/modules/firewall/psa-firewall-1.0.1-rh9.build75050824.12.i586.rpm Installing /PSA_7.5.4/rpm_RedHat_9/opt/modules/vpn/psa-vpn-1.0.0-rh9.build75050824.12.i586.rpm Installing /PSA_7.5.4/rpm_RedHat_9/opt/modules/fileserver/psa-fileserver-1.0.0-rh9.build75050824.12.i586.rpm Installing /PSA_7.5.4/rpm_RedHat_9/opt/docs/psa-manual-custom-skin-guide-7.5.4-rh9.build75050824.12.noarch.rpm file /usr/bin/deliverquota from install of courier-imap-3.0.8-rh9.build75050824.12 conflicts with file from package maildrop-1.6.0-1.9.rh90.art file /usr/bin/maildirmake from install of courier-imap-3.0.8-rh9.build75050824.12 conflicts with file from package maildrop-1.6.0-1.9.rh90.art ----- end of output ----- ===> Autoinstaller: stopped logging at Sun Nov 20 17:17:44 2005 ***** end of log file ***** I went for it and got that, is anything going to be messed up, and how can i fix it so it installs the upgradeS?
Looks like you'll have to uninstall the 'maildrop' package from ART to get past that point. Then you can re-install it afterwards. This was an issue covered early on when 7.5.4 was first released, as well as several other packages (such as the christmas skins from Plesk) As to your custom apache and php, I would imagine that there might be some work for you to do after the installer gets done. Make sure you have backups of all the config files for apache and php...
I'm not sure where that maildrop package came from, so i dont know where it is to reinstall it later. Also, when adding a domain, i now get: Unable to check SiteAppPackage requires: usermng: Failed getting quota: Function not implemented System error 38: Function not implemented 0: /usr/local/psa/admin/plib/class.DomainControlForm.php:994 psaerror(string "Unable to check SiteAppPackage requires: usermng: Failed getting quota: Function not implemented System error 38: Function not implemented") 1: /usr/local/psa/admin/plib/class.DomainControlForm.php:316 domaincontrolform->_detect_site_builder(string "vrt_hst", boolean true, boolean true, string "53", string "nilesc.bafserv.net", string "email@example.com", string "0") 2: /usr/local/psa/admin/htdocs/domains/dom_ctrl.php3:140 domaincontrolform->assign(object of type bsdomain)
maildrop package came from the atomicrocketturtle (ART) repository, possibly you may have qmail-scanner installed? In any case, you can download the rpm from his site (atomicrocketturtle.com) and re-install it afterwards.
Hmm, I did have it installed, but I'm not using it anymore. Can I just leave it uninstalled?
If you are not using it anymore, then I would recommend uninstalling the qmail-scanner package as well. No sense in leaving things partially installed when you are not using them. So "rpm -e qmail-scanner maildrop"
Will this mess up the email system at all? I can't have any downtime :-/
I would imagine that if you were to just uninstall maildrop (needed by qmail-scanner) might have an affect on email, you say you don't use qmail-scanner anymore, but if it is currently still setup and scanning emails, then I would recommend you either get rid of it entirely, or re-install the maildrop afterwards.
Hmm, what config files/etc need to be edited to remove it completely? I'm a n00b at qmail!
We don't recommend dumping qmail-scanner, but if that is what you want to do, I would just: yum remove qmail-scanner Make sure you check the list of dependencies which it may also remove to make sure it's only going to do the ones directly related to qmail-scanner (like maildrop). Off hand, I don't remember what deps get installed upon initial qmail-scanner installation.... Or you can use rpm: rpm -e qmail-scanner maildrop
I don't personally care if I dump it or not, I just want to have this upgrade go smoothly with no bumps
bafserv pastestore # rpm -e qmail-scanner maildrop error: package qmail-scanner is not installed bafserv pastestore # rpm -e maildrop error: package maildrop is not installed
I ran yum and installed the new plesk, it installed fine. Half of plesk looks new, half of it looks like the old one, it still says 7.5.2. Trying to install 7.5.4 base packages, I get: Retrieving Plesk files --- Preparing for packages installation... ----- begin of output ----- Installing /PSA_7.5.4/rpm_RedHat_9/base/psa-locale-base-en-US-7.5.4-rh9.build75051115.01.noarch.rpm error: Failed dependencies: psa-locale-base = 7.5.2 is needed by (installed) psa-7.5.2-rh9.build75050128.10 ----- end of output ----- What should I do?  ==> /tmp/psa_7.5.4_RedHat_9_build75050824.12_upgrade.log <== ===> 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... That came out of my manual yum install psa_7.5.4-whatever-package-failed-the-autoupdate
I just realized, I probably should have done yum upgrade or yum update psa, not yum install psa.... what do I do now? I don't want to uninstall it and have it mess stuff up....
Bump. Can anyone help? This is kind of urgent bafserv httpd # rpm -q psa psa-7.5.2-rh9.build75050128.10 psa-7.5.4-rh9.build75050824.12
Do you or any clients use tomcat (or jakarta)? If not, then 'rpm -e tomcat' and re-try the 7.5.4 upgrade/update. Another thing to try would be, instead of using yum to do the update/upgrade, download the Plesk 7.5.4 installer file and try that. There was at least one other post who had a failed upgrade that did this and was successful.
Apparantly I have both of the plesks installed. I dont use tomcat or jakarta, so ill delete that, but it wont let me yum anything to 7.5.4, saying its already installed. And if i install plesk 7.5.4 again, will I lose any settings or data?
Just make sure you leave the tomcat4 package, I think Plesk needs that. The reason both version show up is because the 7.5.4 did not complete properly. If yum is not doing it, then download and try the installer. You should not 'lose' data or settings (normally), but since the upgrade failed, there are no guarantees.
Separate names with a comma.