Theo
asked on
Internal server error ;'Unable to allocate 35 bytes'
This is the setting: I Run the Drupal CMS which controls two domains. Each time when I instal a particular module ('Views') I get an Internal Server Error. This error makes the Administrative section of my websites inaccessible. I can only regain access by going to PhPMyadmin and change the status of that module from 1 back to zero.
Since the module consists of several parts it is strange to note that on site 1 this error sets the status of part 1 to 1 and on site 2 it sets part 5 of the module to 1.
My Raw Access logs mention a lot of 304 errors (I know these are not real errors, though they are no cause for joy either).
My error logs say:
For site 1: (host) FATAL: erealloc(): Unable to allocate 19456 bytes
[Wed Aug 15 10:56:09 2007] [error] [client 82.176.201.176] Premature end of script headers: /www/klimatosoof/cgi-bin/p hp
For site 2: FATAL: emalloc(): Unable to allocate 35 bytes
[Wed Aug 15 10:51:56 2007] [error] [client 82.176.201.176] Premature end of script headers: /www/klimatosoof/cgi-bin/p hp
Hope anyone knows how to get rid of these!
Since the module consists of several parts it is strange to note that on site 1 this error sets the status of part 1 to 1 and on site 2 it sets part 5 of the module to 1.
My Raw Access logs mention a lot of 304 errors (I know these are not real errors, though they are no cause for joy either).
My error logs say:
For site 1: (host) FATAL: erealloc(): Unable to allocate 19456 bytes
[Wed Aug 15 10:56:09 2007] [error] [client 82.176.201.176] Premature end of script headers: /www/klimatosoof/cgi-bin/p
For site 2: FATAL: emalloc(): Unable to allocate 35 bytes
[Wed Aug 15 10:51:56 2007] [error] [client 82.176.201.176] Premature end of script headers: /www/klimatosoof/cgi-bin/p
Hope anyone knows how to get rid of these!
ASKER
I am trying for days now to get an answer at the Drupal forums, no reactions. Is there a specific Drupal corner here at Experts Exchange?
The problem is that I just had this same server error while trying to run cron. Clicking back and trying again solved that.
The problem is that I just had this same server error while trying to run cron. Clicking back and trying again solved that.
ASKER
Also I am not sure whether this is an inability of the module to run two instances. When I select to install it, it isnt installed in the other site. I havent tried yet to produce two Internal Server Errors by installing them on both sites.
Fyi: The tables for the two sites belong to the same database but have their own prefix. Standard procedure in Drupal.
Fyi: The tables for the two sites belong to the same database but have their own prefix. Standard procedure in Drupal.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It seems that your module does not allow you to run several instances on the server... this creates the MySQL problem.
Any clue from the module FAQ or forum?