Known issues in Cloud Next¶

Interruption in web requests taking longer than 10 minutes¶

In Cloud Next applications, web requests that take longer than 10 minutes might be interrupted by routine platform maintenance activities.

Two daily backups¶

The Cloud Platform user interface may occasionally display two daily backup tasks for the same day, indicating the backups taken at different times of the day.

Unable to copy files between environments¶

The system might display the following error when you attempt to copy files between environments:

rsync: change_dir "/mnt/source/mnt/data/[UUID]-real-shared/sites/[SITENAME]/files" failed: No such file or directory (2)

Until Acquia provides a resolution, contact Acquia Support for assistance with copying files.

“End of script output before headers” error occurs if the HTTP response header exceeds 8 KB¶

Cloud Next introduces a limit of 8 KB to HTTP response headers. When using HTTP headers, ensure that the header size does not exceed this limit. For example, this limit might be triggered when you use:

• Acquia Purge module that is configured to output debug headers
• Security Kit (seckit) module that is configured to output X-Content-Security-Policy headers

File copy operation takes longer in Cloud Next compared to Cloud Classic¶

The file copy operation in Cloud Next takes longer as compared to Cloud Classic. This occurs because the files are first copied from the production environment to an intermediate ODE environment, and then to a migration environment. After the copy operation is complete, the system deletes the ODE environment, thereby keeping only the migration environment. This additional step in the migration process consumes more time.

Cloud hooks are not executed¶

When you copy files or databases from a Cloud Next environment to a Cloud Classic environment, cloud hooks are not executed.

Until Acquia provides a resolution, contact Acquia Support for assistance with copying files.

Change in mod_headers behavior in Cloud Next¶

In Cloud Classic, mod_headers directives in the .htaccess file are ignored for PHP and Drupal requests, and are only applied to static files. However, in Cloud Next, mod_headers directives in the .htaccess file are applied. This might result in unexpected or unwanted changes in application behavior. Acquia recommends that you review your .htaccess file for mod_headers usage.

Static IPs not supported for Log Forwarding¶

Currently, Cloud Next does not support sending logs from static IPs.

MySQL 5.7 features incompatibilities on Cloud Next¶

Cloud Next leverages AWS Aurora MySQL. A few of the MySQL 5.7 features are not supported on Cloud Next. For more information, see list of unsupported MySQL 5.7 features.

Scheduled jobs must not use hardcoded log paths¶

Scheduled jobs or cron jobs on Cloud Next must not use hardcoded log paths.

Pushing multiple commits causes code deployment failures¶

When you push multiple commits to a branch in quick succession, you get the following error in the task log in the Cloud Platform user interface:

Server does not allow request for unadvertised object <git-sha>

For example,

Server does not allow request for unadvertised object 48db8d8a88679468ccdc677753d8a2c9cb0ee117

For example, let us assume that you run the following commands in the same order:

git commit -m "Commit A" ; git push

git commit -m "Commit B" ; git push

git commit -m "Commit C" ; git push

Results:

• Deployment related to the A commit fails if you try to deploy the B or C commit before the push related to the A commit reaches the build step. In such a case, the system does not deploy code or run cloud hooks, and retries deployment for 60 minutes.
• Deployment related to the B commit fails. The system retries deployment for 60 minutes.
• Deployment related to the C commit succeeds.

You do not need to take any action unless you want the cloud hooks for the first push to run before the subsequent pushes.

SSH error with OpenSSH version 8.8 or later¶

After upgrading your local version of OpenSSH to 8.8 or later, you might get the following error while connecting to a Cloud Next environment over SSH:

###@###.ssh.prod.acquia-sites.com: Permission denied (publickey).

Workaround:

Add the -o PubkeyAcceptedAlgorithms=+ssh-rsa option when using SSH, or add the following to the ~/.ssh/config file:

Host *.ssh.prod.acquia-sites.com
PubkeyAcceptedAlgorithms +ssh-rsa

Issues connecting to Cloud Next environments with locally-installed MySQL Workbench¶

If you have MySQL Workbench installed locally, you might not be able to connect to environments on Cloud Next. This issue occurs for a few versions of MySQL Workbench.

However, you are not impacted if you are running Sequel Pro locally.

If you face issues connecting to Cloud Next environments from MySQL Workbench, do the following:

1. Locate the database credentials listed on your Databases page.

2. In a terminal in your PC, run:

   {ssh -L $LOCAL_PORT:$DB_HOST:3306 $SSH_STRING}

   Here,

   • LOCAL_PORT is the port to which Workbench must connect when using localhost.
   • DB_HOST is the hostname obtained from the Cloud Platform user interface.
   • SSH_STRING is the full connection string from the Cloud Platform user interface. For example, user@something.

Long code deployment times¶

Environments on Cloud Next may intermittently experience code deployment times taking more than five minutes.

memcache_admin incompatibility¶