Open ole-db opened 5 years ago
Same problem on Ubuntu 18.04.5 LTS
2020-12-15 11:58:41,094 [ERROR] django.request:135 handle_uncaught_exception Internal Server Error: /api/v2.1/admin/users/markov7722@gmail.com/share-links/
Traceback (most recent call last):
File "/opt/seafile/seafile-server-7.1.5/seahub/thirdpart/django/core/handlers/exception.py", line 41, in inner
response = get_response(request)
File "/opt/seafile/seafile-server-7.1.5/seahub/thirdpart/django/core/handlers/base.py", line 249, in _legacy_get_response
response = self._get_response(request)
File "/opt/seafile/seafile-server-7.1.5/seahub/thirdpart/django/core/handlers/base.py", line 187, in _get_response
response = self.process_exception_by_middleware(e, request)
File "/opt/seafile/seafile-server-7.1.5/seahub/thirdpart/django/core/handlers/base.py", line 185, in _get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/opt/seafile/seafile-server-7.1.5/seahub/thirdpart/django/views/decorators/csrf.py", line 58, in wrapped_view
return view_func(*args, **kwargs)
File "/opt/seafile/seafile-server-7.1.5/seahub/thirdpart/django/views/generic/base.py", line 68, in view
return self.dispatch(request, *args, **kwargs)
File "/opt/seafile/seafile-server-7.1.5/seahub/thirdpart/rest_framework/views.py", line 505, in dispatch
response = self.handle_exception(exc)
File "/opt/seafile/seafile-server-7.1.5/seahub/thirdpart/rest_framework/views.py", line 465, in handle_exception
self.raise_uncaught_exception(exc)
File "/opt/seafile/seafile-server-7.1.5/seahub/thirdpart/rest_framework/views.py", line 476, in raise_uncaught_exception
raise exc
File "/opt/seafile/seafile-server-7.1.5/seahub/thirdpart/rest_framework/views.py", line 502, in dispatch
response = handler(request, *args, **kwargs)
File "/opt/seafile/seafile-server-7.1.5/seahub/seahub/api2/endpoints/admin/users.py", line 1122, in get
link_info = get_user_share_link_info(fs)
File "/opt/seafile/seafile-server-7.1.5/seahub/seahub/api2/endpoints/admin/users.py", line 115, in get_user_share_link_info
repo.version, obj_id)
File "/opt/seafile/seafile-server-7.1.5/seafile/lib64/python3.6/site-packages/seaserv/api.py", line 192, in get_file_size
return seafserv_threaded_rpc.get_file_size(store_id, version, file_id)
File "/opt/seafile/seafile-server-7.1.5/seafile/lib64/python3.6/site-packages/pysearpc/client.py", line 128, in newfunc
return fret(ret_str)
File "/opt/seafile/seafile-server-7.1.5/seafile/lib64/python3.6/site-packages/pysearpc/client.py", line 12, in _fret_int
raise SearpcError(dicts['err_msg'])
pysearpc.common.SearpcError: Invalid file id
The library is OK.
sudo -u seafile ionice -c3 /opt/seafile/seafile-server-latest/seaf-fsck.sh 4a12f556-3d34-42b5-95f2-7b8d06e500ca
Starting seaf-fsck, please wait ...
[12/15/20 12:16:04] fsck.c(592): Running fsck for repo 4a12f556-3d34-42b5-95f2-7b8d06e500ca.
[12/15/20 12:16:04] fsck.c(418): Checking file system integrity of repo Документы(4a12f556)...
[12/15/20 12:17:32] fsck.c(656): Fsck finished for repo 4a12f556.
seaf-fsck run done
Same problem with 8.0.2.
Log file with errors attached. 2021-01-18 is when the problem occured. seahub.zip
I resolved a problem by removing a Library, creating a new one and reuploading all files.
After upgrading Seafile/Seahub from 6.3 to 7.0 I can't create share-links with seahub any more. With the client, there is no problem.
This is from the seahub.log:
I am running FreeBSD 11.2 and seafile/seahub is installed from the prorts.
I posted originally here: https://github.com/haiwen/seafile/issues/2246