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 Fails with: 'urllib2' is not defined

Discussion in 'Plesk Expand 2.2 Troubleshooting Issues' started by v.chernev, Mar 26, 2008.

  1. v.chernev

    v.chernev Guest

    0
     
    Our current topology includes:
    1 Expand Server (v.2.2.3)
    3 Plesk Web servers (v.8.3) on CentOS5
    2 Centralized Plesk Mail Servers (v.8.3) on CentOS5
    2 Centralized Plesk DNS Servers (v.8.3) on CEntOS5
    When we try to add one more Plesk Web Server (v.8.3 on Debian ETCH) and one more Plesk Mail Server (v.8.3 on Debian ETCH) to the Expand and try to migrate clients to them, we experience the following error:

    ############################################################################################################################
    HTTP_AUTH_LOGIN: ********
    Content-type: text/xml
    HTTP_AUTH_PASSWD: ********

    <?xml version="1.0" encoding="UTF-8"?><packet version="1.4.0.0">
    <server>
    <get>
    <gen_info></gen_info>
    </get>
    </server>
    </packet>

    ========================================
    Stacktrace:
    Traceback (most recent call last):
    File "/opt/psa/admin/share/supervisor/processor.py", line 627, in __doRequest
    return self.__doRequestInternal(arc, req, answerClass)
    File "/opt/psa/admin/share/supervisor/processor.py", line 637, in __doRequestInternal
    return self.__doRealRequest(arc, req, answerClass)
    File "/opt/psa/admin/share/supervisor/processor.py", line 643, in __doRealRequest
    except urllib2.HTTPError, e:
    NameError: global name 'urllib2' is not defined
    ###########################################################################################################################

    When we try this in reverse (to migrate test clients from the newly added Plesk server to the production ones) the process completes successfully. We are also able to migrate clients among all productions Plesk servers successfully.

    In fact, before we experienced this issue the version of the Plesk servers was 8.2.1 and the version of the Expand was 2.2.2.
    After opening a ticket, the advice was to update all the SWSOFT software to the latest versions available. We upgraded all servers to the versions mentioned above and also upgraded the Migration Manager but this yielded with no positive result! The next step we did was to reinstall the new Plesk servers on CentOS5 to see if this is an OS issue but same error appears again when migration is tested. Looking forward to resolving this problem very soon! Thanks in advance!
     
  2. Bers

    Bers Basic Pleskian Staff Member

    23
    70%
    Joined:
    Jul 31, 2001
    Messages:
    73
    Likes Received:
    0
    Hello,

    please provide the exactly versions of your Plesk server, 8.3 - isn't enougth.
     
Loading...