-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Update to NC 19.0.1: Internal server error after login #21885
Comments
Info: downgraded back to NC 19.0.0.12, and NC works again without internal server error. |
Same issue;
That code block was added in 5ebb535; commenting it out seems to be a workaround. I am able to browse groups, in the admin UI once I've logged in, so I am not sure why the error is thrown on login. |
thank you so much, workaround worked. |
Is it specifically line 444 that you commented out? I tried this and it didn't seem to work for me. It would be helpful if you could be more specific about what you commented out, as there are multiple things listed in the commit. |
No, it was the cache check code block. I'm not sure if the group cache is
not yet populated when it runs, or if the group cache itself is broken, as
I'm not familiar with the code base. I commented out lines 443-445.
Beware that this will skip use of the cache entirely for and might have
apreformance penalty. Caveat emptor.
…On Mon, Jul 20, 2020, 21:00 RolandiXor ***@***.***> wrote:
Is it specifically line 444 that you commented out? I tried this and it
didn't seem to work for me.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#21885 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACON7ON6LB3DRRA6OH2UPHDR4TSCLANCNFSM4O5K76YQ>
.
|
Same issue here, upgrading from 18.0.8 to 19.0.2. Commenting the three lines in |
instead of commenting it out, you can also handle the null value of displayname like this:
|
We have the same Problem. NC 19.0.2 and LDAP backend. However, until now I only got one user not working the rest (~100) have not complained. As we are using an AD as LDAP backend and there are no displaynames set on any groups I am not sure what makes this user different. |
I can confirm that problem still exists in 19.0.2 (pure local user storage). |
I can also confirm that the Problem still exists in 19.0.3 and the comment from dh-connect works as a fix with that version also. |
I have three instances of NC running, all on Debian/Apache. This is happening on just one of the instances. I'm trying to upgrade to 19.03 from 18.9. Success on two instances, but failed with this error on one. I have noticed that error message below gives the Here's the error formatted for easier reading.
|
No further movement on fixing this? |
Signed-off-by: tgrant <tom.grant760@gmail.com>
Still ended up with this issue in 20.0.0 |
Same here, I had to go back to NC 18 as I got the Internal Server Error message, even after patching the |
Just updated to 19.0.5. Still the same problem. |
Updated to 20.0.4 - still same issue, now internal error appears when switching to user settings, wonder why this is still not being fixed. |
I stopped trying to upgrade because of this. Instead, I'm going to try to backup and migrate when I get the chance. That may be the only solution. As for support, IMHO, forget about it. |
Hello all. We upgraded our infrastructure on sunday from 18.0.12 to 19.0.6 with the same error. Following fix has solved the issue:
Is there any update on this? |
We have found a workaround (this may help triage the problem): |
Issue is still present in 20.0.4. Haven't yet searched how the groupcache is wrongly populated. |
Also with 20.0.5 ... maybe someone cares about checking that? the oc_ldap_group_mapping table has the owncloud_name the same as the CN, but cn is all lower case, and owncloud_name is correctly typed (i.e. mixed case) For me it seems to always affect only a single user at a time so far. |
Seems that it's also the same with 20.0.6 |
So I just solved the problem for me by deleting some records of users in the oc_group_user table, whose groups I had actually deleted in the frontend some time ago. But the records of the users associated with the groups were still there in the database and thus probably triggered the problem after each update. |
thank you for the hint, I did the same, had users assigned to a group GID "users", but in table oc_groups is no GID "users", tried it out without the fix and it works now, so guess the issue was a GID used that's not in the oc_groups table |
List user/group combinations with non-existing group: SELECT oc_group_user.* FROM oc_group_user LEFT JOIN oc_groups ON oc_group_user.gid=oc_groups.gid WHERE oc_groups.gid IS NULL; Remove user/group combinations with non-existing group: DELETE oc_group_user FROM oc_group_user LEFT JOIN oc_groups ON oc_group_user.gid=oc_groups.gid WHERE oc_groups.gid IS NULL; |
@robinelfrink @soerpoers |
Signed-off-by: tgrant <tom.grant760@gmail.com>
Fix null displayname crash as described in #21885
Looks like this was fixed with #23065 |
Signed-off-by: tgrant <tom.grant760@gmail.com>
Signed-off-by: tgrant <tom.grant760@gmail.com>
[stable20] Fix null displayname crash as described in #21885
[stable21] Fix null displayname crash as described in #21885
Steps to reproduce
Expected behaviour
after successful login switch to files
Actual behaviour
internal server error
Server configuration
Operating system: linux debian 10 buster
Web server: Apache 2.4.38
Database: MariaDB 10.3.22
PHP version: 7.4.8
Nextcloud version: 19.0.1
Updated from an older Nextcloud/ownCloud or fresh install: update from 19.0.0
Where did you install Nextcloud from: web installer
Signing status:
Signing status
List of activated apps:
App list
Nextcloud configuration:
Config report
Are you using external storage, if yes which one: smb
Are you using encryption: no
Are you using an external user-backend, if yes which one: no
LDAP configuration (delete this part if not used)
LDAP config
Client configuration
Browser:
Operating system:
Logs
Web server error log
Web server error log
Nextcloud log (data/nextcloud.log)
Nextcloud log
Browser log
Browser log
The text was updated successfully, but these errors were encountered: