By bmcraec on

Hi,

I'm hoping that someone can help with the following. I'm a bit of a newb with this stuff, so I'm betting it's something I didn't do properly.

When trying to run update.php after over-writing all the 6.9 folders with the 6.10 ones, I get the following:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 901 bytes) in /home/costarm/public_html/includes/database.mysql-common.inc on line 41

Run update again, and I get:
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 76 bytes) in /home/costarm/public_html/includes/bootstrap.inc on line 501

Also, the admin interface now seems completely different; unless that's a factor of a pootched Drupal install. How do I manage modules? Where do I switch back to on-line mode? There are currently only three admin choices available:

  1. Content Management (no tasks available)
  2. Site Building/Blocks
  3. Site Configuration/Actions (able to add advanced actions from a pop-up list)
  4. User Management/Access Rules (and there's no way to add a rule)
  5. Reports (I don't seem to have any administrative tasks set up)

Is there THAT much difference between 6.9 & 6.10, or is there something seriously broken?

⋅ Categories: Drupal 6.x

Comments

cog.rusty’s picture

cog.rusty commented

The problem is what the error message says. Your PHP memory limit is 32M and Drupal needed a few bytes more for that page. Obviously you were already "almost" out of memory.

You need to increase your PHP memory limit to 48M or 64M, or remove some modules. See http://drupal.org/node/207036

After you fix the problem, run update.php again to rebuild the menus.
To switch to online mode, login at the /user page and then go to /admin/settings/site-maintenance

bmcraec’s picture

bmcraec commented

Yep, reading the message would help, wouldn't it?

Thanks once again for the pointer, cog.rusty. So, now I've set the .htaccess PHP memory setting to

php_value memory_limit 48M

and I now get:

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, webmaster@co-starmedia.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
Apache/2.2.11 (Unix) mod_ssl/2.2.11 OpenSSL/0.9.8b mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 Server at www.co-starmedia.com Port 80

Possibly a limit set by my hosting company?

Also, I've tried a couple of experiments with settings. With .htaccess edited to
php_value memory_limit 16M

and no change to settings.php, I still get the message above.

With .htaccess unchanged (the above commented out), and the settings.php file changed to include
ini_set('memory_limit', '48M');

One other wierd thing; settings.php shows a modified date of 01/01/70 12:00 AM. Trash it and start again?
I can get back to the "Site Off-line for technical problems" screen. And, I can't login with "http://www.co-starmedia.com/?q=user"

cog.rusty’s picture

cog.rusty commented

It is possible that your server restricts the use of .htaccess for some settings, but the ini_set() line in your settings.php should work. Doesn't it?

Don't worry about the file date, it doesn't matter.

Notice the error message at the end of your "off-line" screen. It says "Access denied for user 'costarm_drpl1'@'192.168.2.7' (using password: YES)." Maybe some of your login information are wrong and you need to fix them in your settings.php file, $db_url line.

bmcraec’s picture

bmcraec commented

Hi cog.rusty

I successfully edited both .htaccess and settings.php (after changing permissions on both to do so). I had success with the settings.php change, but not with the .htaccess change, having tried first one, then both, then the other.

I've got my hosting tech support on it now. The funny thing is that the DB username hasn't changed from 6.9 to 6.10, nor has the password for that db & userID, so something may have gone corrupt in the DB? I've run repair on it a couple of times.

Aha!!! Problem identified! It was something weird happened to the settings.php file. Somehow, and I didn't change it, the url setting got changed from "localhost" to an IP address. The tech guy sorted it out, and bang, it's now working, going through the updates.

bmcraec’s picture

bmcraec commented

After several hours, update.php just runs on and on. When I close the window, and try and log back on (site is still in maintenance mode) with /?q=user, I've got a partially working site, as described in the initial post. I have increased the php memory settings, and removed all but the core modules, but still have a pootched site.

Further suggestions, or would I be better off scrapping this, reinstalling a clean version, and attaching to the existing DB?