Acquia Cloud the Website Encountered an Unexpected Error Please Try Again Later

Troubleshooting awarding imports¶

As described in Importing an existing application, there are several different methods you can use to import a Drupal application into Cloud Platform. In the bulk of cases, the import process works quickly and smoothly. Here are some things you can do to make the import work better and some things to check for in those cases where information technology does not work.

Before you import your application¶

Read Preparing a Drupal application for export, which lists recommended steps to take before you import your Drupal application to Cloud Platform.

Apply transmission import process for multisite¶

Multisite Drupal installations use a dissever database for each website within the application. The site import procedure used by Deject Platform can import but applications with a single database. If you want to import a multisite Drupal installation, you lot need to import it using the manual import process.

Check for dependency on unsupported PHP libraries or unsupported PHP version¶

Deject Platform runs a specific set of PHP libraries on the versions of PHP listed in Cloud Platform engineering platform. If your awarding requires a later or earlier PHP version or PHP libraries that do not run on Deject Platform, your awarding may not work on Cloud Platform.

Cheque your PHP memory limit¶

Cloud Platform configures a PHP retentiveness limit for your infrastructure. If your application is configured with a larger PHP retentiveness limit, it will not be able to commencement. The PHP retentiveness limit might exist gear up in one of iii places:

• The memory_limit parameter in php.ini
• The php_value parameter in .htaccess
• The memory_limit parameter in the Drupal settings.php file in sites/default/settings.php

For Deject Platform applications, y'all should never set whatever of these parameters in these files. Cloud Platform Professional customers tin can configure the PHP memory limit for an environment. Cloud Platform Enterprise customers can submit a support ticket requesting a change in the PHP retentiveness limit. If you have memory_limit settings in .htaccess or settings.php files, delete them earlier y'all import your application.

See also Conditionally increasing memory limits and Retentiveness consumption tracking tools for tips about controlling the amount of memory your application requires.

Checking for import success¶

Importing an application into Deject Platform is usually fairly quick, just it is not instantaneous. Depending on which import method you lot choose, the import process has three major steps:

1. Creating a site annal
2. Sending the site annal to Acquia
3. Opening the site archive and creating the application from information technology

Depending on the size of your application and your Net connection, the beginning 2 steps can take from a few minutes to, in some cases, more than an hour. Yous can check the progress by signing in to the Deject Platform interface, selecting your application, and clicking the activeness button. Later the site annal has arrived on the Cloud Platform infrastructure, you should see an entry like this in the action log:

              Import [archive-filename].tar.gz to environment Dev            

In addition, you can run across your site annal file on the infrastructure. Connect to the infrastructure with SSH. You lot should be able to observe the site annal file in /mnt/gfs/[site]dev/import .

One factor in how long a site import tin take is the size of of your site archive. You can minimize the size of the site archive by doing the following:

• Clearing your cache before yous offset the site import
• Removing any Drupal modules that have been disabled and that yous are not using

My application is on Deject Platform, only volition not beginning¶

If you have verified that your application's annal file has reached Cloud Platform, but your awarding does non start (volition not serve pages), here are some things you lot tin can check.

Get your awarding condition with Drush¶

1. Connect to your environs with SSH.

2. From the control line, run the drush status command, targeting your Dev environs:

Examine the output of drush status for errors that may give you clues about problems that are keeping your application from starting.

Look for errors in infrastructure and PHP logs¶

You can download your Apache infrastructure and PHP error logs from the Logs page for examination. As an alternative, y'all can obtain the logs by using SSH:

1. Connect to your environment with SSH.
2. Observe your Apache infrastructure mistake log at /var/log/sites/[site].[env]/logs/[infrastructurename]/error.log and your PHP error log at /var/log/sites/[site].[env]/logs/[infrastructurename]/php-errors.log .

Any displayed mistake letters should betoken the root crusade of the error. For more than information about the format of these log files and their contents, see Nearly Cloud Platform logging.

Disable problematic Drupal modules¶

I common reason why a Drupal application might not first on Cloud Platform is a custom Drupal module that volition not run on Cloud Platform. If you know which module is causing the problem, you can disable information technology. For data almost how to do this, run across Disabling modules that block sites on Cloud Platform.

Troubleshooting Acquia Connector imports¶

Here are solutions to some issues you may encounter in importing an application using the Acquia Connector.

The Migrate push doesn't practice anything when y'all click it¶

If the Acquia Connector does not beginning to drift your awarding when y'all click Migrate, clear your Drupal enshroud, and then retry the migration process.

To clear your Drupal cache, open your Drupal application's Performance page at http://[site_URL]/admin/config/development/performance .

Cloud Platform displays an mistake message when attempting to migrate your awarding ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~

If y'all are experiencing errors while migrating your awarding, clear the Migrate files directory check box, select the Reduce database export size check box, and so retry the migration process. These options are not displayed unless you have already attempted to migrate and encountered an error.

The following error messages describe the about common causes of issues with the migration process. If you don't run into your mistake bulletin, or the deportment associated with the message don't allow you to migrate your application, contact Support or apply a unlike application import method.

Mistake message	Explanation
No compression libraries bachelor	The application'due south installed PHP does not take available GZip or Zero libraries.
Cannot create temporary directory [file-system-directory] to store site archive	The Acquia Connector cannot create a directory in the Drupal files directory. Examine the file organisation permissions for the Drupal files directory.
Server mistake, please submit again	The Acquia infrastructure did not answer. Retry the migration process. If the Acquia Connector displayed this message at the finish of the migration process, examine the Cloud Platform interface Notifications panel to come across if an import is in progress, and if so, yous can ignore this error bulletin.
Signature from server is wrong	Your Cloud Platform application did not respond with a right signature, indicating possible transmission corruption. Retry the migration procedure.
Server error, unable to call back environments for migration	Make sure that your Development environs does non have a tag deployed. Environments with tags deployed volition be excluded from the eligible list of environments.
Transfer error	The Acquia Connector encountered an unknown error during the site annal upload portion of the procedure. Retry the migration procedure.
AJAX Fault regarding ReadyState	The Drupal batch process running the migration encountered an error. Consult Drupal logs for more information or retry the migration process.

guerrerosysion.blogspot.com

Source: https://docs.acquia.com/cloud-platform/create/import/troubleshooting/

Share this post