Permanent error during database update: An HTTP error 404 occurred. http://mysite/update.php?id=6&op=do

Just tried this in internet explorer and it didn't work, however I have now found the solution that works for me.

I had modified the .htaccess, and uncommented:

RewriteCond %{HTTP_HOST} ^website\.com$ [NC]
RewriteRule ^(.*)$ http://www.website.com/$1 [L,R=301]

And whenever I do this it seems to seriously muck up the update.php script.

So, what I now do (every time I update) is to comment these again, perform the update and then uncomment them afterwards. I know that there's also a new .htaccess file with every new install of Drupal, so in fact I use the new version first, and then copy and paste these lines into the new version, but only after running the update.php script.

I tried with firefox, chromium and opera. No success.

However, IE8 did the job. A think this must be taken as a bug. :-(

I have the same problem, also reported here by someone else:
http://drupal.org/node/316943

It is critical because we can't even apply updates to the database...
I don't have internet explorer at all and can't install it on my OS.

Confirmed on Drupal 6.16, running on PHP 5.3. I have the site running in a subdirectory (not multi-site), though my httpd.conf configs were working just fine earlier today, updates included... I'll dig further and see what I can turn up.

And I have the same problem - it started about a month ago,but it doesn't stop!

An unrecoverable error has occurred. You can find the error message below. It is advised to copy it to the clipboard for reference.
Please continue to the error page

An HTTP error undefined occurred. http://szczesniak.pl/update.php?id=83&op=do

Drupal 6.16

I was having this problem too, then I tried Aminto's solution, except that I comment out the following code from my .htaccess

RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://www.mysite.org/$1 [R=301,L]

Then I run update.php, which runs correctly. Then I go back to my .htaccess file and uncomment the above code back in (the code is necessary to make my site secure. For some reason, when that code is in .htaccess, update.php will not run correctly.

So, every time I update a module and need to run update.php, I have to do the above procedure. Tedious, but I've found no other way.

By the way, a big THANK YOU to Aminto for posting his solution. I was pulling my hair out. I have Drupal 6.16 now but have heard hints that D7 will handle SSL differently and better...I'm crossing my fingers!

Solution: change the browser. I couldn't upate with Chrome. No problem with FF. All updated :-)

I followed bitozoid (#2) solution and it works.. Very strange indeed.

Updating a site from D16 -> D17 I got the same error and #1 worked

but I got this error at the end:

* user warning: Table 'decibelp_meier.semaphore' doesn't exist query: SELECT expire, value FROM semaphore WHERE name = 'menu_rebuild' in /home/decibelp/public_html/meier/includes/lock.inc on line 154.
* user warning: Table 'decibelp_meier.semaphore' doesn't exist query: SELECT expire, value FROM semaphore WHERE name = 'menu_rebuild' in /home/decibelp/public_html/meier/includes/lock.inc on line 154.

updated a few other sites without the problem...

hmmm - I previously noticed this site would "hang" during update, but when I aborted it seemed to be completed.

something funky, maybe it is the missing semaphore table...

{later}

I copied the semaphore table from another site (I don't even know what it does) and I don't get the user warnings - but still getting the HTTP error - actually my error is

An HTTP error 0 occurred....

but #1 fixes it anyway

so I had lots of other problems see #861918: trying to fix funky site with Backup & Migrate which tables should I keep in the fresh install, which should I overwrite

it turned out that my variable table was messed up, and I was using caching

I backed up the db, made a fresh install, and re-imported the db from the site

I disabled all caching, cleared the caches and - voila - all the problems went away, including update.php ones

happydays

just remember the developer's mantra: CTFC...CTFC...CTFC...CTFC... (Clear the F**king Cache)

In sites/default/settings.php change
$base_url = 'http://website.com'
to:
$base_url = 'http://www.website.com'

Thank you, thank you, thank you!

This problem is caused by a wrong configuration of $base_url and should be prevented by inserting a warning message to the requirements system. Therefore I created a new issue and this is now a duplicate of #1046682: Install/Update process fails if $base_url is set to a wrong URL. Please reopen if I'm wrong. Thanks!

#12 works for me after trying others ...

cheers