Recent Topics
  1. b2evolution CMS Support Forums
  2. b2evolution Support
  3. General Support
  4. Auto Upgrade Fails on 'Installer Script' Step

Auto Upgrade Fails on 'Installer Script' Step

1 Sep 30, 2015 20:44    

This is a bit of a minor niggle, as I can always install thing manually, however...

I've tried using the Auto Upgrade feature on each of the 6.6.x updates on my production blog, but they've always failed at the same point with (from memory) the same error message coming up (see screenshot in next post). It's not too obvious what's going wrong, and ideally I'd like it to work as cleanly as it does on my dev/test server, which works perfectly every time. Given that the production blog was first installed at something like v2.4.5, I was wondering whether there might be something in its long history that's making things less than seamless.

As I say though, it's not a big issue for me to do a standard upgrade, though it is rather more time-consuming, and prone to something getting missed. I don't have any customisations in my install as such, just an extra skin or two, and an 'images' folder sharing the b2evo install root that I use for other things.

Any clues as to what might be happening?

Back to top

3 30 Sep 2015 23:12

You definitely need to ask the server admin for the error log as the real error is not displayed on the screen.

It might be that you don't have enough memory... but in that case odds would be than manual upgrade wouldn't work either.

Is the error immediate or does it "load" for a little while before showing that error.

Another possibility is that the newly downloaded install script doesn't get a proper permission to be read by PHP...

Can you force an upgrade where you upgrade 6.6.4 to 6.6.4 and at this last step, check the file perms of the install/index.php script and try to change them to something more permissive, then reload the "error page" in the browser ?

Back to top

4 01 Oct 2015 19:10

@fplanque it looks like it may be a file permissions issue with the install folder when it's created during the auto-upgrade process. I'm in discussion with united-hosting at the moment, trying to work out what's going on, as otherwise, the file permissions on the blog look as I'd expect them to. It would seem rather odd that I'd end up needing to manually intervene on the file permissions during an auto-upgrade.

Back to top

5 02 Oct 2015 14:14

Please let me know if they somehow prevent PHP from executing the files it creates/updates and if there is something we can do about it.

Back to top

6 02 Oct 2015 14:34

Consider it done (as soon as you release the next b2evo)...

Back to top

7 02 Oct 2015 20:13

One other thought, one of the emails I had from UH suggested I needed to have 0755 permissions set on the folders and 0644 for the files. Whilst I didn't go through every folder as you might imagine, that was how things appeared to be set up.

Does the install routine require anything different than that?

Back to top

8 03 Oct 2015 00:17

The installer "only" requires that the files be readable and writable by PHP. What exact permissions this translates to depends on the server set up.

0755 and 0644 means only the file owner can write to it but everyone else can read them. So in your case I doubt the install script actually had 0644 at the time you got the error. But again you can check by resinstalling the same version over the same version.

http://b2evolution.net/man/directory-and-file-permissions

Back to top


Form is loading...