-
Notifications
You must be signed in to change notification settings - Fork 10.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
RC bug: FileSystem Avatars not available #7172
Comments
before with that said, are you saying you cannot change the file uploads storage type option from |
Okay: So the option where to store the avatars is currently remaining in the admin panel but has no influence on the storage as it is set by the main storage settings? So the deprecated menu is confusing. When upgrading to the rc the avatars are not migrated. Is there a way to do a automatic migration instead of forcing the users to reupload their images? They are saved in the same cryptic version as ordinary uploads in e.g. uploads/guTGt472jjHldth instead of avatars/username? And emojis get the same change? |
After upgrading from 0.55.1-rcX to 0.57.1-rc1 all of our avatars and files now return 404. Avatar storage type is (was) FileSystem. After upgrade, it's still FileSystem for both, but actual avatars/files do not load. |
Had the same problem as @Majkl578 so I guess the migration isn't working properly. Avatars were stored in gridFS, other images on disk. |
For me they are simply reset to the colored letters. |
Same here for avatars, altough they still exist physically in original location. |
My logs are full with this since 0.57.0-rc1, is it related to this problem?
|
It seems this LDAP avatar sync problem also breaks the LDAP authentication and login. |
same here with ldap enabled and filesystem for avatar and file uploads. please fix. we have over a 100gb of files. |
@sampaiodiego is working on this: #7352 |
@soundstorm thx for referecing it. so #7352 should have fixed most of the problems with avatar migration, but unfortunately it does not repair broken migrations already ran. 😞 looks like your rocket.chat is on an undesired state.. so let me ask: are avatar files still on the old configured path? what is your configured file upload storage type (regular files not avatar)? |
Confirmed with RC3, avatars still missing. |
@Majkl578 as I said since you have said the original files are still on the old location, can you please confirm if you still have the old configs on your database? please run the following on mongo shell: db['rocketchat_settings'].find({
_id: { $in: ['Accounts_AvatarStoreType', 'Accounts_AvatarStorePath'] }
}); |
|
So you released stable version without actually fixing this... Good job. |
It looks to be fixed in the next minor release. Instead of being rude and unappreciative, try and add something constructive. |
Well, I did right in the previous post. I posted the settings I was asked for (for which I had to google how to execute query in mongo etc.) and it was left without any response - can't do more as I don't code in Node/JS. So now what's being rude... |
@Majkl578 this is why we strongly caution moving production systems to release candidates. They are unfinished and often contain bugs. In this case for people coming directly from 0.56.0 to 0.57.0 it seems to work fine. This is why a release went on out. Its cases where someone tried out 0.57.0-rc.1 / 0.57.0-rc.2 that we're having to work through |
We have a copy of our production system that went directly from 0.56 -> 0.57 (never installed a release candidate) and has this same issue with LDAP avatars. Logins are also broken until the "Sync User Avatar" option is set to false. Is there a manual query or other work around we can use to fix the issue? |
@sampaiodiego I made the mistake to go from 0.56.0 to 0.57-rc1 with a prod system with 280 users and in use 24 hrs a day. I'm still running 0.57-rc1. So doing any test other than applying a working fix is currently not possible, unfortunately. Is there anything else I can do which won't require downtime and possibly won't break anything else? Thank you! |
@Scream85 we just released a patch last night which should fix any avatar issue caused either by an if you were using file system as your avatar storage option, you have to set an environmente variable @Majkl578 we're sorry for that.. please update your server to |
Installed 0.57.1 on a test machine with a snapshot of the mongo database from when 0.56 was installed and ldap avatars are still missing. |
@sampaiodiego worked for me - at least for FS migration. Seems like LDAP is another construction side? |
yes @soundstorm , LDAP is a different issue. thx |
Rocket.Chat Version: 0.57.0.rc-1
Running Instances: 1
Probably this issue exists because of #6788 ?
We used FileSystem as storage type, but it seems that the storage engine was changed to GridFS. Doesn't matter if I switch between both, if I upload a new avatar the file date doesn't alter, so the storage type defaults to GridFS and is not changeable.
The text was updated successfully, but these errors were encountered: