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

Help! Error while migrating.

Discussion in 'Plesk for Linux - 8.x and Older' started by r.basiga, Sep 8, 2005.

  1. r.basiga

    r.basiga Guest

    0
     
    I need help! How do I solve this? What could be the cause? This error occured while migrating.

    Execution of '/usr/local/psa/bin/tomcat.sh' '--set-status' 'true' '-domain' 'alsionline.com' failed with the return code 1.
    STDOUT:

    STDERR:
    warning: failed to load external entity "/var/tomcat4/conf/server.xml"
    tomcatmng: Document /var/tomcat4/conf/server.xml not parsed successfully
    warning: failed to load external entity "/var/tomcat4/conf/server.xml"
    tomcatmng: Document /var/tomcat4/conf/server.xml not parsed successfully
    Unable to turn Tomcat Service on: Unable to install Tomcat vhost: tomcatmng: Document /var/tomcat4/conf/server.xml not parsed successfully


    Failed deployment of domain alsionline.com
    Assertion failed: content.size()
     
  2. r.basiga

    r.basiga Guest

    0
     
    By the way, I use Plesk 7.5.4
     
  3. vrinteractive

    vrinteractive Guest

    0
     
    i have the same error. help plz
     
  4. r.basiga

    r.basiga Guest

    0
     
    jamesyeeoc suggested this to me:


    1. Does the domain use Tomcat on the original server? If not, try turning it off on the original server before migrating.

    2. Does the new server have all necessary Tomcat components installed? If not, then do so and try again.

    3. It is possible that the server.xml file is corrupt in some way. Can you compare them on each server to see if there are any differences?

    4. I gave up on the Migration Manager shortly after they implemented it, it was buggy, and still is buggy.

    5. You are probably still with a valid service agreement to Plesk, so you may want to open a service ticket directly to them. They are more familiar with what 'bugs' the MM has. Personally, I and my associates do it the old fashioned way and transfer domains and databases manually, that way I know it's done right, even for hundreds of domains. Takes more time, but at least we know what we're doing. I have no clue what the Plesk MM is doing...
     
Loading...