In December I upgraded the Seafile Pro server from version 6 to the latest 9.0.13 version.
After a lot of struggle it seemed as its working fine. Users started complaining yesterday that they get unknown error on libraries.
When I look at the docker-compose logs -f I see this error all the time.
seafile-mysql | 2023-01-10 11:17:04 15 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
On the user logs I see these errors:
[01/10/23 07:21:52] sync-mgr.c(582): Repo ‘My Library’ sync state transition from ‘synchronized’ to ‘committing’.
[01/10/23 07:21:52] repo-mgr.c(3842): All events are processed for repo 0045b456-13f5-4f22-a699-942aa48fe8be.
[01/10/23 07:21:52] sync-mgr.c(582): Repo ‘My Library’ sync state transition from ‘committing’ to ‘initializing’.
[01/10/23 07:21:53] sync-mgr.c(582): Repo ‘Electra Mining 2018’ sync state transition from ‘synchronized’ to ‘committing’.
[01/10/23 07:21:53] repo-mgr.c(3842): All events are processed for repo f9dde04a-93dc-4c79-bf2d-758fd6fda443.
[01/10/23 07:21:53] sync-mgr.c(582): Repo ‘Electra Mining 2018’ sync state transition from ‘committing’ to ‘initializing’.
[01/10/23 07:21:54] sync-mgr.c(582): Repo ‘Engineering’ sync state transition from ‘synchronized’ to ‘committing’.
[01/10/23 07:22:05] repo-mgr.c(3842): All events are processed for repo 784a461b-bf8d-4ee0-8904-3e154c6689e4.
[01/10/23 07:22:05] sync-mgr.c(582): Repo ‘Engineering’ sync state transition from ‘committing’ to ‘initializing’.
[01/10/23 07:22:05] sync-mgr.c(881): Removing blocks for repo Engineering(784a461b).
[01/10/23 07:22:05] sync-mgr.c(582): Repo ‘ARVALV’ sync state transition from ‘synchronized’ to ‘committing’.
[01/10/23 07:22:07] repo-mgr.c(3842): All events are processed for repo b428a864-22e6-45a6-b2fe-e24d43ccbac0.
[01/10/23 07:22:07] sync-mgr.c(582): Repo ‘ARVALV’ sync state transition from ‘committing’ to ‘initializing’.
[01/10/23 09:40:03] clone-mgr.c(680): Transition clone state for 52829beb from [init] to [check server].
[01/10/23 09:40:04] clone-mgr.c(680): Transition clone state for 52829beb from [check server] to [fetch].
[01/10/23 09:40:04] http-tx-mgr.c(1157): Transfer repo ‘52829beb’: (‘normal’, ‘init’) → (‘normal’, ‘check’)
[01/10/23 09:40:04] http-tx-mgr.c(1157): Transfer repo ‘52829beb’: (‘normal’, ‘check’) → (‘normal’, ‘commit’)
[01/10/23 09:40:04] http-tx-mgr.c(1157): Transfer repo ‘52829beb’: (‘normal’, ‘commit’) → (‘normal’, ‘fs’)
[01/10/23 09:40:04] http-tx-mgr.c(4010): Bad response code for GET https://cloud.xxxxxx.net/seafhttp/repo/52829beb-fde9-46a6-9ffa-a1c45f46f695/fs-id-list/?server-head=207fee66f1b56441a7ecf7881325bdcc13e7341b: 447.
[01/10/23 09:40:04] http-tx-mgr.c(4580): Failed to get fs id list for repo 52829beb on server https://cloud.xxxxxx.net.
[01/10/23 09:40:04] http-tx-mgr.c(1157): Transfer repo ‘52829beb’: (‘normal’, ‘fs’) → (‘error’, ‘finished’)
[01/10/23 09:40:04] clone-mgr.c(697): Transition clone state for 52829beb from [fetch] to [error]: Unknown error.
In my docker-compose.yml the db shows as :
services:
db:
image: mariadb:10.5
Does anyone know if I should run a newer mariadb or what the issue actually is. I appreciate any assistance on the matter.
Thank you