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

Plesk 9.0.1 => 9.2.1 Debian etch x64 Update fails

Discussion in 'Plesk 9.x for Linux Issues, Fixes, How-To' started by fuck nuts, Apr 28, 2009.

  1. fuck nuts

    fuck nuts Guest

    0
     
    Code:
    Setting up sw-cp-server (1.0-5.200902130602.debian40) ...
    Starting SWsoft control panels server... stale pidfile. failed
    dpkg: error processing sw-cp-server (--configure):
     subprocess post-installation script returned error exit status 1
    dpkg: dependency problems prevent configuration of plesk-base:
     plesk-base depends on sw-cp-server (>= 1.0-5); however:
      Package sw-cp-server is not configured yet.
    dpkg: error processing plesk-base (--configure):
     dependency problems - leaving unconfigured
    dpkg: dependency problems prevent configuration of psa-mail-driver-common:
     psa-mail-driver-common depends on plesk-base (>= 9.2.1); however:
      Package plesk-base is not configured yet.
    dpkg: error processing psa-mail-driver-common (--configure):
     dependency problems - leaving unconfigured
    Errors were encountered while processing:
     sw-cp-server
     plesk-base
     psa-mail-driver-common
    E: Sub-process /usr/bin/dpkg returned an error code (1)
    
    ideas anyone?
     
  2. David Harris

    David Harris Basic Pleskian

    20
    40%
    Joined:
    Apr 22, 2009
    Messages:
    42
    Likes Received:
    0
    Location:
    Pyrenees, France.
    That's not a nice username :|

    I have major problems at the moment. All my sites have gone down after the update which went very smooth?

    Seems to be dns stuff.
     
  3. fuck nuts

    fuck nuts Guest

    0
     
    about the problem i've mentioned above...

    somehow sw-cp-server was still running occupying port 10001 which made all the installation fail. if you experience the same issue like i had.... try

    # lsof | grep 10001
    and then
    kill -9 <pid>

    and try again to install using parallels autoinstaller.
     
Loading...