XF 2.3 2.3.2 upgrade error - not writable

[briansol]

Never seen this one before... going from 2.3.0 to 2.3.2


install/oc-upgrader.php

Oops! We ran into some problems.​

Not all files are writable. Please upgrade manually.


Upgraded to 2.3.0 just fine, and certainly haven't chmodd'ed anything since.

also, it would be great if it said which file is not writable...

 

[ekool]

Can you just chown -R and chmod -R the files and re-try it again?

 

[briansol]

the thing is, i don't see anything not in proper order and i'm not about to just recursively mess with permissions that have worked for years including 2.3.0 because of this.

 

[briansol]

Also, 0 results

[18:01][xxxxx@my.com public]# find . ! -perm -o=r
[18:01][xxxx@my.com public]#


[18:01][xxxxx@my.com public]find . ! -readable
[18:01][xxxx@my.com public]#


[18:01][xxxxx@my.com public]find . ! -writable
[18:01][xxxx@my.com public]#

 

[ekool]

Also, 0 results

[18:01][xxxxx@my.com public]# find . ! -perm -o=r
[18:01][xxxx@my.com public]#


[18:01][xxxxx@my.com public]find . ! -readable
[18:01][xxxx@my.com public]#


[18:01][xxxxx@my.com public]find . ! -writable
[18:01][xxxx@my.com public]#

Are you running that as root? If so, that won't really tell you what the web server can't write to. Guess it depends on how your hosting is setup. But on centminmod for example, that wouldn't tell you anything

 

[eva2000]

the thing is, i don't see anything not in proper order and i'm not about to just recursively mess with permissions that have worked for years including 2.3.0 because of this.

If on Centmin Mod, there's a tools/backup-perm.sh script which can allow you to backup all your file/directory permissions as well as restore from backup file all file/directory permissions as well as inspect the backed up permissions for clues as well. See https://community.centminmod.com/th...kup-restore-file-directory-permissions.10633/

 

[briansol]

So i upgraded manually (Ftp, go in to /install) and it ran fine, except, i'm stuck with


So, i'm guessing the install/ process could not remove the lock file either.

not sure what the heck is going on here...

 

[CedricV]

And can you enter the ACP?

 

[briansol]

i ran /install/ again (said there was nothing to upgrade) and suddenly it's open again.

The legacy file cleaner failed too. had to run
php cmd.php xf:file-clean-up XF

manually at the command line. Not sure what happened to my file system. all this has worked fine up until 2.3.2

 

[AWS]

I had the same errors. I run Windows 2022 DC. I been running with a Windows version of PHP chroot for years. After upgrading to 2.3.2 I got permission errors. The index page would not load. Only way to access the forum was by adding /forums to url. It was like the index page was non existent. I had to remove the chroot and give more permissions than I am comfortable with to get the site operational.

The other sites on 2.3.0 are fine.I won't upgrade them until I find the problem.

 

[javakhir]

2.2.16 upgrade to 2.3.2 showed the same error, not writeable
only thing I did change PHP version,
did use ftp to upload update, after upload, once again checked online update from acp, went normal & fast