Revert from failed seafile 11.0.5 Upgrade back to 10.0 does not work

Seafile Server
,
1

After failing with upgrade to Seafile 11.0.5 due to Django requiring MariaDB 10.4 see (Upgrade from 10.0.x to 11.0.5 requires MariaDB 10.4). Unlink of seafile-server-lastest and linking it to seafile-server-10.0.1

lrwxrwxrwx  1 seafile seafile       21 Feb 19 13:56 seafile-server-latest -> seafile-server-10.0.1

The server fails to start. The seahub.log has the following:

[ERROR] root:64 <module> Failed to import seafevents package.
Traceback (most recent call last):
  File "/home/seafile/seafile-server-10.0.1/seahub/seahub/utils/__init__.py", line 62, in <module>
    from seafevents import seafevents_api
ModuleNotFoundError: No module named 'seafevents'

I can neither move forward quickly or go back.

2

I found that by downgrading the python packages installed using pip3 resolved the issue.

pip3 install Pillow==9.3.* captcha==0.4 djangosaml2==1.5.* django_simple_captcha==0.5.*
3

but the seahub.log still has the same error messages about seafevents

2024-02-19 17:24:54,301 [ERROR] root:64 <module> Failed to import seafevents package.
Traceback (most recent call last):
  File "/home/seafile/seafile-server-10.0.1/seahub/seahub/utils/__init__.py", line 62, in <module>
    from seafevents import seafevents_api
ModuleNotFoundError: No module named 'seafevents'
2024-02-19 17:24:54,310 [ERROR] root:557 <module> Failed to import seafevents package.
Traceback (most recent call last):
  File "/home/seafile/seafile-server-10.0.1/seahub/seahub/utils/__init__.py", line 553, in <module>
    import seafevents
ModuleNotFoundError: No module named 'seafevents'
4

And the controller.log has this…

2024-02-19 17:24:50 seafile-controller.c(481): Config [fileserver, use_go_fileserver] not set, default is FALSE.
2024-02-19 17:24:50 seafile-controller.c(191): starting seaf-server ...
2024-02-19 17:24:50 seafile-controller.c(82): spawn_process: seaf-server -F /home/seafile/conf -c /home/seafile/ccnet -d /home/seafile/seafile-data -l /home/seafile/logs
/seafile.log -P /home/seafile/pids/seaf-server.pid -p /home/seafile/seafile-server-10.0.1/runtime
2024-02-19 17:24:50 seafile-controller.c(116): spawned seaf-server, pid 417372
2024-02-19 17:25:00 seafile-controller.c(458): path /proc/400656 doesn't exist, restart progress [4]
2024-02-19 17:25:00 seafile-controller.c(532): seafevents need restart...
2024-02-19 17:25:00 seafile-controller.c(82): spawn_process: /usr/bin/python3 -m seafevents.main --config-file /home/seafile/conf/seafevents.conf --logfile /home/seafile
/logs/seafevents.log -P /home/seafile/pids/seafevents.pid
2024-02-19 17:25:00 seafile-controller.c(116): spawned /usr/bin/python3, pid 417420
2024-02-19 17:25:00 seafile-controller.c(124): /usr/bin/python3: Error while finding module specification for 'seafevents.main' (ModuleNotFoundError: No module named 'se
afevents')

and seems to continually try to respawn the seafevents.

5

You could update mariadb from the official mariadb repo. Here a simple howto for 10.5 instead of a seafile rollback.

Hope this will help you.

How To Install MariaDB 10.5 on Ubuntu 22.04|20.04 | ComputingForGeeks