Hello

I have been using the frontpage module for many months without any issue. My site is hosted on godaddy's ultimate linux shared hosting. Suddenly 2 weeks ago, I started getting internal server error 500 only when I login and its getting redirected to the authenticated user's homepage. I had not made any changes prior to this error starting. Once this error happens, I can go to any other page on the site (if I know the URL ofcourse). Its only this frontpage that is throwing this error.

I have called godaddy many many times and they are of no help. Interestingly, I copied the same site to an economy hosting server and that works fine without any issue.

Please help
-vas

Comments

timhilliard’s picture

Status: Active » Postponed (maintainer needs more info)

Hi vgulla,

Unfortunately I don't think you have given me enough details about this error for me to help you. Aside from that I think it's fair to say from your description that there is something funky with your godaddy environment. Have you tried setting the authenticated user settings for front page to some other setting? Since it's a 500 error have you tried looking at your php error log?

If you manage to get any more information let me know and I'll try and help you.

Thanks,
Tim

vgulla’s picture

Hi Tim

Thanks for replying. What I noticed is that the issue is just with the authenticated homepage. Changing it to something else, doesn't work too.. the 500 error comes up on that page. I disabled front page and login destination module and still get the error upon logging in. Sometimes just refreshing after this error comes up, works and once this error comes up, I can navigate to any other page on the site (if I know the URL that is). Could the issue be with just the login module? I cannot disable that since I have users using it to login.

The error log just shows this error:
Premature end of script headers index.php.

Things that I tried and didn't work:
1. Disabled fast cgi
2. Added RewriteBase /med (med is the directory in which I have drupal installed)
3. Increased the memory limit, max execution time in php5.ini that is in my med directory.
4. Disabled front page module and login destination module suspecting these to be problematic.

Hope I have given all the information.

Thanks in advance
-vasantha

timhilliard’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Hi vasantha,

It sounds like the cause of your problem has nothing to do with the front page module then. Since you have access to the server I would definitely have a look at the error log. That will be able to tell you a lot more than "Internal Server Error 500", it should be able to tell you what the specific fault is, in what file and on what line. On a Linux box this can usually be found at /var/log/apache2 or /var/log/httpd.

As this is not a front page error I'm going to close the issue. If you find out later on that the issue is indeed from front page module then please feel free to reopen the issue. If you need more help troubleshooting your problem I would suggest jumping onto IRC channel #drupal on freenode. More details about this can be found at http://drupal.org/irc. I would also suggest trying to drupal forums.

Thanks,
Tim

vgulla’s picture

Here is what I found so far.

Upon enabling devel module, I found that there were way too many queries trying to retrieve the URL aliases. I have 60K nodes in my DB and on the homepage, I have a tag cloud and a quicktab block showing forms to add different content types. Each content type has a drop down or autocomplete boxes for node references. It seems the URL alias query is being fired for these dropdowns as well. When I deleted the URL aliases, the 500 error went away. When I removed the quicktab block with all the forms, the page was blazing fast.

Now, how do I go about optimizing the forms quicktab block? Secondly, is there an optimal way to use uRL aliases? I don't want to expose node/### since its not good for SEO

Thanks so much

-vasantha

timhilliard’s picture

Status: Closed (cannot reproduce) » Closed (works as designed)

Hi vgulla,

Glad you were able to get things working again. Unfortunately optimizing the forms quicktabs block is not something I can help you with in this issue nor is it anything I have any knowledge or experience with. I would suggest trying the support forums of the #drupal channel on IRC.

Since this is no longer related to the front page module I'm going to close the ticket.

Thanks,
Tim