Can't upgrade from 11.0.6 to 11.0.8 - /seahub/media/avatars/*': No such file or directory

[maroon]

Hi,

i just tried to upgrade my docker seafile from 11.0.6 to 11.0.8 and got this error.

[upgrade]: The container was recreated, start fix the media symlinks
mv: cannot stat '/opt/seafile/seafile-server-11.0.6/seahub/media/avatars/*': No such file or directory
Traceback (most recent call last):
  File "/scripts/start.py", line 95, in <module>
    main()
  File "/scripts/start.py", line 61, in main
    check_upgrade()
  File "/scripts/upgrade.py", line 120, in check_upgrade
    fix_media_symlinks()
  File "/scripts/upgrade.py", line 104, in fix_media_symlinks
    call('mv -n %s/* %s' % (avatars_dir, dst_avatars_dir))
  File "/scripts/utils.py", line 70, in call
    return subprocess.check_call(*a, **kw)
  File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command 'mv -n /opt/seafile/seafile-server-11.0.6/seahub/media/avatars/* /shared/seafile/seahub-data/avatars' returned non-zero exit status 1.
*** Shutting down /scripts/enterpoint.sh (PID 25)...
*** Shutting down runit daemon (PID 24)...
*** Running /etc/my_init.post_shutdown.d/10_syslog-ng.shutdown...
*** Init system aborted.
*** Killing all processes...

what is the solution for the issue?

[maroon]

Fixed. While recreating the container its important to change the env entry to the right version. I think everyone will encounter this issue in some case. Is it possible to abandoned this flag?

[daniel.pan]

Which flag do you mean?

[maroon]

SEAFILE_VERSION env entry. Forgetting to update the version number during an update can lead to issues. In my opinion, this flag is unnecessary and can cause problems if users are unaware of the need to change it. The version should be hardcoded in the container depending on its version.

Edit: Sorry i meant entry not flag.

[mehlkopf]

Even though the flag might trigger this error, the root cause in my opinion is the very strange construction regarding the media / avatars folders. For me, it was easy to deploy Seafile in a Docker environment, but it was hours of work to find out why avatars were not displayed, and I have to manually re-copy files and correct folder permissions after every update. So I would strongly wish for a revision of whatever makes this so special in contrast to all other data/database storage.

Just a selection of years-long problems with avatars, which in my opinion should not at all be an isolated factor that could cause any trouble:

Seafile 10 Permission denied: 'default-non-register.jpg'

I’ll never understand why someone distributes all this non-working shit. Trying to setup Seafile 10 like explained in instructions. But setup-seafile-mysql.sh ends with: Error: Failed to prepare seahub avatars dir: [Errno 13] Permission denied: ‘default-non-register.jpg’

Seafile Docker upgrade from 8.0.7fails

Hi, Docker Seafile 8.0.7 is running fine. Upgrade to 8.0.7-1 runs fine. Upgrade to any later version (9.0.0, latest) fails with error messages in the container log. *** Running /etc/my_init.d/01_create_data_links.sh... *** Booting runit daemon... *** Runit started as PID 25 *** Running /scripts/enterpoint.sh... 2023-05-15 10:22:11 Waiting Nginx 2023-05-15 10:22:12 Nginx ready 2023-05-15 10:22:12 This is a idle script (infinite loop) to keep container running. [05/15/2023 10:22:12][upgrade…

[Docker] Missing/Broken avatar with seafile-mc:7.1.3

Hi, my avatar is broken and Chrome shows this in error in console. Failed to load resource: the server responded with a status of 403 () Hovewer, I can upload an avatar without any issue.

Avatars won't load on default docker installation

Hello, just installed Seafile 8.0.5 with the given docker-compose file found here: https://download.seafile.com/d/320e8adf90fa43ad8fee/files/?p=/docker/docker-compose.yml But the webinterface doesn’t load the avatar as seen here: [image] When I try to follow the URL mydomain.com/media/avatars/1/7/710a4bcff9eab8e1f93567a8e137cf/resized/72/77bafd21e249c6fd17c4ff809c37b4b8.png I get a 403 error. Does anyone know how to fix this? Thanks in advance! EDIT: In the meantime I was able to solve t…

Avatar + CSS + media problems

So I managed to setup seafile 7.1.4 via docker and after logging in I see a broken image instead of my avatar. Google chrome reveals: failed to load SourceMap: Could not load content for https://mydomain.tld/media/css/seafile-ui.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE so I enter the docker container and check: docker exec -ti seafile bash cat /etc/nginx/sites-enabled/seafile.nginx.conf shows location /media { root /opt/seafile/seafile-server-latest/seahub; …

Seahub: Avatar location / failure - Apache / Ubuntu / Community Manual

Good evening, I would appreciate some help; installed Seafile this evening and some minor problem. All is installed and working fine except the Avatar in my profile on Seahub. On my Settings page, it shows as a broken image. If I click on it and select a replacement file to upload, I get “Internal Server Error”. The Seahub log file says: 2019-07-10 00:30:37,513 [WARNING] django.request:152 get_response Not Found: /media/avatars/default.png 2019-07-10 00:30:47,671 [WARNING] django.request:15…

Avatars do not work in Seafile CE 7.0.0

When loading up an avatar, the picture does not load. When checking the URL of the image it is trying to load, it’s “http://127.0.0.1:8000/media/avatars…” as opposed to the proper address it is supposed to be. When looking avatars in CE 6.3.4, it works properly. It looks like Seahub is failing to fill in the proper HTTP URL for the avatar image.