Max Pyziur wrote:
Before disk failure we managed to gzip-tar the Drupal-related websites, and run pg_dump against the respective website's Postgres database.
We've restored the Drupal-related websites to their same respective directories (ones that the webserver recognizes.
Did you restore the database users and privileges with the same passwords as before?
We've restored one of the Drupal-related databases; some adjustments had to first be made to the contents of one of "pg_dumps;" i.e. two lines had to be modified from 'CREATE FUNCTION greatest ...' to 'CREATE OR REPLACE FUNCTION "greatest" ....' in order for the Postgres database to be restored.
However, the website returns Drupal's "Blue Screen of Death." (It's a nice shade of blue). The one that says, "Site off-line .... If you are the maintainer of this site, please check your database settings in the settings.php file and ensure that your hosting provider's database server is running. ..."
At least you didn't get redirected to the install page. It finds settings.php but can't get logged into the DB.
The database server is running, since other (non-Drupal) databases are fully accessible.
While the general plan is keep looking through log files, trying to find clues to the cause, suggestions from the user community would be helpful, especially who have encountered similar circumstances and problems.
Make sure to truncate cache* tables and the session table.