Search results

agents are located in [/usr/local|/opt/psa]/psa/PMM, explanation how migration works can be found here: http://forum.swsoft.com/showpost.php?p=193601&postcount=2

good question - did you try to just specify it in the remote host (Source host) field, like 192.168.1.1:2222 ? I remember one time we tried that but I don't remember if it really helped or not. Anyway it is possible to do the first migration steps manually, i.e. upload needed agent to remote...

indeed, looks like some files are also stored there, and since it's name is ../tmp I think nothing important should be left there after the migration finishes. well, to be sure not to break anything, I suggest to just move those folders that are to be deleted to /tmp for example, then let the...

absolutely, as far as I know there are no migration manager files, only temporary data retreived from remote hosts. and even if you delete something important reinstallation of psa-migration-manager package will restore all needed files. probably you've ticked the checkbox in the end of...

It can happen for many reasons, hard to say why without taking a look at the logs. Deployment is basically execution of some Plesk utilities to create needed entites and then unpacking of archives, see this post for general scheme: http://forum.swsoft.com/showpost.php?p=193601&postcount=2...

just use Plesk CLI - they are described in the manuals + they have --help context help, located in /usr/local/psa/bin or /opt/psa/bin

indeed, sounds like a deep-perl problem happened because the script was run on behalf of root user, I haven't seen such error yet - did you try to apply to support yet?

> I had heard enough bad things about the migration This is usually because people under-estimate migrations - those are actually not trivial operations, and failure can happen during any step of it. I can say that almost always there are some problems during migrations, sometimes more...

migration manager uses perl scripts to determine type of remote OS (scout) and collect data (agent). as seen from the error message there was a problem during scout script execution. it can be found under the Plesk directory, let's take a look: # head /usr/local/psa/PMM/scout.pl...

there were such problems with migration manager in Plesk 8.0 and they were fixed. probably they are reoccuring now on cPanel 11, because support for it in Plesk migration manager was introduced not long ago, since Plesk 8.2.1 if I'm right. I suggest to doublecheck everything and report to...

basing on my experience Plesk for Unix to Plesk for Unix migrations are the best case, usually almost everything is properly migrated, because the structure is very similar. How it works in general: 1) migration agent collects data from source host, it collects everything which is stored...

the patch worked for me on Debian and Ubuntu, thanks heap! I have one correction to the patch - currently it checks for the sublogins. I.e. if there is user "ftpuser" and you will try to add "user" then patch will refuse to add it because user matches ftpuser as a substring and patch...

just figured out - I've forgotten to specify the domain for which I wanted to change the domain admin password so it changed it for all of them :) it can be seen from server response with domain IDs, so be sure not to miss that

it's also possible to change password for domain level user of course, here's the XML packet I used for that: <?xml version="1.0" encoding="UTF-8" standalone="no" ?> <packet version="1.3.1.0"> <domain> <set> <values> <user> <password> 123qwe </password> </user> </values> </set>...

this is rather strange... there is yet another way - you can just mount your big drive directly to your current dumps directory

hm, have you copied contents from old dump directory to the new one? as i can see from the error message it just can't find the dumps repository directories.

If I were you I would do: 1. full plesk backup 2. uninstall plesk 3. upgrade os (or just reinstall os) 4. install plesk for fc3 (better to install the same version as before, restore would go smoother) 5. restore backup ! And also it's a good idea to just manually tar/gzip old...

Well, documentation is not so clear, indeed, but at least their test script works, I've modified it a bit and then was able to run this php and change Plesk admin password from setup to setupp. I've executed it right from shell and it provided me with an answer too: <?xml version="1.0"?>...

why do you post things like that on forum? imho you should submit a support ticket or try to call them in directly.

do you mean that if it's ok do download the dump on windows box, do something with it and then upload it again back? I think you can do that if you use ascii transfer mode for ftp, so that no CR (carriage return) characters would get through.