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

killing migrations

Discussion in 'Plesk Expand 2.3 Troubleshooting Issues' started by wsani, Jul 22, 2008.

  1. wsani

    wsani Silver Pleskian

    28
    40%
    Joined:
    Mar 4, 2005
    Messages:
    509
    Likes Received:
    0
    I have two migrations that have been running for over 7 days. That's not normal, so I need to know how I can remove them manually. Its obvious that they've failed but for some reason expand doesn't have a built-in logic to check for this. Go figure...
     
  2. ryoku

    ryoku Guest

    0
     
    Just stop the migration of these processes. then remove.
    Remove the copies to the destination server.
    and try start a migration again.

    A good idea to tell build of source and destination plesk, and the number of accounts you have migrated.
     
  3. wsani

    wsani Silver Pleskian

    28
    40%
    Joined:
    Mar 4, 2005
    Messages:
    509
    Likes Received:
    0
    Can't remove it using the expand interface. I have to do this manually at this point...
     
  4. gold

    gold Regular Pleskian

    25
    57%
    Joined:
    Jan 8, 2008
    Messages:
    307
    Likes Received:
    0
    What errors do you see?
     
  5. wsani

    wsani Silver Pleskian

    28
    40%
    Joined:
    Mar 4, 2005
    Messages:
    509
    Likes Received:
    0
    Code:
    <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
    <packet version="2.3.0.32">
        <abort>
            <result>
                <status>error</status>
                <errcode>2107</errcode>
                <errtext>[Transport] Empty PleskAgent answer. Invalid reply from Plesk server #2 (10.20.42.207). The message is empty. Make sure your Plesk server is up and running correctly and has all available patches and hotfixes applied and has all requred optional components (e.g. psa-backup-manager, psa-migration-manager) installed.</errtext>
                <id>44</id>
            </result>
        </abort>
    </packet>
     
  6. gold

    gold Regular Pleskian

    25
    57%
    Joined:
    Jan 8, 2008
    Messages:
    307
    Likes Received:
    0
    This migration with ID=44 must have status 'Error' now. You can delete it.
     
  7. wsani

    wsani Silver Pleskian

    28
    40%
    Joined:
    Mar 4, 2005
    Messages:
    509
    Likes Received:
    0
    I've already tried that. Believe me, I'm not a novice in troubleshooting stuff. I can assure you that your software is at fault, has been and will be for many versions to come. That said, here is what I do when I try to remove it:

    Code:
    <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
    <packet action_id="931366" version="2.3.1.8">
        <remove>
            <result>
                <status>error</status>
                <errcode>19001</errcode>
                <errtext>[Migration] Migration is still working. Can't remove migration #44 - it is working, stop it before removing</errtext>
                <id>44</id>
            </result>
        </remove>
    </packet>
    
     
  8. gold

    gold Regular Pleskian

    25
    57%
    Joined:
    Jan 8, 2008
    Messages:
    307
    Likes Received:
    0
    You can remove failed migrations by commands:

     
Loading...