You still aren't getting the PHP errors though that would be causing this. You need to configure your PHP to show the errors. Go to your php.ini file and set error handling to this:
error_reporting = E_ALL & ~E_DEPRECATED & ~E_NOTICE display_errors = On log_errors = On
Then restart Apache and try accessing the site and see what it says. Since you originally got a Drupal error page, that means PHP is executing, but there is an error hiding in there somewhere (which can also be something in the database). You need to get PHP's errors to be able to track that down. Generally the site offline error page means there is some connection issue with the database, so you might want to double check the $db_url in settings.php.
Jamie Holly http://www.intoxination.net http://www.hollyit.net
On 3/24/2013 5:05 PM, Max Pyziur wrote:
On Sun, 24 Mar 2013, Jamie Holly wrote:
Apache doesn't have anything to do with the database. That's PHP and Drupal. Since you're getting the site offline error, there's a problem within the database. Check your PHP/Apache error logs and see what's being reported there.
In the Apache logs, there is a 503 error; the message means "Temporarily Unavailable --- the service or file that is being requested is not currently available."
Is this a setting within the database? If so what table; can I do an update sql command?
Where else can I look?
By having done a fresh install, I see that Drupal 6.28 and PHP 5.3 can coexist.
Jamie Holly http://www.intoxination.net http://www.hollyit.net
Thanks very much for your help.
Max Pyziur pyz@brama.com
On 3/24/2013 4:29 PM, Max Pyziur wrote:
Are you running Varnish? If so, is the new server configured properly in terms of Varnish listening on 80 and the vhosts on 8080, and 8080 being a configured port?
No.
As a test, I did a fresh install of Drupal 6.28 for a test user. The site runs. The sites that were restored from a pg_dump do not.
I'm checking a variety of configuration settings: e.g. 47 Tables in the new database, 47 in an existing site.
Perhaps it is an Apache configuration?
fyi,
MP pyz@brama.com
On Mar 24, 2013, at 2:18 PM, Max Pyziur pyz@brama.com wrote:
Greetings,
Due an emergency (failing disk) we moved our whole server from a CentOS 5 machine to a CentOS 6.
In the process, newer software versions were installed by default; relevant to Drupal CentOS 5 had PHP 5.1; CentOS 6 now has PHP 5.3 CentOS 5 had Postgresql 8.1.x; CentOS 6 has Postgresql 8.4.x
The way I restored the Postgresql databases was through pg_dumpall to a huge text file, and then psql postgres < AllPostgresDatabases.out on the PG 8.4 system.
Our Drupal installations were local from tarballs, not from RPMs. In most cases they are Drupal 6.22
The sites all show Drupal's blue page - site offline.
The Apache logs show that the page returns a 503 Error.
I'm in the process of trying to debug and in a bit of a rush. Usually, I try and research this in detail before posting.
Much thanks for any advice on returning these sites to status quo.
Max Pyziur pyz@brama.com -- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]