-
-
Notifications
You must be signed in to change notification settings - Fork 4.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
[Bug]: After upgrade to 28.0.1 nonstop errors regarding guestName avatar #42858
Comments
I think server/lib/private/Contacts/ContactsMenu/ContactsStore.php Lines 341 to 345 in 23a7f8c
The route expects guestName to have a value: Line 56 in 23a7f8c
I suspect it'll go away if you change EDIT: Might be a couple other spots where the use of |
Any idea on the underlying cause? Is this related to LDAP auth? Is this an actual bug? Maybe a combination of the two? I just don't understand why it is pulling a guest avatar from an LDAP authenticated user. This is flooding my logs as an error and I guess 28 keeps an error in log count that doesn't go away for a week. Otherwise everything is functional but I really would like to know what this is related to. I mean with my limited knowledge it almost looks as though it is first searching the local system side for avatars but then not finding it and then snatching the avatar from LDAP (which the server has) and plugging it in so LDAP users have avatars. Maybe I am wrong though. |
Outside of making that area of code noted a bit more robust to empty name fields that reach it? No. Well, I suppose having guest users with empty name fields. :-)
Not sure. Handling of empty name fields at this point in the code could be more robust. That would eliminate the error you're seeing, but unclear whether it's expected that you have guest users with empty name fields in your environment. :-)
This area of code looks to be generating the contacts menu, so it's looking up everyone's avatars - including for any guests you have added - and not just the currently authenticated user's avatar. It doesn't sound like you've experienced any other symptoms, so that's a good sign.
What version of Nextcloud did you upgrade from? EDIT: Didn't mean to close. |
I created a test guest user a while back just for testing but then deleted the user. That was quite a while ago. This issue happened both when enabled and disabled. I actually disabled it at the time because I was suspecting that may possibly have been the cause. I went from 27 (latest forgot exact version) to 28.0.1. Is there a way to possibly hunt down remnants of guest users in the db and possibly remove them or from occ to check that? Maybe it's just something lingering in the db? |
sudo -u www-data php --define apc.enable_cli=1 /var/www/cloud.domain.tld/occ guests:listNo guests created I'm guessing because no guests exist. |
Fixes #42858 and makes things more robust Signed-off-by: Josh <josh.t.richards@gmail.com>
I applied the changes manually and so far no errors in the log (which would pop up on any access to anything in the web ui). After truncating the Nextcloud log I now have a green checkmark in the admin page. I will keep an eye on it but it seems fixed. |
No, an upstream dependency changed exit code requirements. Fix pending in nextcloud/guests#1101 |
Fixes #42858 and makes things more robust Signed-off-by: Josh <josh.t.richards@gmail.com>
The other matter fixed in nextcloud/guests#1102 and will be in the next release. |
Bug description
After upgrading I noticed that the nextcloud administration status page showed errors that were constantly counting up. Looking at the logs (had to disable ad blocker to see them for some reason) It was showing the following error...
InvalidParameterException
Parameter "guestName" for route "core.GuestAvatar.getAvatar" must match "[^/]++" ("" given) to generate a corresponding URL.
I am not really sure where to look here. Maybe it is related to auth against ldap? I haven't been able to find any more information about it.
Steps to reproduce
Just run nextcloud and it will constantly log this.
Expected behavior
To not have this error.
Installation method
Community Manual installation with Archive
Nextcloud Server version
28
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.2
Web server
Apache (supported)
Database engine version
MySQL
Is this bug present after an update or on a fresh install?
Upgraded to a MAJOR version (ex. 22 to 23)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: