Konstigt 500 Internal Server Error

Events happening in the community are now at Drupal community events on www.drupal.org.
antonnyman's picture
Posted by antonnyman on January 30, 2012 at 3:46pm

När jag ska lägga till en ny användare får jag ett konstigt felmeddelande.

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, root@localhost 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.

Sidan ligger på en delad host, så jag fattar inte varför det står root@localhost. Jag har provat att ta bort .htaccess och avaktiverat rena urler.
Någon som haft ett liknande problem?

Categories:

Comments

Vad säger apache-error log?

Posted by kristofferwiklund on January 30, 2012 at 4:09pm
kristofferwiklund's picture

Har haft likande på vissa webhotell där felmeddelanden från PHP inte skrivs ut utan man endast får ett error 500. Troligtvis är det något syntax-fel i php-filerna. Har du någon egna moduler eller likande. Finns det möjlighet att visa PHP error på hosten?

Jag löste det med att göra

Posted by antonnyman on January 31, 2012 at 2:37pm
antonnyman's picture

Jag löste det med att göra ett nytt konto på "vanliga" sättet. Men jag ska kontakta supporten för Binero och kolla vad som kan orsaka felet.

I have had such http errors

Posted by jaxxed on February 6, 2012 at 6:31pm
jaxxed's picture

I have had such http errors occur in 2 circumstances:

  1. error in db configuration in settings.php, where the databased referred to has an invalid installation (missing db, missing tables). In this case drupal seemed to think that it was past installation, but couldn't make the db connection work;

  2. overloading the apache server with resources: Drupal can be a memory hog, and during development I have had some server reply to heavy requests with a 500 error. In this case, the server can not acquire the resources (memory and cpu) to thread a new request. The behaviour tends to start with a certain operation/page, and then from that point exhibit on many other pages (sometimes even simple ones.)

If the 500 error occurs on certain heavy pages (admin/[build|structure]/modules), or feed imports; or if it tends to go away if the server is left alone (10 minutes or so), then it is likely that you suffer from #2. If you can get no access to the site, then check #1.

There are of course things that I don't know about that could have caused the error.

I apologize for my language. My Swedish is to poor to write.

J