/api/v2.1/repos/2a54b9bd-c1ec-44bb-b5de-c9e896fb404b/repo-tags/ [HTTP/1.1 500 Internal Server Error 123ms]

Seafile Server
#1

Hey, everybody!
after upgrading from 6.2 to 6.3 I got this error, please help.

tail seahub.log
File “/opt/data/drop/seafile-server-9.0.9/seahub/thirdpart/django/db/backends/utils.py”, line 84, in _execute
return self.cursor.execute(sql, params)
File “/opt/data/drop/seafile-server-9.0.9/seahub/thirdpart/django/db/utils.py”, line 90, in exit
raise dj_exc_value.with_traceback(traceback) from exc_value
File “/opt/data/drop/seafile-server-9.0.9/seahub/thirdpart/django/db/backends/utils.py”, line 84, in _execute
return self.cursor.execute(sql, params)
File “/opt/data/drop/seafile-server-9.0.9/seahub/thirdpart/django/db/backends/sqlite3/base.py”, line 423, in execute
return Database.Cursor.execute(self, query, params)
django.db.utils.OperationalError: no such table: file_tags_filetags
2023-08-14 21:09:37,095 [ERROR] seahub.api2.endpoints.dir:98 get_dir_file_info_list no such table: file_tags_filetags

#2

I don’t really understand how an upgrade from 6.2 to 6.3 has server 9.0.9, but for the upgrade to 6.3 there was a change in file comments.
While I’m not entirely sure this is the issue, it might be worth checking out.

Source: Seafile Community Edition - Seafile Admin Manual
Version 6.3 also changed the database table for file comments, if you have used this feature, you need migrate old file comments using the following commends after upgrading to 6.3:

./seahub.sh python-env seahub/manage.py migrate_file_comment

Note, this command should be run while Seafile server is running.