Seafile 8.05 (Docker) Server Hiccup

Hi,
we’ve been using seafile server 7 and upgraded it to Version 8
Now we periodically get 500 error from the server

Traceback (most recent call last):
  File "/opt/seafile/seafile-server-8.0.5/seahub/thirdpart/django/core/handlers/exception.py", line 34, in inner
    response = get_response(request)
  File "/opt/seafile/seafile-server-8.0.5/seahub/thirdpart/django/core/handlers/base.py", line 115, in _get_response
    response = self.process_exception_by_middleware(e, request)
  File "/opt/seafile/seafile-server-8.0.5/seahub/thirdpart/django/core/handlers/base.py", line 113, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/opt/seafile/seafile-server-8.0.5/seahub/thirdpart/django/views/decorators/csrf.py", line 54, in wrapped_view
    return view_func(*args, **kwargs)
  File "/opt/seafile/seafile-server-8.0.5/seahub/thirdpart/django/views/generic/base.py", line 71, in view
    return self.dispatch(request, *args, **kwargs)
  File "/opt/seafile/seafile-server-8.0.5/seahub/seahub/api2/base.py", line 23, in dispatch
    response = super(APIView, self).dispatch(*a, **kw)
  File "/opt/seafile/seafile-server-8.0.5/seahub/thirdpart/rest_framework/views.py", line 505, in dispatch
    response = self.handle_exception(exc)
  File "/opt/seafile/seafile-server-8.0.5/seahub/seahub/api2/base.py", line 20, in handle_exception
    return super(APIView, self).handle_exception(exc)
  File "/opt/seafile/seafile-server-8.0.5/seahub/thirdpart/rest_framework/views.py", line 465, in handle_exception
    self.raise_uncaught_exception(exc)
  File "/opt/seafile/seafile-server-8.0.5/seahub/thirdpart/rest_framework/views.py", line 476, in raise_uncaught_exception
    raise exc
  File "/opt/seafile/seafile-server-8.0.5/seahub/thirdpart/rest_framework/views.py", line 493, in dispatch
    self.initial(request, *args, **kwargs)
  File "/opt/seafile/seafile-server-8.0.5/seahub/thirdpart/rest_framework/views.py", line 410, in initial
    self.perform_authentication(request)
  File "/opt/seafile/seafile-server-8.0.5/seahub/thirdpart/rest_framework/views.py", line 324, in perform_authentication
    request.user
  File "/opt/seafile/seafile-server-8.0.5/seahub/thirdpart/rest_framework/request.py", line 220, in user
    self._authenticate()
  File "/opt/seafile/seafile-server-8.0.5/seahub/thirdpart/rest_framework/request.py", line 373, in _authenticate
    user_auth_tuple = authenticator.authenticate(self)
  File "/opt/seafile/seafile-server-8.0.5/seahub/seahub/api2/authentication.py", line 70, in authenticate
    return self.authenticate_v1(request, key)
  File "/opt/seafile/seafile-server-8.0.5/seahub/seahub/api2/authentication.py", line 79, in authenticate_v1
    user = User.objects.get(email=token.user)
  File "/opt/seafile/seafile-server-8.0.5/seahub/seahub/base/accounts.py", line 95, in get
    emailuser = ccnet_threaded_rpc.get_emailuser(email)
  File "/opt/seafile/seafile-server-8.0.5/seafile/lib64/python3.6/site-packages/pysearpc/client.py", line 126, in newfunc
    ret_str = self.call_remote_func_sync(fcall_str)
  File "/opt/seafile/seafile-server-8.0.5/seafile/lib64/python3.6/site-packages/pysearpc/named_pipe.py", line 101, in call_remote_func_sync
    ret_str = transport.send(self.service_name, fcall_str)
  File "/opt/seafile/seafile-server-8.0.5/seafile/lib64/python3.6/site-packages/pysearpc/named_pipe.py", line 62, in send
    sendall(self.pipe, header)
  File "/opt/seafile/seafile-server-8.0.5/seafile/lib64/python3.6/site-packages/pysearpc/utils.py", line 32, in sendall
    raise NetworkError('Failed to write to socket: %s' % e)
pysearpc.errors.NetworkError: Failed to write to socket: [Errno 32] Broken pipe

So, in the browser it looks like an error with “server hiccup” and if I refresh the page with “F5” - error is gone and seafile page loads correctly.

We soppose that this is the problem with jango cache or a bug in server version 8

P.S. server has been updated from Version 7 to Version 8

Thank you!

I also have the same problems.

Have you tried deleting seahub_cache in /tmp?