Search results

The migrator seems to be doing the right thing with the databases that are already in the cluster on the source server: [...] debug.log:+|2017-06-27_16:23:10,132|D|ST2|core.migrator|domain1.name||Database 'asddsa_joomla_5' from mysql server at remote_db:3306 remains on the same server, content...

Plesk 12.5.30 Linux on both src and target servers. Per client migration. On both src and target servers there are 2 database servers configured: 1. localhost:3306, default 2. remote_db:3306, on a Percona XtraDB 5.7.18 cluster. Both src and target servers have admin access to remote_db. What I...

Alina, will let you know if I'll see the issue again.

Thanks Alina. For the external IP, I wouldn't have thought it would cause any issue, we have many other subscriptions with external IPs which are migrated properly. As long as the IP is external, that is, unallocated to any of the 2 nodes, source and target, shouldn't really matter, should it...

First of all, sorry if this has been answered before, or it's documented in one of the Plesk manuals and I missed it, however I'm trying to understand how the virtual hosts logs location is set up in Plesk. Just yesterday we've notices something NQR with several newly deployed vhosts. Say the...

Alina, is this what you're after? mysql> select type, displayHost, displayVal from dns_recs where dns_zone_id in (select id from dns_zone where name in ('domain.com')); +-------+---------------------------------------+------------------------------------+ | type | displayHost...

Igor, of course there are DB entries for 1.2.3.4 on the source server in the psa.dns_recs table. But, since 1.2.3.4 is an external IP, Plesk should migrate it as is, has nothing to do with the IP mapping. According to IP Mapping the IP mapping is only used to map the source IP addresses to...

Thanks Igor. I was already using the IP mapping, I always am mapping the src->target IPs. The problem in this case is, 1.2.3.4 is *external*, i.e. not configured as local IP on neither source, nor target server, therefore the record should be migrated *as is*. It's always been like this, wasn't...

Any effort to block a DDoS attack on the target server is a waste of time. You must liaise with your network provider to block the traffic upstream. You can build the most elaborate firewall on that server, the DDoS packets will still hit the network interface and the server will still use CPU...

Plesk 12.5.30 on both src and target, Panel Migrator 2.7.9. Here's another one: we've just had a client reporting DNS zone corruption, one of their previously configured A record got changed during the migration in the following fashion: 1. src server: remote.domain.com A 1.2.3.4 2. target...

Thanks for replying UFHH01. Sometimes(c) running the latest migrator version isn't an option. In our case we need some customizations to speed up the migration of large batches and ensuring mailboxes consistency for, i.e. I use "--delete" switch for rsync when migrating the emails, this avoids...

Plesk 12.5.30 on CentOS on both source and target server, using migrator 2.7.9. I see the latest is 2.8.7 so I might have to look into it later down the track. I think we have an issue which has been plaguing us recently. Some domains fail to migrate, causing the deployer process to loop for a...

I hope someone where can point me in the right direction. We are trying to pull a list of all the sub-users with permission to login to plesk for an integration project. The top level ones like Admin, reseller and client we can pull back via plesk API which is fine but we are having trouble...

Hi, Just finished a Plesk Linux -> Plesk Linux migration of a fairly large server using version 2.7.9 and I must confess I'm pretty impressed with the improvements, especially on the reliability front. And the fact that it's highly scriptable and written in Python makes my job much easier to...

I've just fixed it after strace-ing the autoinstaller execution. For some reason the broken installers had outdated files in /var/cache/parallels_installer/, after purging all that the problem went away and the remaining C7 servers are now on 12.5.30 #62.

Hi, I have this rather odd problem on several CentOS 7 servers. Sometime last year I set up a local mirror using Plesk Mirror Setup Tool v3.0 and it's been working without any issues for a while. But around 14th of December 2 of the CentOS 7 servers started to experience MU update failures...

Igor, thanks for this, I have. However, I'm still yet to find a way to update the site configuration without restarting/reloading the webserver(s). I need to be able to do bulk updates for an array of domains, but only reload apache & nginx once the job's done. Any hint will be greatly...

Hi, I need to basically create a certificate in Plesk being given the key and the bundle (CA+cert) and update the vhost's SSL configuration accordingly. At the moment I'm doing something like this: /usr/local/psa/bin/certificate --create "www.${MYSITE} cert" \ -domain ${MYSITE} \...

Hi Alina, thanks for replying. We can't unfortunately provide access to any of the servers. What I've done in the meantime was to retest the migration for some of the failed subscriptions from the panel and it worked every time, which makes me think the 2 methods aren't functionally the same...

CentOS 5->, Plesk 12.5.30 #59, Panel migrator 2.4.9 When I'm running the migration from cli, Plesk fails to migrate the subscriptions that have addons attached because the limits enforced by the service plan on the target server are exhausted. When I look in the destination I can see the...