Seahub problems after upgrading 8.0.17 to 9.05

Seafile Server
1

Hey all,

after Upgrading 8.017 pro to 9.05 pro, seahub starts, but when accessing the Webinterface (DEBUG: true), I get the following message, any idea what went wrong?

ImproperlyConfigured at /

Error importing authentication backend seahub_extra.django_cas_ng.backends: “No module named ‘seahub_extra’”
Request Method: GET
Request URL: 127.0.0.1:8000/
Django Version: 3.2.6
Exception Type: ImproperlyConfigured
Exception Value:
Error importing authentication backend seahub_extra.django_cas_ng.backends: “No module named ‘seahub_extra’”
Exception Location: /home/seafile/seafile-pro-server-9.0.5/seahub/seahub/auth/init.py, line 23, in load_backend
Python Executable: /usr/bin/python3
Python Version: 3.6.8
Python Path:
[’/home/seafile/seafile-pro-server-9.0.5/seahub/thirdpart/bin’,
‘/home/seafile/seafile-pro-server-9.0.5/seafile/lib/python3/site-packages’,
‘/home/seafile/seafile-pro-server-9.0.5/seafile/lib64/python3/site-packages’,
‘/home/seafile/seafile-pro-server-9.0.5/seahub’,
‘/home/seafile/seafile-pro-server-9.0.5/seahub/thirdpart’,
‘/’,
‘/home/seafile/seafile-pro-server-9.0.5/pro/python’,
‘/home/seafile/seafile-pro-server-9.0.5/seahub/thirdparts’,
‘/usr/lib64/python36.zip’,
‘/usr/lib64/python3.6’,
‘/usr/lib64/python3.6/lib-dynload’,
‘/usr/local/lib64/python3.6/site-packages’,
‘/usr/local/lib/python3.6/site-packages’,
‘/usr/lib64/python3.6/site-packages’,
‘/usr/lib/python3.6/site-packages’,
‘/home/seafile/seafile-pro-server-9.0.5/seahub/seahub/auth/…/…/…/…/conf’,
‘/home/seafile/seafile-pro-server-9.0.5/seahub/seahub/api2/endpoints/…/…/…/…/…/conf’,
‘/home/seafile/seafile-pro-server-9.0.5/seahub/seahub/api2/endpoints/…/…/…/…/…/conf’,
‘/home/seafile/seafile-pro-server-9.0.5/seahub/seahub/oauth/…/…/…/…/conf’]
Server time: Wed, 01 Jun 2022 20:53:44 +0000

I appreciate the effort!

With kind regards,
Patrick

2

Topic can be closed.

I have no idea why, but today the issue resolved istself…

3

I’ve had the same issue. After hours of search and going through the code line by line, I had the epiphany, that it has to do with the user sessions.
I logged out of the desktop client and deleted all cookies in the browser, and everything was working fine afterwards.
I assume either the session signature key, or something alike, corrupted the authentication handling in the backend.
I hope this will help the next person facing this issue.