By ESR on
Hi,
I just did a CVS update (-> 5.3) on my local copy of my site. This was the first time I tried this. CVS went well (I think, I'm not an expert on that) but my site now gives me a 500 internal server error. Contacting the server administrator won't help 'cause that's me.... Anyone a clue what's happening?
Thanks in advance.
Comments
Possibly you've now not got
Possibly you've now not got a .htaccess file? Else... Maybe permissions are messed up? You shouldn't use CVS to update sites, check who 'owns' the files - maybe your webserver isn't permitted to read them?
Pobster
I checked and now have 2
I checked and now have 2 .htaccess files. One 'normal' and one (the old one I guess) renamed in .#.htaccess.1.81.2.2. Would it be helpfull to rename the latter back into .htaccess? And euhm, why shouldn't I use CVS to update sites? It's for updating drupal/themes/modules no?
No it's really not for
No it's really not for that... That's why there's the Update Status module to let you know when a module is out-of-date and needs updating. CVS is for development and may not give you the permissions you need on a live site. Plus... If you use CVS to completely fill your modules and themes folders with everything available you'll likely run out of memory when you try and access the admin/build/modules page in Drupal...
I'm not bitching about it, do what you like - I absolutely don't care what you do... Just passing a comment...
Pobster
Mmm, sorry, I'm not saying
Mmm, sorry, I'm not saying that you are bitching about it, I just thought it was the way to upgrade the stuff. So it's not and I messed up things without thinking first. Now I have to learn to get it to work again. That's good.
Anyway, thanks but the problem still exists. Deleting/renaming .htaccess doesn't work yet....
What I was getting at is
What I was getting at is that after using CVS to update your site its entirely probable that now all your files 'belong' to CVS and your webserver can't read them. Just unzip a fresh Drupal download into your root directory then see if you can access it - if you can then, yep - permissions problem caused by using CVS...
...and apologies if the above sounded abrupt! I'd just prefer to solve your problem rather than have a discussion about how people keep their sites up-to-date...
Pobster
Thanks. As I mentioned the
Thanks. As I mentioned the sites are on my localhost. I never had any problems with permissions, and I ran a few but always 'by hand'. I'm certain that doing a fresh install will solve the problem and I probably will try that. Done in a sec. But if something goes wrong, I just want to undersatnd the problem. You can learn by doing stupid thing.
Nope I think that's the
Nope I think that's the first time you've mentioned it! Anyways, it doesn't really matter... I don't think you appreciate that CVS isn't updating your files - it's overwriting them with newer versions, hence it's CHANGED the original permissions. It's highly likely that if you take a look at them you'll see that they're owned by 'CVS' with group 'CVS' or something similar... That'll be why your webserver can't read them - just take a look?
I'm not talking about doing a fresh install, just installing a fresh codebase in a new directory to check that this really is the problem. If you navigate to the new directory and *still* get the issue then obviously something else is up and we'll deal with that then...
Pobster
Try deleting .dtaccess
Try deleting or renaming the ".htaccess" file in main drupal folder.
It solved my problem:)
Renaming .htaccess didn't work
I have the same problem:
After upgrading my drupal from 5.1 to 5.3, I can browse to any of my (multisite) start pages. But when clicking on any link in the menu I get the 500 error. I tried to rename .htaccess and the only thing that happend was that I now get a 404 error when clicking on any link.
Can anyone help? Why can I see my drupal start page, but all the others don't work??
By the way: most of my multisites are accessed via redirected URLs (e.g. sub.example.com => www.example.com/drupal). The default site can be accessed directly (www.example.com/drupal) and IT WORKS! Why does this thing work, but all the others show me errors?
Matthias
Your problem is unsurprising
Your problem is unsurprising considering what you're doing... It's quite simple really, apache brings up index.php as a default page so when you navigate to your top level directory the front page is shown (by default, as it's the same as typing www.whatever.com/drupal/index.php). The .htaccess file handles rewriting and (easy explanation follows, its actually a bit more complicated than this...) 'tells Drupal which page it should be displaying' - it in effect passes anything after www.whatever.com/drupal/... TO drupal. You'll notice that you don't have a folder called... 'menu' or 'forum'... All your pages aren't *cough* physical (you know what I mean) they're stored in the database. Without a .htaccess file (if it's deleted or called something other than .htaccess) then apache doesn't look to the db for your pages, it looks for files or folders called whatever you're trying to access. As they don't exist as files or folders, hence you're getting 404 error messages.
To sort this, put a fresh *FRESH* .htaccess file from the Drupal project download into your top level directory. Then access your site NOT USING CLEAN URLS (if you require them, then directly type in the page which handles clean urls and disable them first, then re-enable them). Job done...
Pobster
Maybe a rewrite problem?
I just noticed, that my only working site does NOT use clean URLs, while all others do. Could these be the cause of the problem? And how can I switch of clean URLs if I can't log in anymore (because I get a 500 error of course)??
EDIT: it definitely has to do with clean URLs! I tried to manually enter the address of some of my pages WITHOUT clean URLs (e.g. www,example.com/?q=contact) and it worked! What happened to the clean URLs that worked just a day ago? Can anyone explain this strange behaviour? It seems, a whole lot of people are experiencing this.
Error 500 is ambiguous, what
Error 500 is ambiguous, what do your apache error logs say? I'd perhaps use a fresh .htaccess file anyway? It's likely that its something in there which has borked. Anyways, in the upgrade it's one of the files which has been updated so you should use the newer version anyway.
Pobster
I updated drupal to a
I updated drupal to a completely new directory, so I should have all the new files. I only copied the "file", "modules" and "sites" folder from my old drupal installation.
How to log in without clean urls
...but then: how do I log into the admin panel without using clean urls? sure, i can access the login page via www.example.com/?q=user, but when clicking the submit button, I get the 500 error again. How can I log in without clean urls when clean urls are enabled for the site? I need to log in to turn clean urls off.
Problem SOLVED
This thing here http://drupal.org/node/165761 solved my problem. Just added the "RewriteBase /" to my .htaccess and now it all works with clean urls :o). Hope this solution helps some of you, too.
Me Too
It worked for me on GoDaddy hosting.
Drupal 5.5 & clean URL's.
Thanks morgler.
+N
It doesn't matter, the
It doesn't matter, the cookie will still be generated regardless of the bad link.
Pobster
Ah good, glad you got it
Ah good, glad you got it working. ;o)
Pobster
500 Error Detail
To show greater detail than a 500 error turn off "friendly errors" in IE. Go to Tools >> Internet Options>> Advanced. Under "Browsing" section uncheck "Show friendly HTTP error messages". This will give you a better understanding of what is going on behind that error and will show a more detailed message most times.
500 Error Detail
To show greater detail than a 500 error turn off "friendly errors" in IE. Go to Tools >> Internet Options>> Advanced. Under "Browsing" section uncheck "Show friendly HTTP error messages". This will give you a better understanding of what is going on behind that error and will show a more detailed message most times.