Mysql partition was full => all clients unsynced, links admin broken for some users

Hi all,

today mysql run out of disk space. I enlarged the disk and restarted mysql and the seafile/seahub services.

apparently this corrupted quite a few things:

  1. all libraries on all clients have been unsynced (which is very unfortunate, but can be solved by the users)

  2. at least one user cannot access the links in the share-admin. the error I see is:

May 5 16:32:52 filipe 2022-05-05 16:32:52,082 [ERROR] django.request:135 handle_uncaught_exception Internal Server Error: /api/v2.1/admin/users/avi@ifi.uzh.ch/share-links/#012Traceback (most recent call last):#012 File “/srv/seafile/seafile-pro-server-7.1.7/seahub/thirdpart/django/core/handlers/exception.py”, line 41, in inner#012 response = get_response(request)#012 File “/srv/seafile/seafile-pro-server-7.1.7/seahub/thirdpart/django/core/handlers/base.py”, line 249, in _legacy_get_response#012 response = self._get_response(request)#012 File “/srv/seafile/seafile-pro-server-7.1.7/seahub/thirdpart/django/core/handlers/base.py”, line 187, in _get_response#012 response = self.process_exception_by_middleware(e, request)#012 File “/srv/seafile/seafile-pro-server-7.1.7/seahub/thirdpart/django/core/handlers/base.py”, line 185, in _get_response#012 response = wrapped_callback(request, *callback_args, **callback_kwargs)#012 File “/srv/seafile/seafile-pro-server-7.1.7/seahub/thirdpart/django/views/decorators/csrf.py”, line 58, in wrapped_view#012 return view_func(*args, **kwargs)#012 File “/srv/seafile/seafile-pro-server-7.1.7/seahub/thirdpart/django/views/generic/base.py”, line 68, in view#012 return self.dispatch(request, *args, **kwargs)#012 File “/srv/seafile/seafile-pro-server-7.1.7/seahub/thirdpart/rest_framework/views.py”, line 505, in dispatch#012 response = self.handle_exception(exc)#012 File “/srv/seafile/seafile-pro-server-7.1.7/seahub/thirdpart/rest_framework/views.py”, line 465, in handle_exception#012 self.raise_uncaught_exception(exc)#012 File “/srv/seafile/seafile-pro-server-7.1.7/seahub/thirdpart/rest_framework/views.py”, line 476, in raise_uncaught_exception#012 raise exc#012 File “/srv/seafile/seafile-pro-server-7.1.7/seahub/thirdpart/rest_framework/views.py”, line 502, in dispatch#012 response = handler(request, *args, **kwargs)#012 File “/srv/seafile/seafile-pro-server-7.1.7/seahub/seahub/api2/endpoints/admin/users.py”, line 1122, in get#012 link_info = get_user_share_link_info(fs)#012 File “/srv/seafile/seafile-pro-server-7.1.7/seahub/seahub/api2/endpoints/admin/users.py”, line 115, in get_user_share_link_info#012 repo.version, obj_id)#012 File “/srv/seafile/seafile-pro-server-7.1.7/seafile/lib/python3.6/site-packages/seaserv/api.py”, line 212, in get_file_size#012 return seafserv_threaded_rpc.get_file_size(store_id, version, file_id)#012 File “/srv/seafile/seafile-pro-server-7.1.7/seafile/lib/python3.6/site-packages/pysearpc/client.py”, line 128, in newfunc#012 return fret(ret_str)#012 File “/srv/seafile/seafile-pro-server-7.1.7/seafile/lib/python3.6/site-packages/pysearpc/client.py”, line 12, in _fret_int#012 raise SearpcError(dicts[‘err_msg’])#012pysearpc.common.SearpcError: Invalid file id

does anybody know how this can be fixed?

we are using seafile pro 7.17 on debian 11, mariadb 10.3

best,
Hp

ok, the problem with the link admin page is apparently older, the user just reported it today. but still it would be nice to fix it.

The first problem should have already fixed in the latest 8.1 or 9.0 version.

Can you upgrade to 8.1 or 9.0 to check if the second problem still there?