By zvikico on

Hi,

I'm having trouble running the update.php. This happens in Drupal 6.8. I'm getting to the update stage, I'm getting the progress bar, but nothing happens. Using Firefox with Firebug I got the following error "Access to restricted URI denied" code: "1012" in jquery.js?j (line 13). The code presented in the console is "eval(function(p,a,c,k,e,r){e=function(c)...r|serialize|pixelLeft'.split('|'),0,{}))".

Trying to do it in Safari fails, too.

Any ideas?

Thanks.
Zviki

⋅ Categories: Drupal 6.x

Comments

Mark_J’s picture

Mark_J commented

I think the problem is permission related but I cannot be sure. Normally Drupal warns you if the vital files don't have the right permissions. I would not want to advise you giving your files write access but you can try and see what happens and then restore the original permissions. At this stage, personally it is all I can advise you. I am sure someone else around here will give you a better advise. Just hang on.

peterx’s picture

peterx commented

The update from 6.7 to 6.8 does not change anything in the database. If you are updating from an earlier release to 6.8, there could be database updates. Some database updates change every row in big tables and can time out if you have limited resources. What is your current release?

When you turn on Firebug, Firebug picks up Javascript errors not normally visible. You can get errors where something runs to completion with Firebug off but times out with Firebug on. Are the symptoms the same with Firebug off and on?

petermoulding.com/web_architect

petermoulding.com/web_architect

zvikico’s picture

zvikico commented

Thanks for the quick responses.

I'm with 6.8 now. I recently updated from 6.6 (didn't go through 6.7). It is clear that there are database updates pending - I can see them listed in the select updates page.

I tried with Firebug disabled and with Safari. I have a relatively small sites (less than 100 nodes, 2 users) so I don't believe it's a resource issue. If it is, where's the indication for that?

zvikico’s picture

zvikico commented

I'm still with this problem, I'm not sure that upgrading to 6.9 is a good idea at this point.

Anyone?

Mark_J’s picture

Mark_J commented

Have you tried installing XAMPP and Drupal 6.8 and then upgrading to 6.9? Do you still have to same problems?

How about installing Drupal 6.9 into a separate folder on your online server with a separate database - starting a fresh install. Does that work?

If Yes, delete your old 6.9 files and upload them again from the zip achieve and then try upgrading it.

If no, re-download the zip achieve and try again. May be it is a bad download?

Cheers,

zvikico’s picture

zvikico commented

Thanks for your response.

Sorry for not specifying this before - I'm running with Nginx and FascCGI, so I'm not going for XAMPP.

I recently updated from 6.6 to 6.8. I want to solve this issue before upgrading. I had the problem in 6.6 and carried it forward to 6.8, so I'm guessing it is not related to the drupal core files. It could be database related or configuration related.

R2-D8’s picture

R2-D8 commented

Hello everybody,

i am new to drupal so I don't know whether this solution will help others.

My system:
Multisite-drupal (2 sites) on debian (etch). No site uses default-site.

The Problem:
After upgrading from 6.8 to 6.9 one of my multisites had the same updating problem. (Why not both? - i really don't know)
Firebug was showing the "Access to restricted URI denied" error.

My solution:
After a while of research i realized that my debian-vhost-entries all got the www-prefix but drupal wasn't handling them.
Little later i figured out setting www-prefix at drupals .htaccess file and guess what...

... update is working fine now. :)

zvikico’s picture

zvikico commented

Thank you so much!

AFAIK the .htaccess files are Apache config files, thus not used by Nginx. But, I had the settings.php baseUrl set to example.com instead of www.example.com. Once I added the www-prefix it, I could execute the update smoothly.

Much appreciated.

Zviki

zetxek’s picture

zetxek commented

Changing the $base_url in settings.php worked for me too. I had not setted $base_url and I could access locally to the files, but not from outside my network, as drupal linked them to "http://local.ip/route/to/file.txt". Adding the $base_url made Drupal link correctly the files :)

daytripscanada’s picture

daytripscanada commented

This very same issue has been driving me nuts since 6.1. Finally at 6.9 I decided to figure it out. Thank's for the help. Adding www. to my $base_url fixed the issue.

jsquyres’s picture

jsquyres commented

+1 on this; changing my $base_url worked as well.

IMHO: this seems to be a bug in Drupal. Yes, it's a user-configuration error, but Drupal should *tell* you that rather than hanging indefinitely. This particular issue caused me many hours of tearing my hair out wondering why the 6.9->6.10 upgrade would hang in the database upgrade portion.