Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updater fails to update to 5.0.11 (unable to move ...) #4857

Closed
RandolfCarter opened this issue Sep 15, 2013 · 13 comments
Closed

Updater fails to update to 5.0.11 (unable to move ...) #4857

RandolfCarter opened this issue Sep 15, 2013 · 13 comments
Labels

Comments

@RandolfCarter
Copy link
Contributor

Expected behaviour

The updater updates ownCloud from 5.0.10 to 5.0.11

Actual behaviour

The updater stops in the middle of the process and reports:
Update failed Please fix this and retry.

Steps to reproduce

  1. Apply the updater workaround to make the 5.0.11 update show up (http://mail.kde.org/pipermail/owncloud/2013-September/010583.html)
  2. Go to the "Update Center"
  3. Click on Update
  4. The updater will show this:
ownCloud 5.0.11 is available. Get more information  
Checking your installation...
Downloading package...
Creating backup...
Here is your backup: /[edited]/data/updater_backup/5.0.17-32f04baa.zip
Moving files...
Update failed

Please fix this and retry.

The update was unsuccessful. Please report this issue to the ownCloud
community.

I already reported this here: http://mail.kde.org/pipermail/owncloud/2013-September/010601.html
There was also somebody else reporting this in the forum: http://forum.owncloud.org/viewtopic.php?f=23&t=15787&p=41304#p41300

Checking the log (see below), at least in my case this seems to be related to the Updater being unable to move files.

Server configuration

Operating system: Ubuntu Server 12.04 (64 bit)
Web server: Apache 2.2.22
Database: MySQL 14.14 Distrib 5.5.32
PHP version: 5.4.13
ownCloud version: 5.0.11

Client configuration

Browser: Firefox 23
Operating system: Ubuntu 13.04

Logs

Web server error log

Nothing relevant, as far as I can tell

ownCloud log (data/owncloud.log)

{"app":"updater","message":"Something went wrong for 3rdparty. Rolling back.","level":3,"time":"2013-09-13T20:36:11+00:00"}
{"app":"updater","message":"Unable to move \/www\/owncloud\/3rdparty\/Archive to \/media\/data\/owncloud\/data\/updater_backup\/tmp\/3rdparty\/Archive","level":3,"time":"2013-09-13T20:36:11+00:00"}

It seems like the updater has the same problems to move data here which also caused a blank page in the Update center for me (see also here: http://mail.kde.org/pipermail/owncloud/2013-September/010585.html).
I double- and triple-checked the permissions and ownership. I definitely don't have any security extensions installed.
I checked to do some moving like this as www-data user from the command line, and that also works without problems (sudo -u www-data mv /www/owncloud/something /media/data/owncloud/data/).

So the updater seems to have some weird problems moving files/folders...

@gfr
Copy link

gfr commented Oct 6, 2013

I think this problem is caused by open-basedir settings. I had the same problem because /media/data/owncloud/data/ is not on the open-basedir-path. Replacing the absolute path to the data-dir in the config.php with a relative path + symlink in the owncloud-directory fixed the problem for me.

@TwoPhased
Copy link

Thank you for you answer!
However, i'm not quite sure what you mean by "replacing the absolute path to the datadir with a relative path + symlink"
Could you give me an example.
In defence of my stupidity, I'm both Dutch and a noob.

Regards,
TwoPhased

Op 6 okt. 2013 om 11:45 heeft gfr [email protected] het volgende geschreven:

I think this problem is caused by open-basedir settings. I had the same problem because /media/data/owncloud/data/ is not on the open-basedir-path. Replacing the absolute path to the data-dir in the config.php with a relative path + symlink in the owncloud-directory fixed the problem for me.


Reply to this email directly or view it on GitHub.

@TwoPhased
Copy link

Is this what you mean, or did I take things to literary?

/home/username/www/owncloud/data -> /mnt/wd120/data

Op 6 okt. 2013 om 11:45 heeft gfr [email protected] het volgende geschreven:

I think this problem is caused by open-basedir settings. I had the same problem because /media/data/owncloud/data/ is not on the open-basedir-path. Replacing the absolute path to the data-dir in the config.php with a relative path + symlink in the owncloud-directory fixed the problem for me.


Reply to this email directly or view it on GitHub.

@gfr
Copy link

gfr commented Oct 6, 2013

Looks alright. I also had an absolute path in my config.php -> "/data/owncloud/". Now I have "data/" because the symlink named "data" points to "/data/owncloud/.

@TwoPhased
Copy link

Ok, seems to work! I changed data-dir from /mnt/wd120/data to plain data/, and so far I have been able to see the content of my owncloud in my browser. However, after doing a update/upgrade, I saw a newer oc update 5.0.12 flashing by, but that was before I changed the path in the config.php

Is there a way to re-invoke the oc 5.0.12 update/upgrade? I run ubuntu server 12.04.1 I'd hate to do it manually.

Peace!
TwoPhased

Op 6 okt. 2013 om 14:06 heeft gfr [email protected] het volgende geschreven:

Looks alright. I also had an absolute path in my config.php -> "/data/owncloud/". Now I have "data/" because the symlink named "data" points to "/data/owncloud/.


Reply to this email directly or view it on GitHub.

@Octopus2
Copy link

I have the same Problem since 5.0.11
@VicDeo : Is there any news on this?

@karlitschek
Copy link
Contributor

@VicDeo What do you think?

@VicDeo
Copy link
Member

VicDeo commented Nov 13, 2013

@karlitschek initial report was caused by open-basedir settings and resolved by symlinking data-dir.
@Octopus2 what's in the log on admin page when the updater report about a failure?

@RandolfCarter
Copy link
Contributor Author

@VicDeo If by initial report you mean me, then no, i have no open_basedir setting active...

Unfortunately I cannot test this again at the moment because of the extraction error problem (#5795)

@Octopus2
Copy link

@VicDeo This is what is shown on the admin page:

Warning core    starting upgrade from 5.0.20 to 5.0.22  2013-10-21T21:06:22+00:00
Error   updater Unable to move /srv/www/htdocs/web3/html/owncloud/data/updater_backup/5.0.22/apps/files_archive to /srv/www/htdocs/web3/html/owncloud/apps/files_archive    2013-10-21T20:30:54+00:00
Error   updater Something went wrong for apps. Rolling back.    2013-10-21T20:30:53+00:00

php-Version: 5.3.26 / open_basedir: no value

Supplement: Autoupdate to 5.0.12 and 5.0.13 had the same problem.
Manual update works without problems.
Updater before 5.0.10 worked without problems!

@karlitschek
Copy link
Contributor

@VicDeo Any idea?
The update should detect if the upgrade i not possible because of open_basedir for example.

@VicDeo
Copy link
Member

VicDeo commented Nov 29, 2013

@Octopus2 remove apps/files_archive files. it is no longer supported with oC5 anyway

@VicDeo
Copy link
Member

VicDeo commented Jan 31, 2014

Duplicate of owncloud-archive/apps#1561

@VicDeo VicDeo closed this as completed Jan 31, 2014
@lock lock bot locked as resolved and limited conversation to collaborators Aug 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

6 participants