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

Migration manager error

Discussion in 'Plesk for Linux - 8.x and Older' started by tfanabe, Dec 23, 2006.

  1. tfanabe

    tfanabe Guest

    0
     
    I use plesk 8.1.0 with opensuse 10.1.
    When I try to use the MM, I have these error: I have try to delete the .xxxrc file from root home directory but don't change anything...


    Traceback (most recent call last):
    File "/usr/local/psa/admin/share/supervisor/processor.py", line 110, in doActivityRunner
    newState = self.doActivity()
    File "/usr/local/psa/admin/share/supervisor/processor.py", line 217, in doActivity
    cmd.spawn()
    File "/usr/local/psa/admin/lib/python/subproc.py", line 237, in spawn
    proc.run()
    File "/usr/local/psa/admin/lib/python/subproc.py", line 193, in run
    BaseSubprocess.run(self)
    File "/usr/local/psa/admin/lib/python/subproc.py", line 177, in run
    self.wait()
    File "/usr/local/psa/admin/lib/python/subproc.py", line 197, in wait
    BaseSubprocess.wait(self)
    File "/usr/local/psa/admin/lib/python/subproc.py", line 187, in wait
    raise NonzeroExitException(self, os.WEXITSTATUS(status))
    NonzeroExitException: was finished with exit code 1
     
  2. JohnB@

    JohnB@ Guest

    0
     
    We have the exact same problem and exact same error message.
    Did you find out how to solve this?

    John
     
  3. TarkanVeKurdu

    TarkanVeKurdu Guest

    0
     
    We have the same problem here. Any solution to this ?
     
  4. nstriedinger

    nstriedinger Guest

    0
     
    Same problem! Python

    Migrating from 7.5.4 to 8.1.0

    rhel3 to centOS




    Traceback (most recent call last):
    File "/usr/local/psa/admin/share/supervisor/processor.py", line 78, in getStatus
    return (None, self.realGetStatus())
    File "/usr/local/psa/admin/share/supervisor/processor.py", line 510, in realGetStatus
    return getRunningAgentState(self.session)
    File "/usr/local/psa/admin/share/supervisor/processor.py", line 466, in getRunningAgentState
    d = minidom.parseString(content)
    File "/usr/lib/python2.3/xml/dom/minidom.py", line 1929, in parseString
    return expatbuilder.parseString(string)
    File "/usr/lib/python2.3/xml/dom/expatbuilder.py", line 940, in parseString
    return builder.parseString(string)
    File "/usr/lib/python2.3/xml/dom/expatbuilder.py", line 223, in parseString
    parser.Parse(string, True)
    ExpatError: syntax error: line 1, column 0:(
     
  5. TarkanVeKurdu

    TarkanVeKurdu Guest

    0
     
    Hello,

    This might help your situation we have updated our plesk 8.1.0 using auto updater and everything works ok now.

    Regards
     
  6. nstriedinger

    nstriedinger Guest

    0
     
  7. nstriedinger

    nstriedinger Guest

    0
     
    Migration is taking forever

    So I guess taking that code out of .bashrc worked...but...

    It is a 9G site, and its been running for 40:25:19. Should I cancel it?

    Dumping progress
    Done:
    2 domain(s) out of 2
    1 client(s) out of 1

    Remaining:
    0 domain(s)
    0 client(s)
     
  8. nstriedinger

    nstriedinger Guest

    0
     
    Does anyone know how I can check the file size of the migration (maybe a compressed file)? I know the site is 9gig, so if I can monitor a few files, I can see if things are close.

    I can see that I've got some files changing in /tmp/usr/local/psa/PMM/var/

    2007-02-14-14.19.34.579176
    2007-02-14-14.19.34.579176/supervisor.log
    2007-02-14-14.19.34.579176/dumping-status.xml
    2007-02-14-14.19.34.579176/migration.log
     
  9. nstriedinger

    nstriedinger Guest

    0
     
    I could have done this faster manually...I'll wait a little longer...
     
  10. nstriedinger

    nstriedinger Guest

    0
     
    ok, well the migration got hung up b/c I didn't have enough space on the old 7.5 Plesk box. Thanks for all the help.

    You need at least double what the site is.
     
  11. thewolf

    thewolf Regular Pleskian

    25
    57%
    Joined:
    Mar 11, 2004
    Messages:
    231
    Likes Received:
    0
    Hi,
    What directory do you need the free space in?

    My old server has little free space left and I want to be sure that the migration to the new server will not fail.

    Thanks.
     
  12. nstriedinger

    nstriedinger Guest

    0
     
    If you have "managed" hosting with a limit of 10G and your site takes up 9G, you'll need at least 18G to migrate. It seems that Plesk almost makes a duplicate of your current site, THEN migrates the files.
     
  13. HoneyMonster

    HoneyMonster Guest

    0
     
    My Solution

    Hello,

    I ran into this on two seperate, entirely differently configured servers. After wasting lots of time trying to find the problem this is how we found the solution:

    -We made sure there was nothing silly in .bashrc - no luck

    -We tried upgrading both the source and destination server to the most update version of Plesk 8.1 - no luck.

    -We tried doing a full Plesk dump via command line and then restoring it to the new server - no luck. Exactly the same error message as the migration, however it threw this error in too:
    AWSTATS_DOC_D not defined

    So, We went and added the line AWSTATS_DOC_D /var/www/html/awstats to /etc/psa/psa.conf and now the migration works fine.

    It may not be awstats thats causing the problems on your servers but at least by tring a Plesk dump/restore you can get some more useful error reporting that points you in the right direction. :)
     
Loading...