V9.0.2+ Howto make sure new GoLang fileserver is enabled?

Hi Seafile Community,

i just upgraded the server v8.0.8 > v9.0.2 and added in seafile.conf:

[fileserver]
use_go_fileserver = true

How can I make sure, this new golang fileserver is really enabled?

Is this what that is Link

If it’s a regular docker container just like seafile or mariadb you can just type sudo docker-compose ps in your seafile docker folder to see if it’s running.

Hey what does that do, I only heard about it now.

Thank you, i am runnig it currently on prem ubuntu 20.04 server without docker from source

I just got the following exception when downloading a ZIP File with “use_go_fileserver = true”, so it seems to enable it but there’s a bug. disable go fileserver, exception disappears. Maybe it makes sense to make a bugreport, will check the already open issues tomorrow on github.

2022-01-20 23:22:41,051 [ERROR] django.request:224 log_response Internal Server Error: /api/v2.1/query-zip-progress/
Traceback (most recent call last):
  File "/var/www/clients/client1/web1/private/seafile/seafile-server-9.0.2/seahub/thirdpart/django/core/handlers/exception.py", line 47, in inner
    response = get_response(request)
  File "/var/www/clients/client1/web1/private/seafile/seafile-server-9.0.2/seahub/thirdpart/django/core/handlers/base.py", line 181, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/var/www/clients/client1/web1/private/seafile/seafile-server-9.0.2/seahub/thirdpart/django/views/decorators/csrf.py", line 54, in wrapped_view
    return view_func(*args, **kwargs)
  File "/var/www/clients/client1/web1/private/seafile/seafile-server-9.0.2/seahub/thirdpart/django/views/generic/base.py", line 70, in view
    return self.dispatch(request, *args, **kwargs)
  File "/var/www/clients/client1/web1/private/seafile/seafile-server-9.0.2/seahub/thirdpart/rest_framework/views.py", line 505, in dispatch
    response = self.handle_exception(exc)
  File "/var/www/clients/client1/web1/private/seafile/seafile-server-9.0.2/seahub/thirdpart/rest_framework/views.py", line 465, in handle_exception
    self.raise_uncaught_exception(exc)
  File "/var/www/clients/client1/web1/private/seafile/seafile-server-9.0.2/seahub/thirdpart/rest_framework/views.py", line 476, in raise_uncaught_exception
    raise exc
  File "/var/www/clients/client1/web1/private/seafile/seafile-server-9.0.2/seahub/thirdpart/rest_framework/views.py", line 502, in dispatch
    response = handler(request, *args, **kwargs)
  File "/var/www/clients/client1/web1/private/seafile/seafile-server-9.0.2/seahub/seahub/api2/endpoints/query_zip_progress.py", line 38, in get
    return Response(json.loads(progress))
  File "/usr/lib/python3.8/json/__init__.py", line 341, in loads
    raise TypeError(f'the JSON object must be str, bytes or bytearray, '
TypeError: the JSON object must be str, bytes or bytearray, not NoneType

Edit: i see this issue is already discussed here Seafile community edition 9.0.2 is ready! - #4 by andresnnn

That just went flying over my head :slight_smile:

Isn’t there a fileserver.log file for the Go Fileserver in Seafile 9?

not found yet
edit: the fileserver.log includes Go messages, example: 2022/01/21 11:25:09 http: superfluous response.WriteHeader call from main.getBlockInfo (sync_api.go:755)

I also see a fileserver-error.log that’s new to me.