Blog Marco

My previous host lost a week's worth of data - Thank God I had a regular back up regime to fall back on - otherwise i really would be starting my blog from square one. I recently converted to MediaTemple hosting - a reputable host among internet users according to many forum postings (If you decide to signup with them - tell them that "photos2view.com" sent you in the signup form). The one time it did go down was from a power outage in Los Angeles. Other webhosting services I've subscribed to in the past all died because of their own fault.

Anyway, a new host means a whole new set of small customisations to make my backed up website files and my backup database work with the new website server constraints.

maximum number of internal redirects reached

So I uploaded the files, created a database, uploaded my database there and had the frontpage of my website running. the problem was when I clicked on any internal link I would get a page that came up when I tried to access the page was "Internal Server error." I only found out what was actually happening when I accessed the server error logs. Ask your host or in MediaTemple (mt) you can find it in the error folder.

The first error from the server logs I got was:
"mod_rewrite: maximum number of internal redirects reached. Assuming configuration error. Use 'RewriteOptions MaxRedirects' to increase the limit if neccessary."

So I thenGoogled for the error... and found a few posts addressing this problem.

The fix is with the .htaccess file in the root directory of of your Drupal installation. Now the FIX is to find this line:
RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]

And replace it with this line RewriteRule ^(.*)$ /index.php?q=$1 [L,QSA]

The whole internal server error is caused by a single forwardslash (/).

Links from the Drupal forums which point out how to solve the "maximum number of internal redirects" error.
mod_rewrite error
Drupal 4.5 RC - SAFE MODE Restriction in effect.

Allowed memory size of 8388608 bytes exhausted

The next error I had was when I was browsing around - especially with pages with images:

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 640 bytes) in /home/virtual/site/fst/var/www/html/blog.photos2view.com/includes/image.inc on line 284

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 2560 bytes) in /home/virtual/site/fst/var/www/html/blog.photos2view.com/includes/image.inc on line 284

And once again I Googled for : Allowed memory size of 8388608 bytes exhausted

A reply on one forum said:
"by default the maximum allowed memory for a script is 8mb which is the equilivant to 8388608 bytes and for some reason your script is using up more then 8mb of memory... either theres a bug in your script or the output is very large - you need to increase the value in the ini setting - if you have access to your php.ini file incrase the value in this line

memory_limit = 8M ; Maximum amount of memory a script may consume (8MB)

if not you should be able to change it using the ini_set function (look it up in the manual @ php.net)."

But in (mt) MediaTemple you can't touch the php.ini file in the Shared Virtual Hosting accounts and their work aroung was to add a line in the .htaccess file:

php_value memory_limit 16M

Good Luck!

Webmaster information | bookmark | reddit | cosmos»