Buggy Plesk 8.3 migration manager (migration tool)

As SwSoft, now known as Parallels, introduced an end of life policy for supporting old OSes I’ve had to migrate a number of Fedora Core machines to Ubuntu 6.06 LTS. The best way of doing this is via the migration manager from the new Plesk node. However, the migration manager will copy everything over, but, due to a bug in their code it doesn’t copy over auto_increment options in the databases. This obviously causes major issues with databases that use auto_increment that are migrated over.

The option about Mysql compatibility with the older versions was defined in Plesk Migration manager, the file is /opt/psa/PMM/agents/shared/Db/MysqlShellBackend.pm.
I have commented out the values:
root at hostname:~# cat /opt/psa/PMM/agents/shared/Db/MysqlShellBackend.pm | grep compatible
# $self->{not_compatible_mysql_323} = $params{not_compatible_mysql_323} if defined $params{not_compatible_mysql_323};
# $dumpoptions .= ” –compatible=mysql323 ” if !$self->{not_compatible_mysql_323} && $self->_mysql41OrNewer();

Comment out those two lines and Plesk database migrations should work alright.

NOTE: This should be fixed in newer Plesk 8.3 releases

a

Plesk 8.3 on Ubuntu main IP change

I needed to change a machine primary IP from one network to another… Not knowing that Plesk 8.3 has a specific way of changing IPs on a machine I manually updated the /etc/network/interfaces file with the systems new IP address details. Infact, probably best that I changed this file manually as Plesk doesn’t appear to have any knowledge of default gateways, so, if I followed the article below I probably would have a machine with an IP address in a different network to the default gateway:

http://kb.swsoft.com/en/943

So probably best to update the IP address manually and follow below:

Once I change the machine into the new network with it’s new IP & default gateway I thought I’d be able to login to Plesk and click on Server->IP Addresses and just refresh for it to pickup the new IP. Instead, when I clicked repair it added the new IP address and left the old one as well… it added the old one as an alias on the machine. I was not able to select the IP in the IP address management area so I couldn’t delete it.

The follow article made it possible for me to delete the IP address from within the CP:

http://kb.swsoft.com/en/237