-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Upgrade to 9.1 fails on Remove shares of a users root folder #25621
Comments
This is a similar error to issue #25535 |
Reformatting exception for readability:
|
From reading the stack trace it looks like this user has never logged in and the cleanup routine's init code |
@owncloud/sharing any idea ? |
Apparently this is an issue with @nextcloud/server as well during the upgrade. I wonder @PVince81 if this has anything to do with a LDAP user that hasn't logged in yet. Will have to look into this. |
Could not reproduce this issue even with LDAP users who never logged in. |
@compuguy mind sharing your LDAP config |
@PVince81 I had a user that reported the same issue, but it disappeared with the 2nd run of the upgrade. |
@PVince81 I'm no longer working for the company for which the nextcloud/owncloud instance had a issue with. You can try to contact @JamesonFinney about this issue for more information. |
Closing this for now, unless we get more detailed information to reproduce this. |
Same issue here. No LDAP. Fresh docker container from official image. I logged in as admin, changed account password, created a new user, logged out, tried to login on a new account and got "Internal server error message". I can still login as admin. Error in logs:
I also did Formatted traceback:
Image version: 9.1.4 |
OK, I just realized there's a new version available. This is what I've done:
Result: exactly the same problem, except that I cannot login even on admin account (first login after container start). Maybe Docker image is the problem here? |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Steps to reproduce
2/246 InvalidArgumentException: $absolutePath must be relative to "files"
Update failed
Maintenance mode is kept active
Reset log level
Expected behaviour: Upgrade succeeds
Actual behavior: errors out with InvalidArgumentException (see step 3 for exact error).
Operating System: Ubuntu 14.04.4
Web server: apache 2.4.7 (Ubuntu)
Database: Mysql 5.5.50-0-ubuntu0.14.04.1
owncloud version: 9.1
Attempted update from 9.0.3
Installed owncloud via official ubuntu 14.04 repo on owncloud site
Cant check signing status because owncloud in maintenance mode
List of activated apps:
activity 2.3.2
comments: 0.3.0
dav: 0.2.5
encryption: 1.3.0
federatedfilesharing: 0.3.0
federation: 0.1.0
files: 1.5.1
files_external: 0.6.0
files_pdfviewer: 0.8.1
files_sharing: 0.10.0
files_texteditor: 2.1
files_trashbin: 0.9.0
files_versions: 1.3.0
files_videoplayer:0.9.8
firstrunwizard: 1.1
gallery: 15.0.0
notifications: 0.3.0
provisioning_api: 0.5.0
systemtags: 0.3.0
templateeditor: 0.1
updatenotification: 0.2.1
user_ldap: 0.9.0
Ussing external storage: local
Not using encryption
LDAP backend in use will post redacted config later
Owncloud output:
The text was updated successfully, but these errors were encountered: