1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Upgrade from 8.1.1 to 8.2.0 - Incomplete upgrade. Admin site unavailable

Discussion in 'Plesk for Linux - 8.x and Older' started by h4inf, Sep 17, 2007.

  1. h4inf

    h4inf Guest

    0
     
    Upgrade from 8.1.1 to 8.2.0 - Incomplete upgrade. Admin site unavailable. SOLVED

    Hi,

    I was just doing updates to my plesk installation. First of all i installed all of the remaining 8.1.1 updates to bring that up to scratch... I recieved 2 update success emails after I set that going. Everything continued to work perfectly, the admin panel and my websites and email.

    I returned to the Server Screen, went to update and ticked most of the boxes under the 8.2.0 upgrades, then clicked install and confirmed. A few minutes later, I recieved an email with the subject "Plesk autoupdate success report" ... the email ended with "Exit with OK status".

    The problem now is that my admin page does not display at all. If i type in the URL to get to my admin page, my browser reports "Connected to https://plesk.mydomain.com:8443..." and just hangs there. It does not timeout or display anything.

    My mail is still working, as are my websites, however I am not game enough to reboot the server at this stage as I fear things will become unavailable.

    Looking through the autoupdate report I spotted the following potential issues. If anyone could explain them, I'd be most grateful. I was unable to find anything in the KB regarding these.

    Code:
    Warning: packages conflict by files detected: package [b]psa8-vz-30domain-license-ppl-239746.0000-0.i386[/b]
      conflict with package [b]psa8-vz-30domain-license-239711.0000-0.i386[/b]
      both have file /usr/local/psa/tmp/psa.key.custom with different md5 sum.
    Warning: packages conflict by files detected: [b]package sitebuilder_remote-admin-3.0.2-all.build06112310.noarch[/b]
      conflict with package [b]sitebuilder-4.0.0-all.build07062700.noarch[/b]
      both have file /usr/local/sitebuilder/htdocs/ServiceFacade/AccountWebService.asmx with different md5 sum.
    Warning: packages conflict by files detected: package [b]psa8-vz-30domain-license-239711.0000-0.i386[/b]
      conflict with package [b]psa8-vz-30domain-license-ppl-239746.0000-0.i386[/b]
      both have file /usr/local/psa/tmp/psa.key.custom with different md5 sum.
    Check package set before installation
    repository: download selected packages
    Download file opt/updater/psa-autoinstaller-3.2.0-build32070705.20.i586.rpm: 11%..20%..30%..40%..50%..60%..71%..80%..90%..100% done.
    Start packages installation
    Warning: packages conflict by files detected: package psa8-vz-30domain-license-ppl-239746.0000-0.i386
      conflict with package psa8-vz-30domain-license-239711.0000-0.i386
      both have file /usr/local/psa/tmp/psa.key.custom with different md5 sum.
    Warning: packages conflict by files detected: package psa8-vz-30domain-license-239711.0000-0.i386
      conflict with package psa8-vz-30domain-license-ppl-239746.0000-0.i386
      both have file /usr/local/psa/tmp/psa.key.custom with different md5 sum.
    prepareInstallStep: resolve results for package(s):
     (s) system_installed_bash-3.0-31.i386.rpm
     (s) system_installed_glibc-2.3.6-3.i686.rpm
     (s) system_installed_openssl-0.9.7f-7.10.i686.rpm
     (s) system_installed_rpm-libs-4.4.1-23.i386.rpm
     (s) system_installed_zlib-1.2.2.2-5.fc4.i386.rpm
    Install package psa-autoinstaller-3.2.0-build32070705.20.i586
    Installation done.
    Exit with OK status
    
    Now usually I get 2 emails when I do updates... This time I only got one... so can anyone tell what has gone wrong here?

    Any ideas would be much appreciated!!!

    Thanks in advance,

    Paul.
     
  2. h4inf

    h4inf Guest

    0
     
    Problem Solved

    Problem Solved.

    Logging into the terminal, I just ran the autoinstaller script from psa/bin and that took all night, but has left me in a good position :)

    Hooray everything works!
     
Loading...