Original Publishing Date: 2020-01-22 Symptoms Task Install DB slave of OSS DB on node #xx failed with error like: "Error: Internal error: /usr/bin/python /usr/bin/python sysdb_master_ctrl.py deploy 30 1 ******** uinode 365 /usr/local/pem/tmp/client_ctrl.py /usr/local/pem/etc/slave_db.conf failed with code 1 saying: STDOUT: '2018-02-27 06:56:51.333 [DEBUG] read agent config from /usr/local/pem/etc/pleskd.props" ... /bin/sh /bin/sh -c rpm -ql postgresql90-odbc | grep /psqlodbc\.so$ failed with code 1 saying: STDOUT: '' STDERR '' ... ERROR: role "oa_192_168_1_71" cannot be dropped because some objects depend on it DETAIL: 1 object in database oss Traceback (most recent call last): File "sysdb_master_ctrl.py", line 14, in deployRv = uDBAccessAPI.deployPgSlave(slaveHostID, isBillingMaster, masterRoorPwd, readOnlyUserType, additionalIPs, slaveScriptCb, tuple(sys.argv[8:])) File "/usr/lib/python2.7/site-packages/poaupdater/uDBAccessAPI.py", line 313, in deployPgSlave runOnMaster(""" su - postgres -c "psql --port=%d -c \\"DROP ROLE IF EXISTS %s\\"" """ % (masterPort, roUserName,)) ... Cause pa-central-repo repository is not configured on DB replication host. Resolution Login to Database replication host and Configure pa-central-repo on the replica host. For example, you can copy /etc/yum.repos.d/pa-central.repo from CloudBlue Commerce Core node Enable repository with command yum --enablerepo=pa-central-repo clean metadata; Rerun failed task from Task Manager. Internal content

Original Publishing Date: 2020-01-22 This hotfix is superseded by hotfix OA 7.3.0 HOTFIX 133324 PLATFORM v2 Internal content

Original Publishing Date: 2020-01-22 Overview To run some server platforms and services on Windows Shared Hosting Module at POA 5.4, there was a dependency on Microsoft Hosted Messaging and Collaboration (HMC or MPS) 4.5. HMC was built to run on top of Windows Server 2003 and SQL Server 2000 or 2005. Neither HMC nor SQL Server 2000/2005 are supported by Microsoft anymore. To solve this issue, starting on POA 5.5, this dependency was removed and all the latest Windows-based server platforms and services are running on a new provisioning platform, called Parallels Windows Provisioning Engine (WPE). WPE provides to users the same functionalities HMC provided, but instead it runs on top of Windows Server 2008 and SQL Server 2008. When upgrading to POA 5.5, in case there are old services running on HMC, they will still work normally. However, it will not be possible to upgrade any of these services further than 5.5 on top of HMC. All of them will have to be deployed on top of WPE instead. New PA installations will only be able to deploy WPE. Services supported by WPE The table below shows which services are supported by WPE in POA 5.4 and POA 5.5. Note that Legacy services are not supported by WPE on any POA version. Service POA 5.4 POA 5.5 Not Supported IIS 7.5 - Yes - IIS 6/7 - - Yes SharePoint 2/3 - - Yes SharePoint 2010 Yes Yes - MS SQL 2000/2005 - - Yes MS SQL 2008 - Yes - MS DNS Yes Yes - Hosted Exchange 2003/2007 - - Yes Hosted Exchange 2010 SP2 Yes Yes - Hosted Exchange 2013 - Yes - Good Mobile Messaging - - Yes BlackBerry Enterprise Server 5 Yes Yes - Hosted Dynamics CRM 4 - - Yes Hosted OCS 2007 R2 - - Yes Windows Streaming Media - - Yes ColdFusion 6/7/8 - - Yes Branding and UI Servers Yes Yes - WinFileManager - Yes - AWStats Web Statistics - Yes - SQL Server Web Data Administrator - Yes - myLittleAdmin for MS SQL Server - Yes - Domain Parking on MS IIS - Yes - SSL Proxy on IIS - Yes - Internal content

Original Publishing Date: 2020-01-22 Symptoms Task Upgrading resources of application 'Office 365' fails: Internal error: APSC: Upgrade to ver. 17.2.1-4 : resource 9dd1d9bc-...-069070fbf049 of type 'office365app' (http://www.parallels.com/Office365/Office365app/1.22) for APS application 'Office 365-17.2.1-4' : API for service with base domain 'example.com' is not supported.. Cause Application instance misconfiguration. User specified as Administrator's login for connecting to Microsoft Online should have UPN based on *.onmicrosoft.com domain. Resolution Create proper administrator according to the Creating Administrative User documentation article; Specify its credential info in the Office 365 application instance settings (Administrator's login for connecting to Microsoft Online and Administrator's password for connecting to Microsoft Online fields); Restart the IIS service on the Office 365 Endpoint host; Restart failed upgrade task. Internal content

Original Publishing Date: 2020-01-22 Symptoms Provisioning of WAP subscriptions fails with the error: Task ID 2557134 Queue name aps_application_instance272 subscription_id1000782 Task name Provisioning "Context" for APS application Windows Azure Pack APS Package Task description Provisioning resource 6f2a8027-abaf-4c88-bafb-70dcf25b1cdf of type "contexts" (http://sp.parallels.com/infrastructure/cloudos/context/1.0) for APS application Windows Azure Pack APS Package Belongs to groups provide subscription 1000782 Subscription ID 1000782 Queue status Failed Start not earlier than Jun-24-2014 15:15 Method name taskExecuteWorkflow on SCREF:SaaSManagerTasks:0 Last execution output Internal error: SDK::Platform::blob Plesk::SaaS::SaaSManagerTasks_impl::taskExecuteWorkflow(const SDK::Platform::Properties&) : [APSC] [AZURE] {"Code":"ErrorFromUnderlyingNotificationSubscribers","Message":"One or more errors occurred while contacting the underlying notification subscribers. The operation may be partially completed.","Details":[]}. Nothing specific is shown in /var/log/WAP/errors.log and /var/log/WAP/wap.log Microsoft-WindowsAzurePack-MgmtSvc-Usage/Operational section of Event Viewer on WAP node shows many errors of the following type: Log Name: Microsoft-WindowsAzurePack-MgmtSvc-Usage/Operational Source: Microsoft-WindowsAzurePack-MgmtSvc-Usage Date: 6/25/2014 7:32:31 AM Event ID: 12 Task Category: (65522) Level: Error Keywords: None User: IIS APPPOOL\MgmtSvc-UsageCollector Computer: HV-WAPINT01.hvinfra.local Description: Error: System.Data.SqlClient.SqlException (0x80131904): Error: 9002, Severity: 17, State: 2, Procedure GetSchedulerConfiguration, Line 15, Message: The transaction log for database 'Microsoft.MgmtSvc.Usage' is full due to 'LOG_BACKUP'. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryHasMoreRows(Boolean& moreRows) at System.Data.SqlClient.SqlDataReader.TryReadInternal(Boolean setTimeout, Boolean& more) at System.Data.SqlClient.SqlDataReader.TryNextResult(Boolean& more) at System.Data.SqlClient.SqlDataReader.NextResult() at Microsoft.WindowsAzure.Server.Usage.Storage.ConfigurationStorageClient.<>c__DisplayClass6.b__1(SqlDataReader reader) at Microsoft.WindowsAzure.Server.Common.SqlProcExecutor.d__6`1.MoveNext() ..... Cause Issues on the side of WAP MSSQL database Resolution Please check the transaction log settings of MSSQL database Microsoft.MgmtSvc.Usage. The following Microsoft article could be useful: http://support.microsoft.com/kb/317375. If it does not help, please contact Microsoft support to get further assistance. Internal content

Original Publishing Date: 2020-01-22 Symptoms APS Booster was configured and all tasks were completed successfully. UI hosts were connected to Database Replica Nodes be steps from Documentation. Following error appears in /var/log/pa/pui/pui.log on UI hosts: 00:00:00.001 [EJB default - 7] DEBUG c.o.a.s.b.e.ReplicationAndBoosterStatusBean - replica status check 00:00:00.005 [EJB default - 7] DEBUG c.o.a.s.b.ejb.WebServerStatusChecker - replica status: replay delay = 168909 ms, WAL diff = 0 bytes 00:00:00.005 [EJB default - 7] DEBUG c.o.a.s.b.ejb.WebServerStatusChecker - replica is out of sync - 168909 ms since last WAL replay 00:00:00.005 [EJB default - 7] DEBUG c.o.a.s.b.ejb.WebServerStatusChecker - booster is inactive, replica is out of sync APS REST API requests with OAuth authentication fail with: Authorization failed. Invalid authorization signature. Please check application settings. Cause APS Booster is disabled PostgreSQL replication is not working. Database replication does not work due difference in time between the UI host and the Database Replica node. Resolution Check if the APS booster is Enabled or not. If not, enable it. Make sure that APS Booster is enabled on the UI node: # grep apsbooster /usr/local/pem/wildfly-21.0.1.Final/standalone/configuration/standalone_xml_history/standalone-full-ha.boot.xml and in runtime: # sh /usr/local/pem/wildfly-21.0.1.Final/bin/jboss-cli.sh -c --commands="/system-property=com.parallels.pui.apsbooster.enabled:read-resource" { "outcome" => "success", "result" => {"value" => "true"} } Check if the PostgreSQL replica is working or not. To check if PostgreSQL replication is working, run this oss database query:                                                       oss=#  select * from pg_stat_replication;  pid  | usesysid |      usename       | application_name | client_addr | client_hostname | client_port |         backend_start     | backend_xmin |   state   |  sent_lsn   |  write_lsn  |  flush_lsn  | replay_lsn  |    write_lag    |    flush_lag    |   repl ay_lag    | sync_priority | sync_state ------+----------+--------------------+------------------+-------------+-----------------+-------------+--------------------------- ----+--------------+-----------+-------------+-------------+-------------+-------------+-----------------+-----------------+------- ----------+---------------+------------  1295 |    31716 | slave_oa_10_1_10_7 | walreceiver      | 10.1.10.7   |                 |       33128 | 2023-01-27 19:43:16.991738 +09 |     48984320 | streaming | 69/B35994B8 | 69/B35994B8 | 69/B35994B8 | 69/B35994B8 | 00:00:00.001291 | 00:00:00.004878 | 00:00: 00.005063 |             0 | async (1 row) On oss replica, use this query:                                                                                                                                        oss=# select * from pg_stat_wal_receiver;   pid  |  status   | receive_start_lsn | receive_start_tli | received_lsn | received_tli |      last_msg_send_time       |     last _msg_receipt_time     | latest_end_lsn |        latest_end_time        | slot_name | sender_host | sender_port |                                                                                conninfo -------+-----------+-------------------+-------------------+--------------+--------------+-------------------------------+--------- ----------------------+----------------+-------------------------------+-----------+-------------+-------------+------------------- ----------------------------------------------------------------------------------------------------------------------------------- -------------------------------------------------------  32592 | streaming | 69/82000000       |                 1 | 69/B35AE770  |            1 | 2023-01-30 10:09:45.012388+09 | 2023-01- 30 10:09:45.012485+09 | 69/B35AE770    | 2023-01-30 10:09:45.012388+09 |           | 10.1.10.6   |        5432 | user=slave_oa_10_1 _10_7 password=******** dbname=replication host=10.1.10.6 port=5432 fallback_application_name=walreceiver sslmode=verify-ca sslcomp ression=1 krbsrvname=postgres target_session_attrs=any (1 row)             If it is not working, make sure that oss and oss replica has the same version of PostgreSQL. Check if it has more than a one-minute time difference. Synchronize time between UI host and replication node. More than one-minute time difference causes the issue: maxReplayDelay = Duration.ofMinutes(1); NOTE: In case UI cluster deployed in Azure, follow this article: How to change timezone on Azure UI cluster Make sure that /etc/localtime file is linked to a proper timezone. If not, correct this like in the example below: localtime -> /usr/share/zoneinfo/Etc/GMT+8 As an alternative, configure time synchronization services like Chrony or NTPD on the affected hosts. Internal content Link on internal Article

Original Publishing Date: 2020-01-22 This hotfix is superseded by hotfix OA 7.0.1 HOTFIX 130584 UI CORE APP v6 Internal content

Original Publishing Date: 2020-01-22 Symptoms When trying to perform live migration of container from PVA MN, the container is rebooted: Log into PVA MN Select any container Click Migrate Check Perform live migration to avoid service interruption. Choose a hardware node Click Migrate Container is rebooted The same situation occurs if one tries to migrate container via POA with the option 'Shut down VPS before migration' unchecked. Cause The problem is recognized as a product bug with internal ID PVA-33883. Resolution A permanent fix will be included in one of the future product updates. If online migration is necessary, it can be done using command-line tools: # pmigrate c CTID c DestinationNode/NewCTID --online # vzmigrate --online DestinationNode CTID Internal content

Original Publishing Date: 2020-01-22 Symptoms Trying to delete a host registered as a nameserver in OA fails with the following error: Service #xxx with name 'bind9' controlled by service controller #yyy is used on host 'ns1.domain.tld'. Cause During the host removal OA checks whether any services are using this host. In case the nameserver is used by any domain, the removal will fail. Resolution In order to proceed with removal, it is required to identify which instances use the DNS server that is being removed, and switch them to another nameserver: In OA Provider Panel go to Services > Domains > DNS > Nameservers and find ID of respective server. Access OA database and execute the following query: SELECT * FROM dns_reverse_zones WHERE xxx IN (ns1, ns2, ns3); Replace xxx with real ID of the nameserver from step 1. In case any value is returned, it means that this nameserver is used to host respective reverse DNS zones. In OA UI go to Services > Domains > DNS > Reverse DNS Zones > Zone > Zone Info, click "Edit" and remove or replace required name server. Run the following query to identify whether there are domain zones using this nameserver: SELECT * FROM dns_hostings h JOIN dns_zones z ON (z.hosting_id = h.hosting_id) WHERE xxx IN (h.ns1, h.ns2, h.ns3); Replace xxx with real ID of the nameserver from step 1. If any results are returned, please contact Odin technical support to fix the issue. Internal content Link on internal Article

Original Publishing Date: 2020-01-22 Symptoms After Upgrade to 5.5, the API Call pem.addDomain keeps failing with the error: Invalid hosting type '0' passed. Please refer to the Parallels Automation OpenAPI documentation. Cause This is caused by POA-82272 Resolution The issue will be fixed in one of future updates of POA. For now please use the following workaround: Set Auto-host Domains parameter in all Service Templates to Yes Call pem.addDomain without hosting_type parameter in case of physical hosting needed. Please contact your account manager regarding POA-82272. Internal content