Transporter and Transporter agent mismatch

S

SystemsM

Bit poster
I'm attempting to migrate a physical Ubuntu 12.04 system to a VM on Parallels Server for Mac 4.0.

The version of the Transporter Agent for Linux at:

http://download.parallels.com/serve.../parallels-transporter-agent-10311.676512.run

fails to install on the Ubuntu server.

The version of the Transporter Agent for Linux at:

http://download.parallels.com/deskt...lels-transporter-agent-18354.823166-amd64.run

installs OK, but does not communicate correctly with the version of the Transporter provided with Parallels Server for Mac 4.0. When I try, I get:

Unable to connect to Parallels Transporter Agent. Please check your
firewall settings and make sure that Parallels Transporter is not
blocked. For successful migration, the following ports should be
open: 1620, 1621, 1622, 1623.
Click to expand...

Running tcpdump on the Ubuntu server sees a request come in on port 1622 and a response being sent back, so there isn't a reachability issue. Firewalls are disabled on both systems, so that's not the problem either.

So where does one find a version of the Transporter Agent for Linux that actually works with Parallels Server for Mac 4.0?
 
Hi SystemsM

Could you generate a problem report from Parallels Server for Mac side (Help -> Report a Problem if I remember correctly) ?

Thanks
 
I generated the problem report, but...

I generated the problem report and received an email from Parallels Support re: my inquiry telling me that a solution had been provided to me and my ticket would be placed in Pending Confirmation Status for 14 days.

The only problem is that I never received any information regarding any such solution, or where to look for it.

Can you shed some light on that?
 
SystemsM, I see in log that connection was refused.

First of all make sure that Parallels Transporter Agent is up and running. It is not system service. Parallels Transporter Agent is application.

Then check that port 1622 is used by Parallels Transporter Agent: netstat -lntp

After that try to perform network migration once again.

If connection still fails try to connect from you mac to Parallels Transporter Agent using telnet: telnet <ip here> 1622

If nothing helped, post results here.

Thanks.
 
It works!

I was under the incorrect impression that the transfer agent was a service not an app. Finding it at /usr/bin/parallels-transporter-agent (there's no GUI on this server) and launching it did the trick. The fact that the server was responding at port 1622 made me think it was already running.

As it turns out, the first server I wanted to migrate uses the unsupported ext4 filesystem so I'll have to do that one by hand anyway, but the others should now work as expected.

Thanks for your help!
 
You must log in or register to reply here.
Back
Top