Original Publishing Date: 2020-01-22 Symptoms It is not possible to retrieve Plesk packages from the repository at autoinstaller.plesk.com. The following error is displayed: Getting new version of Parallels Installer... File downloading parallels_installer_CloudLinux_5.7.1_x86_64.md5sum : ERROR: The required version '3.11.0' was not found on the server. This could happen because of configuration error at the download site. Failed to download the package http://autoinstall.plesk.com/Paralle...x86_64.md5sum: The requested URL returned error: 404 Not all packages were installed. OR http://autoinstall.plesk.com/PHP_5.3.29/dist-rpm-CentOS-7-x86_64/packages/plesk-php53-ioncube-loader-4.7.2-centos7.15020319.x86_64.rpm: [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=PHP_5_3_29-dist clean metadata Trying other mirror. centos7.15020319.x86_64: [Errno 256] No more mirrors to try.', u'plesk-php53-ioncube-loader-4.7.2-centos7.15020319.x86_64: [Errno 256] No more mirrors to try.', u'plesk-php52-xdebug-2.2.3- ERROR: Failed to run the Yum utility. The Yum utility failed to install the required packages. It is also not possible to download the file using wget: wget http://autoinstall.plesk.com/plesk.inf3 Resolving autoinstall.plesk.com... 93.184.221.133 Connecting to autoinstall.plesk.com|93.184.221.133|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 222396 (217K) [text/xml] Saving to: `plesk.inf3.9' 3% [====> ] 6,960 --.-K/s in 0.001s 2013-09-01 00:21:21 (6.56 MB/s) - Read error at byte 6960/222396 (Connection reset by peer). Retrying. Cause Odin uses a content delivery network (CDN) to distribute Plesk packages. This technology uses several cache servers which are distributed across different parts of the internet. All of the servers share a common domain name, autoinstall.plesk.com, which resolves to different IP addresses depending on the network segment that a request comes from. Sometimes, a server becomes out of sync with the main replica and files go missing. Network issues (TCP window scaling). Resolution Use the main replica of the Plesk repository until your local CDN server synchronizes with it. To do this, configure a static resolution rule in the file /etc/hosts: 68.232.34.73 autoinstall.plesk.com Alternatively: 93.184.221.133 autoinstall.plesk.com If this does not help, disable TCP window scaling: echo 0 > /proc/sys/net/ipv4/tcp_window_scaling See the following link for more details on TCP window scaling http://lwn.net/Articles/92727/ If the issue still persists, open the /etc/hosts file and replace: 68.232.34.73 autoinstall.plesk.com With: 199.115.104.31 pleskwin.download.swsoft.com download1.parallels.com autoinstall.plesk.com origin.autoinstall.plesk.com Internal content

Original Publishing Date: 2020-01-22 Symptoms After upgrade to OA 7.x switch to Billing does not work. Cause OA was successively upgraded from 5.x version to 6.0 and then to 7.0. In OA 5.x Billing used the port 443 to access its panel. Starting OA 6.0, the port 8443 was introduced, however, environments, upgraded from 5.5 was still using the port 443 - please see more details in the OA 6.0 Firewall Guide. Since OA 7.0, UI nodes require the port 8443 to be listened by Apache on the Billing application server. Resolution Go to the Billing application server Edit the file /etc/httpd/conf.d/ssl.conf.inc and copy the whole configuration of the virtual host Add the copied configuration to the end of the file /etc/httpd/conf.d/ssl.conf.inc replacing the port 443 with 8443 and save the file Restart Apache: # systemctl restart httpd Internal content Link on internal Article

Original Publishing Date: 2020-01-22 Symptoms The following task fails: Task name Install set of VZ templates to VPS vps Task description Install of following VZ templates into VPS: .pp12-msmtp.centos-6-x86_64/, .pp12-bind.centos-6-x86_64/, .pp12-mailman.centos-6-x86_64/, .pp12-php5.centos-6-x86_64/, .pp12-webhosting-addons.centos-6-x86_64/, .pp12.centos-6-x86_64/, .pp12-postfix.centos-6-x86_64/, .pp12-courier-imap.centos-6-x86_64/, .pp12-migration.centos-6-x86_64/, .pp12-panel-addons.centos-6-x86_64/, .pp12-spamassassin.centos-6-x86_64/, .pp12-watchdog.centos-6-x86_64/, .pp12-webmail.centos-6-x86_64/ Last execution output Internal error: 3501 : Can not install packages: ' vzpkg install -q 10205 .pp12-bind .pp12 .pp12-courier-imap .pp12-mailman .pp12-migration .pp12-msmtp .pp12-panel-addons .pp12-php5 .pp12-postfix .pp12-spamassassin .pp12-watchdog .pp12-webhosting-addons .pp12-webmail' exec failed - Error: plesk-mail-mc-driver conflicts with postfix Error: plesk-mail-mc-driver conflicts with psa-courier-imap Error: plesk-mail-mc-driver conflicts with plesk-courier-imap-driver Error: plesk-mail-pc-driver conflicts with sw-msmtp Error: plesk-mail-mc-driver conflicts with psa-courier-authlib Error: plesk-mail-mc-driver conflicts with psa-mail-driver-common Error: /usr/share/vzyum/bin/yum failed, exitcode=1 Cause Provider has configured service template to install both pp12-postfix and pp12-msmtp application templates automatically during subscription creation. These 2 application templates are mutually exclusive and cannot be used at same time. Resolution Open service template > Application templates and make sure only one of these 2 application templates is marked as "Install automatically" For already existing failed tasks - cancel task and fix the templates via following way: From POA PCP go to "Cloud Infrastructure > VPSs" and select the needed VPS. Click on the "Application templates" tab, then click on the needed template in "Installation Failed" state. In the opened tab, click on the template name again, then switch to the "VPSs" tab, select the needed VPS and click "Uninstall". This should be done for every template in "Installation Failed" state. Internal content

Original Publishing Date: 2020-01-22 Question We have an upcoming requirement to relocate the server "ns.provider.com". We intend on moving it to an entirely different network, where it will have a new backnet and frontnet IP address and will essentially be a new server. Can you please provide a rough guideline as to how we could do this? Answer Basic procedure is the following: Add new nameserver in another location Appropriate documentation page can be used as a reference. "Deploying Linux-based DNS Servers" chapter Use attached script to synchronize all DNS zones to a new server Decomission old server, make sure that all appropriate tasks completed successfully This procedure will allow to keep server redudancy. But, if you need to re-use the same server and there so no chance to add a new one (step 1), then the procedure will be changed: Decomission old server, make sure that all appropriate tasks completed successfully Add the same server in a new location (with new network parameters) Use attached script to synchronize all DNS zones to a new server Please be advised that there are several possible aftermathes: If you have 2 nameservers in OSA configuration and the second one shall fail during relocation hosting infrastructure shall stay without DNS service Some domain registrars have a requirement to have at least 2 nameserver to register a domain. If you decomission 1 server and only 1 left - domain registration will be impossible In case of significant nuber of domains (several thousands) the synchronization procedure can be extremely long: divide domains in portions to avoid system overload Several additional recommendations By default when you add a new DNS server in OSA configuration only newly created domains shall be propagated on a new server. If you need to propagate old domains too - please use 'pem.syncNameServers' API method to sync. Another way is to do it manually - choose a domain in "Domains" tab, switch zone to external and then back to internal hosting. In case of significant number of domains it is strongly recommended to divide list of domains in several smaller portions. Script below can be used as a reference. Script #!/bin/bash psql -Uplesk -h`hostname` plesk -c "SELECT d.name FROM domains d JOIN accounts a ON (a.account_id = d.owner_id) JOIN dns_zones z ON (z.zone_id = d.zone_id) JOIN domains dp ON (dp.zone_id = z.zone_id AND dp.dns_path = z.name AND dp.deleted != 'y') WHERE ((a.path >= (SELECT ap.path||'x' FROM accounts ap WHERE ap.account_id = 1) AND a.path < (SELECT ap.path||'y' FROM accounts ap WHERE ap.account_id = 1)) OR a.account_id = 1) AND d.deleted != 'y' AND (d.is_locked = 0 ) ORDER BY d.domain_id" > domains.txt sed '1,2 d;' domains.txt > domains2.txt sed -e 's/^.\{1\}//' domains2.txt > domains.txt sed 'N;$!P;$!D;$d' domains.txt > domains_final.txt rm -f domains2.txt rm -f domains.txt while read i do echo "< /root/domains_final.txt Internal content

Original Publishing Date: 2020-01-22 Additional information This article provides a list of supported BackupAgent versions in Service Automation. Last Changed Product Version OA Versions Comment 18-Jul-2011 BackupAgent Management Console, Version 3.10.3.1 and higher in V3 5.5 and later 24-Aug-2011 BackupAgent Management Console, Version 4.0.1 and higher in V4 5.5 and later See also: Supported Third-Party Products in Odin Service Automation Internal content

Original Publishing Date: 2020-01-22 Additional information This article provides a list of supported Microsoft Office 365 versions in Service Automation. Last Changed Product Version OA version Comment 18-Jul-2011 Microsoft Office 365 5.5 and later 18-Jul-2011 Microsoft Office 365 with trial subscriptions support 5.5 and later See also: Supported Third-Party Products in Odin Service Automation Internal content

Original Publishing Date: 2020-01-22 Symptoms Task related to APS-application WordPress fails in OA Task Manager with errors similar to following: PHP Notice: Undefined index: REQUEST_METHOD in /usr/local/pem/vhosts/172325/webspace/siteapps/WordPress-5621/htdocs/wp-content/plugins/ip-geo-block/classes/class-ip-geo-block.php on line 108 Cause Option WP_DEBUG is enabled in wp-config.php: [root@linweb01 ~]# egrep 'define.*(WP_DEBUG)' /usr/local/pem/vhosts/172325/webspace/siteapps/WordPress-5621/htdocs/wp-config.php define('WP_DEBUG', true); In this case WordPress generates notices that are visible in output of APS-scripts. It causes failure of OA tasks. Note: WordPress overrides value of setting error_reporting in php.ini Resolution Change value of setting WP_DEBUG from true to false in wp-config.php Restart failed task Internal content

Original Publishing Date: 2020-01-22 Additional information The article provides a list of supported VMware Zimbra versions in Service Automation. Last Changed Product Version OA Versions Comment 15-Aug-2013 Zimbra Network Edition 7.0.3. or later 5.5 and later Service Automation is integrated with Zimbra Network Edition because only this edition supports domain administrators with per domain permissions management. See also: Supported Third-Party Products in Odin Service Automation Internal content

Original Publishing Date: 2020-01-22 Additional information This article provides a list of MS SCVMMversions supported in Service Automation. Last Changed Product Version OA Versions Comment 21-Jan-2011 2008 R2 5.5 and later See also: Supported Third-Party Products in Odin Service Automation Internal content

Original Publishing Date: 2020-01-22 Information This article provides a list of supported qmail versions in Service Automation. Last Changed Product Version OA versions Comment 18-Aug-2010 1.03 5.5 and later qmail is heavily modified by Odin The following qmail patches are applied: Last Changed Patch Name OA versions Comment 12-Oct-2010 Any-To-Cname 5.5 and later 12-Oct-2010 qmail SMTP Plugin 5.5 and later 12-Oct-2010 Big Todo 5.5 and later 12-Oct-2010 STARTTLS 5.5 and later See also: Supported Third-Party Products in Odin Service Automation Internal content