I have seen other threads on this error that suggest looking at the watchdog table, which might be filling up with errors ( via a select * from watchdog). You might try deleting all the records in watchdog, visiting the site then looking at watchdog again to see what info is in there.
This isn't a civicrm installation is it?
Looks like you've got a thorny one....
Dave
-----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Max Pyziur Sent: Monday, March 25, 2013 1:25 PM To: support@drupal.org Cc: Earnie Boyd Subject: Re: [support] Recent move Drupal 6.22, PHP5.3, PostGresql 8.4 doesn't work - continuing
On Mon, 25 Mar 2013, Max Pyziur wrote:
On Mon, 25 Mar 2013, Earnie Boyd wrote:
Ensure you empty any table with cache* as well as sessions table.
I take it you mean running a script like this: DELETE FROM cache WHERE 1=1; DELETE FROM cache_block WHERE 1=1; DELETE FROM cache_filter WHERE 1=1; DELETE FROM cache_form WHERE 1=1; DELETE FROM cache_menu WHERE 1=1; DELETE FROM cache_page WHERE 1=1; DELETE FROM cache_update WHERE 1=1;
DELETE FROM sessions WHERE 1=1;
(1=1 is a kluge I used when I worked on Informix databases; probably unnecessary these days).
Thanks.
I tried this procedure on one site, and it still fails to remove the 503 error.
However, this does seem to be the correct area (stored data) to remedy this.
New Drupal installs of 6.14 to 6.28 on Postgresql 8.4/PHP 5.3 do work/function.
So it isn't the software (PHP and Postgresql), it points to the data.
Max Pyziur pyz@brama.com
[... recycle ...]
Earnie
On Mon, Mar 25, 2013 at 1:34 PM, Max Pyziur pyz@brama.com wrote:
On Sun, 24 Mar 2013, Jamie Holly wrote:
[... delete for the sake of brevity ...]
[ Drupal support list | http://lists.drupal.org/ ]