"Connection refused" to mysql in docker on Raspberry Pi

[woj-tek]

"Connection refused" to mysql in docker on Raspberry Pi

[freeplant]

No good idea on this problem. You can try to ask support questions in our forum https://forum.seafile.com

[woj-tek]

Thanks @freeplant

(ref: https://forum.seafile.com/t/connection-refused-to-mysql-in-docker/19484)

[mdlaat]

Same here. The problems seems to be the latest (as of today 11.0.6) docker image for arm64. If I use 11.0.5 for arm there is no problem.

[woj-tek]

Same here. The problems seems to be the latest (as of today 11.0.6) docker image for arm64. If I use 11.0.5 for arm there is no problem.

Interesting @mdlaat , I switched back to 11.0.5 the problem still persists though:

seafile-mysql      | 2024-03-24T16:39:19.040657174Z 2024-03-24 16:39:19 0 [Note] InnoDB: Buffer pool(s) load completed at 240324 16:39:19
seafile-mysql      | 2024-03-24T16:39:19.885692424Z 2024-03-24 16:39:19 3 [Warning] Aborted connection 3 to db: 'unconnected' user: 'seafile' host: '172.28.0.4' (Got an error reading communication packets)
seafile            | 2024-03-24T16:39:19.891142637Z [2024-03-24 16:39:19] Skip running setup-seafile-mysql.py because there is existing seafile-data folder.
seafile            | 2024-03-24T16:39:19.891203210Z waiting for mysql server to be ready: %s (2003, "Can't connect to MySQL server on 'seafile_db' ([Errno 111] Connection refused)")
seafile            | 2024-03-24T16:39:19.891296191Z [03/24/2024 16:39:19][upgrade]: The container was recreated, start fix the media symlinks
seafile            | 2024-03-24T16:39:19.922879605Z [03/24/2024 16:39:19][upgrade]: Done
seafile            | 2024-03-24T16:39:19.928868075Z
seafile            | 2024-03-24T16:39:20.001321689Z Starting seafile server, please wait ...
seafile            | 2024-03-24T16:39:23.039491644Z Seafile server started
seafile            | 2024-03-24T16:39:23.039676513Z
seafile            | 2024-03-24T16:39:23.039726791Z Done.
seafile            | 2024-03-24T16:39:23.054099329Z
seafile            | 2024-03-24T16:39:23.142385436Z Starting seahub at port 8000 ...
seafile-mysql      | 2024-03-24T16:39:26.508956742Z 2024-03-24 16:39:26 6 [Warning] Aborted connection 6 to db: 'seahub_db' user: 'seafile' host: '172.28.0.4' (Got an error reading communication packets)
seafile            | 2024-03-24T16:39:29.298772900Z
seafile            | 2024-03-24T16:39:29.298894344Z Seahub is started
seafile            | 2024-03-24T16:39:29.298916658Z
seafile            | 2024-03-24T16:39:29.298931918Z Done.
seafile            | 2024-03-24T16:39:29.298946436Z
seafile-mysql      | 2024-03-24T16:39:46.502588933Z 2024-03-24 16:39:46 13 [Warning] Access denied for user 'root'@'172.28.0.2' (using password: NO)

[SkywalkerSpace]

If seafile starts normally on your device and is usable, you can ignore this issue. And if the logs cause trouble to you, we will optimize the output logs later.

If seafile cannot be started on your device, you can try to enter the container to manually debug the code. My guess is that the problem is caused by special characters in your mysql configuration.

The source code: wait_for_mysql

1. Enter the container

docker exec -it seafile bash

2. Modify the /scripts/utils.py, add the prints to line 285

vim /scripts/utils.py

    print('db_host', db_host)
    print('db_port', db_port)
    print('db_user', db_user)
    print('db_passwd', db_passwd)

3. Run the /scripts/start.py and check the output

/scripts/start.py

[woj-tek]

If seafile starts normally on your device and is usable, you can ignore this issue. And if the logs cause trouble to you, we will optimize the output logs later.

Unfortunately it doesn't hence my investigation :-)

3. Run the /scripts/start.py and check the output

Argh:

Seafile controller is already running, pid 88

Killed the process, and got the result:

root@943d2ee6800f:/opt/seafile# kill -9 88
root@943d2ee6800f:/opt/seafile# /scripts/start.py
db_host seafile_db
db_port 3306
db_user seafile
db_passwd 187a7…-…-72390
[2024-03-25 14:00:09] Skip running setup-seafile-mysql.py because there is existing seafile-data folder.

[seafevents] is running, pid 132. You can stop it by:

        kill 132

Stop it and try again.



Warning: seafile-controller not running. Have you run "./seafile.sh start" ?

Traceback (most recent call last):
  File "/scripts/start.py", line 95, in <module>
    main()
  File "/scripts/start.py", line 81, in main
    call('{} start'.format(get_script('seahub.sh')))
  File "/scripts/utils.py", line 70, in call
    return subprocess.check_call(*a, **kw)
  File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '/opt/seafile/seafile-server-11.0.5/seahub.sh start' returned non-zero exit status 1.
root@943d2ee6800f:/opt/seafile#

Afterwards service seems to be inoperable still.

While in the same container I installed mysql-client and connected with the printed details:

root@943d2ee6800f:/opt/seafile# mysql -h seafile_db -u seafile -p187a7…c5c5472390
mysql: [Warning] Using a password on the command line interface can be insecure.
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 2951
Server version: 5.5.5-10.11.7-MariaDB-1:10.11.7+maria~ubu2204 mariadb.org binary distribution

Copyright (c) 2000, 2024, Oracle and/or its affiliates.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> show databases;
+--------------------+
| Database           |
+--------------------+
| ccnet_db           |
| information_schema |
| seafile_db         |
| seahub_db          |
+--------------------+
4 rows in set (0.01 sec)

mysql>

I tried granting rights with 'seafile'@'%' (as oposed to 'seafile'@'%.%.%.%') but still no luck.

---

What's concernig is the difference in error messages on mysql end (denied for root and issues with connectivity it seems for seafile):

seafile-mysql      | 2024-03-25T14:11:48.648594059Z 2024-03-25 14:11:48 2986 [Warning] Access denied for user 'root'@'172.28.0.2' (using password: NO)
seafile-mysql      | 2024-03-25T14:11:50.666525874Z 2024-03-25 14:11:50 2987 [Warning] Aborted connection 2987 to db: 'seahub_db' user: 'seafile' host: '172.28.0.4' (Got an error reading communication packets)

What is the %s in the log entry?

seafile            | 2024-03-25T14:24:10.434026990Z waiting for mysql server to be ready: %s (2003, "Can't connect to MySQL server on 'seafile_db' ([Errno 111] Connection refused)")

---

EDIT: while running the script I constantly get this in mysql logs:

seafile-mysql      | 2024-03-25T14:33:26.494698474Z 2024-03-25 14:33:26 22 [Warning] Aborted connection 22 to db: 'seahub_db' user: 'seafile' host: '172.28.0.4' (Got an error reading communication packets)
seafile-mysql      | 2024-03-25T14:33:26.494821103Z 2024-03-25 14:33:26 21 [Warning] Aborted connection 21 to db: 'seahub_db' user: 'seafile' host: '172.28.0.4' (Got an error reading communication packets)
seafile-mysql      | 2024-03-25T14:33:26.494851769Z 2024-03-25 14:33:26 20 [Warning] Aborted connection 20 to db: 'seahub_db' user: 'seafile' host: '172.28.0.4' (Got an error reading communication packets)
seafile-mysql      | 2024-03-25T14:33:26.495396933Z 2024-03-25 14:33:26 19 [Warning] Aborted connection 19 to db: 'seafile_db' user: 'seafile' host: '172.28.0.4' (Got an error reading communication packets)
seafile-mysql      | 2024-03-25T14:33:26.495496858Z 2024-03-25 14:33:26 18 [Warning] Aborted connection 18 to db: 'seafile_db' user: 'seafile' host: '172.28.0.4' (Got an error reading communication packets)
seafile-mysql      | 2024-03-25T14:33:33.104148370Z 2024-03-25 14:33:33 26 [Warning] Aborted connection 26 to db: 'seahub_db' user: 'seafile' host: '172.28.0.4' (Got an error reading communication packets)

[SkywalkerSpace]

The phenomenon is that mysql-client can connect to mysql, but the python pymysql cannot connect to mysql. Based on this, I guess it is a problem with python pymysql. But we don't have rpi to test.

This is a simple script to verify if there is a problem with pymysql

docker exec -it seafile bash

vim test_pymysql.py

Content

import pymysql

db_host = 'seafile_db'
db_user = '3306'
db_passwd = '187a7…-…-…'
db_port = 3306
connection = pymysql.connect(host=db_host, port=db_port, user=db_user, passwd=db_passwd)

Then run the script

python3 test_pymysql.py

If it is really a problem with pymysql, you can remove wait_for_mysql() to temporarily solve the problem.
We will consider other ways to implement python connect mysql later.

vim /scripts/start.py

Find wait_for_mysql() and remove it.

Then restart the container

docker restart seafile

[woj-tek]

I ran the thing and it worked.

I then added more debug to utils.py:

def wait_for_mysql():
    logdbg(f'wait inside')
    print(f'wait inside')
    db_host = get_conf('DB_HOST', '127.0.0.1')
    db_user = 'root'
    db_passwd = get_conf('DB_ROOT_PASSWD', '')
    db_port = int(get_conf('DB_PORT', 3306))
    logdbg(f'conn1, db_host: {db_host}, db_user: {db_user}, db_passwd: {db_passwd}, db_port: {db_port}')
    print(f'conn1, db_host: {db_host}, db_user: {db_user}, db_passwd: {db_passwd}, db_port: {db_port}')


    installdir = get_install_dir()
    topdir = dirname(installdir)
    seafile_conf_path = join(topdir, 'conf', 'seafile.conf')
    if exists(seafile_conf_path):
        cp = ConfigParser()
        cp.read(seafile_conf_path)
        db_host = cp.get('database', 'host')
        db_user = cp.get('database', 'user')
        db_passwd = cp.get('database', 'password')
        db_port = int(cp.get('database', 'port'))

    print(f'conn2, db_host: {db_host}, db_user: {db_user}, db_passwd: {db_passwd}, db_port: {db_port}', flush=True)
    while True:
        try:
            connection = pymysql.connect(host=db_host, port=db_port, user=db_user, passwd=db_passwd)
        except Exception as e:
            print ('waiting for mysql server to be ready: %s', e)
            time.sleep(2)
            continue
        logdbg('mysql server is ready')
        print(f'ready my', flush=True)
        connection.close()
        return

and... it worked as well (I'm confused) but it seems to be failing to connect to the database from the app (flask?) itself it seems, though no exception:

seafile            | 2024-03-29T14:43:20.884504784Z wait
seafile            | 2024-03-29T14:43:20.884683209Z wait inside
seafile            | 2024-03-29T14:43:20.884705875Z conn1, db_host: seafile_db, db_user: root, db_passwd: db_dev, db_port: 3306
seafile            | 2024-03-29T14:43:20.884722227Z conn2, db_host: seafile_db, db_user: seafile, db_passwd: 187a…-…-…-…-…72390, db_port: 3306
seafile            | 2024-03-29T14:43:20.902933652Z ready my
seafile            | 2024-03-29T14:43:20.905207177Z [2024-03-29 14:43:20] Skip running setup-seafile-mysql.py because there is existing seafile-data folder.
seafile            | 2024-03-29T14:43:20.912641250Z
seafile            | 2024-03-29T14:43:20.992475930Z Starting seafile server, please wait ...
seafile            | 2024-03-29T14:43:24.030383109Z Seafile server started
seafile            | 2024-03-29T14:43:24.030576608Z
seafile            | 2024-03-29T14:43:24.030631181Z Done.
seafile            | 2024-03-29T14:43:24.044834497Z
seafile            | 2024-03-29T14:43:24.136829171Z Starting seahub at port 8000 ...
seafile-mysql      | 2024-03-29T14:43:25.979569071Z 2024-03-29 14:43:25 91 [Warning] Aborted connection 91 to db: 'seahub_db' user: 'seafile' host: '172.28.0.4' (Got an error reading communication packets)
seafile            | 2024-03-29T14:43:29.947261878Z
seafile            | 2024-03-29T14:43:29.947478080Z Seahub is started
seafile            | 2024-03-29T14:43:29.947592376Z
seafile            | 2024-03-29T14:43:29.948174225Z Done.
seafile            | 2024-03-29T14:43:29.948258150Z

From what I can see in vim /opt/seafile/seafile-server-11.0.6/seahub.sh it starts the app here:

function start_seahub () {
    before_start;
    echo "Starting seahub at port ${port} ..."
    check_init_admin;

    export DJANGO_SETTINGS_MODULE=seahub.settings
    $PYTHON $gunicorn_exe seahub.wsgi:application -c "${gunicorn_conf}" --preload

I'm at a loss here, all settings in all files under /shared/seafile/conf seems to have correct credentials...

[SkywalkerSpace]

The warning and the error in the log are different.

seafile-mysql      | 2024-03-29T14:43:25.979569071Z 2024-03-29 14:43:25 91 [Warning] Aborted connection 91 to db: 'seahub_db' user: 'seafile' host: '172.28.0.4' (Got an error reading communication packets)

The warning means already connected to mysql, but the connection was interrupted, and didn't use the correct method to disconnect.

seafile            | 2024-03-25T14:24:10.434026990Z waiting for mysql server to be ready: %s (2003, "Can't connect to MySQL server on 'seafile_db' ([Errno 111] Connection refused)")

The error means cannot connect to mysql.

[woj-tek]

Yes, they are different. There are two problems:

1. after modifying startup scripts the second error is gone for some reason (though, seafile still doesn't work)
2. there is no error message in seafile for the second error (maybe lack of "flush=True" in log statements? that caught me off guard while I was debugging the issue)

As I said - I kinda got stuck now and don't know how to debug further - I don't see any error in seafile anymore but it still doesn't work. Is there a way to increase debugging / force flushing of logs to know what's going on?

[freeplant]

seafile-mysql | 2024-03-29T14:43:25.979569071Z 2024-03-29 14:43:25 91 [Warning] Aborted connection 91 to db: 'seahub_db' user: 'seafile' host: '172.28.0.4' (Got an error reading communication packets)

This warning message is caused by restarting of Seafile. It is normal.

What error message do you have now if you visit Seafile web interface? What error logs do you have in seahub.log and seafile.log?

[woj-tek]

It turns out, that despite the mysql error seafile seems to be working now... there is another issue with client ("Repo 'x' sync is finished but with error: Error when indexing) but that seems to be different issue...

---

What error message do you have now if you visit Seafile web interface? What error logs do you have in seahub.log and seafile.log?

@freeplant
The web interface doesn't open and I don't see any errors in the logs:

2024-03-29 14:35:12 ../common/seaf-utils.c(359): Use database Mysql
2024-03-29 14:35:12 http-server.c(199): fileserver: worker_threads = 10
2024-03-29 14:35:12 http-server.c(213): fileserver: fixed_block_size = 8388608
2024-03-29 14:35:12 http-server.c(228): fileserver: web_token_expire_time = 3600
2024-03-29 14:35:12 http-server.c(243): fileserver: max_indexing_threads = 1
2024-03-29 14:35:12 http-server.c(258): fileserver: max_index_processing_threads= 3
2024-03-29 14:35:12 http-server.c(280): fileserver: cluster_shared_temp_file_mode = 600
2024-03-29 14:35:12 socket file exists, delete it anyway
2024-03-29 14:35:15 start to serve on pipe client
2024-03-29 14:35:17 start to serve on pipe client
2024-03-29 14:35:17 start to serve on pipe client
2024-03-29 14:35:21 start to serve on pipe client
2024-03-29 14:36:26 ../common/seaf-utils.c(359): Use database Mysql
2024-03-29 14:36:26 http-server.c(199): fileserver: worker_threads = 10
2024-03-29 14:36:26 http-server.c(213): fileserver: fixed_block_size = 8388608
2024-03-29 14:36:26 http-server.c(228): fileserver: web_token_expire_time = 3600
2024-03-29 14:36:26 http-server.c(243): fileserver: max_indexing_threads = 1
2024-03-29 14:36:26 http-server.c(258): fileserver: max_index_processing_threads= 3
2024-03-29 14:36:26 http-server.c(280): fileserver: cluster_shared_temp_file_mode = 600
2024-03-29 14:36:26 socket file exists, delete it anyway
2024-03-29 14:36:30 start to serve on pipe client
2024-03-29 14:36:32 start to serve on pipe client
2024-03-29 14:36:32 start to serve on pipe client
2024-03-29 14:36:32 start to serve on pipe client
2024-03-29 14:41:38 ../common/seaf-utils.c(359): Use database Mysql
2024-03-29 14:41:38 http-server.c(199): fileserver: worker_threads = 10
2024-03-29 14:41:38 http-server.c(213): fileserver: fixed_block_size = 8388608
2024-03-29 14:41:38 http-server.c(228): fileserver: web_token_expire_time = 3600
2024-03-29 14:41:38 http-server.c(243): fileserver: max_indexing_threads = 1
2024-03-29 14:41:38 http-server.c(258): fileserver: max_index_processing_threads= 3
2024-03-29 14:41:38 http-server.c(280): fileserver: cluster_shared_temp_file_mode = 600
2024-03-29 14:41:38 socket file exists, delete it anyway
2024-03-29 14:41:41 start to serve on pipe client
2024-03-29 14:41:43 start to serve on pipe client
2024-03-29 14:41:43 start to serve on pipe client
2024-03-29 14:41:53 start to serve on pipe client
2024-03-29 14:43:21 ../common/seaf-utils.c(359): Use database Mysql
2024-03-29 14:43:21 http-server.c(199): fileserver: worker_threads = 10
2024-03-29 14:43:21 http-server.c(213): fileserver: fixed_block_size = 8388608
2024-03-29 14:43:21 http-server.c(228): fileserver: web_token_expire_time = 3600
2024-03-29 14:43:21 http-server.c(243): fileserver: max_indexing_threads = 1
2024-03-29 14:43:21 http-server.c(258): fileserver: max_index_processing_threads= 3
2024-03-29 14:43:21 http-server.c(280): fileserver: cluster_shared_temp_file_mode = 600
2024-03-29 14:43:21 socket file exists, delete it anyway
2024-03-29 14:43:24 start to serve on pipe client
2024-03-29 14:43:26 start to serve on pipe client
2024-03-29 14:43:26 start to serve on pipe client
2024-03-29 14:43:29 start to serve on pipe client

(I think that making changes to the startup script causes some exception that's silently ignored…)

I just tore down and recreated containers (docker compose down & pull & up) and the error is the same/returned:

seafile-mysql      | 2024-04-06T12:52:18.471235009Z 2024-04-06 12:52:18+00:00 [Note] [Entrypoint]: MariaDB upgrade not required
seafile-mysql      | 2024-04-06T12:52:18.524395937Z 2024-04-06 12:52:18 0 [Note] Starting MariaDB 10.11.7-MariaDB-1:10.11.7+maria~ubu2204 source revision 87e13722a95af5d9378d990caf48cb6874439347 as process 1
seafile-mysql      | 2024-04-06T12:52:18.618141324Z 2024-04-06 12:52:18 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
seafile-mysql      | 2024-04-06T12:52:18.625607709Z 2024-04-06 12:52:18 0 [Note] InnoDB: Number of transaction pools: 1
seafile-mysql      | 2024-04-06T12:52:18.625869004Z 2024-04-06 12:52:18 0 [Note] InnoDB: Using ARMv8 crc32 instructions
seafile-mysql      | 2024-04-06T12:52:18.626407334Z 2024-04-06 12:52:18 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
seafile-mysql      | 2024-04-06T12:52:18.627491328Z 2024-04-06 12:52:18 0 [Warning] mariadbd: io_uring_queue_init() failed with errno 1
seafile-mysql      | 2024-04-06T12:52:18.628255750Z 2024-04-06 12:52:18 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF
seafile-mysql      | 2024-04-06T12:52:18.631365195Z 2024-04-06 12:52:18 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
seafile-mysql      | 2024-04-06T12:52:18.637114312Z 2024-04-06 12:52:18 0 [Note] InnoDB: Completed initialization of buffer pool
seafile-mysql      | 2024-04-06T12:52:18.642494652Z 2024-04-06 12:52:18 0 [Note] InnoDB: File system buffers for log disabled (block size=4096 bytes)
seafile-mysql      | 2024-04-06T12:52:18.749642502Z 2024-04-06 12:52:18 0 [Note] InnoDB: End of log at LSN=16652872
seafile-mysql      | 2024-04-06T12:52:18.854782345Z 2024-04-06 12:52:18 0 [Note] InnoDB: 128 rollback segments are active.
seafile-mysql      | 2024-04-06T12:52:18.859590633Z 2024-04-06 12:52:18 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
seafile-mysql      | 2024-04-06T12:52:18.859661263Z 2024-04-06 12:52:18 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
seafile-mysql      | 2024-04-06T12:52:18.865152417Z 2024-04-06 12:52:18 0 [Note] InnoDB: log sequence number 16652872; transaction id 129073
seafile-mysql      | 2024-04-06T12:52:18.865949117Z 2024-04-06 12:52:18 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
seafile-mysql      | 2024-04-06T12:52:18.866461318Z 2024-04-06 12:52:18 0 [Note] Plugin 'FEEDBACK' is disabled.
seafile-mysql      | 2024-04-06T12:52:18.868760972Z 2024-04-06 12:52:18 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
seafile-mysql      | 2024-04-06T12:52:18.876448318Z 2024-04-06 12:52:18 0 [Note] Server socket created on IP: '0.0.0.0'.
seafile-mysql      | 2024-04-06T12:52:18.876579410Z 2024-04-06 12:52:18 0 [Note] Server socket created on IP: '::'.
seafile-mysql      | 2024-04-06T12:52:19.037568961Z 2024-04-06 12:52:19 0 [Note] mariadbd: ready for connections.
seafile-mysql      | 2024-04-06T12:52:19.037686368Z Version: '10.11.7-MariaDB-1:10.11.7+maria~ubu2204'  socket: '/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
seafile-mysql      | 2024-04-06T12:52:19.784240044Z 2024-04-06 12:52:19 0 [Note] InnoDB: Buffer pool(s) load completed at 240406 12:52:19
seafile            | 2024-04-06T12:52:20.473665092Z [2024-04-06 12:52:20] Skip running setup-seafile-mysql.py because there is existing seafile-data folder.
seafile            | 2024-04-06T12:52:20.474647382Z waiting for mysql server to be ready: %s (2003, "Can't connect to MySQL server on 'seafile_db' ([Errno 111] Connection refused)")
seafile            | 2024-04-06T12:52:20.474721178Z [04/06/2024 12:52:20][upgrade]: The container was recreated, start fix the media symlinks
seafile            | 2024-04-06T12:52:20.499639799Z [04/06/2024 12:52:20][upgrade]: Done
seafile            | 2024-04-06T12:52:20.505756617Z
seafile            | 2024-04-06T12:52:20.581895732Z Starting seafile server, please wait ...
seafile            | 2024-04-06T12:52:23.605976748Z Seafile server started
seafile            | 2024-04-06T12:52:23.606079062Z
seafile            | 2024-04-06T12:52:23.606645540Z Done.
seafile            | 2024-04-06T12:52:23.612755284Z
seafile            | 2024-04-06T12:52:23.664668441Z Starting seahub at port 8000 ...
seafile-mysql      | 2024-04-06T12:52:26.902800092Z 2024-04-06 12:52:26 6 [Warning] Aborted connection 6 to db: 'seahub_db' user: 'seafile' host: '172.29.0.4' (Got an error reading communication packets)
seafile-mysql      | 2024-04-06T12:52:27.352091918Z 2024-04-06 12:52:27 9 [Warning] Aborted connection 9 to db: 'seahub_db' user: 'seafile' host: '172.29.0.4' (Got an error reading communication packets)
seafile            | 2024-04-06T12:52:29.785359923Z
seafile            | 2024-04-06T12:52:29.785523293Z Seahub is started
seafile            | 2024-04-06T12:52:29.785570478Z
seafile            | 2024-04-06T12:52:29.785585978Z Done.
seafile            | 2024-04-06T12:52:29.785600589Z

And virgin seafile.log only says this:

root@2cd2c52dd944:/opt/seafile# cat logs/seafile.log
2024-04-06 12:52:20 ../common/seaf-utils.c(359): Use database Mysql
2024-04-06 12:52:20 http-server.c(199): fileserver: worker_threads = 10
2024-04-06 12:52:20 http-server.c(213): fileserver: fixed_block_size = 8388608
2024-04-06 12:52:20 http-server.c(228): fileserver: web_token_expire_time = 3600
2024-04-06 12:52:20 http-server.c(243): fileserver: max_indexing_threads = 1
2024-04-06 12:52:20 http-server.c(258): fileserver: max_index_processing_threads= 3
2024-04-06 12:52:20 http-server.c(280): fileserver: cluster_shared_temp_file_mode = 600
2024-04-06 12:52:23 start to serve on pipe client
2024-04-06 12:52:27 start to serve on pipe client
2024-04-06 12:52:27 start to serve on pipe client
2024-04-06 12:52:29 start to serve on pipe client

seahub.log:

root@2cd2c52dd944:/opt/seafile# cat logs/seahub.log
2024-04-06 12:52:27,917 [INFO] seafevents.db:69 create_engine_from_conf [seafevents] database: mysql, name: seahub_db

nginx seems to be listening just fine:

root@2cd2c52dd944:/opt/seafile# lsof -iTCP -sTCP:LISTEN -Pn
COMMAND   PID USER   FD   TYPE   DEVICE SIZE/OFF NODE NAME
nginx      35 root   12u  IPv4 43564966      0t0  TCP *:80 (LISTEN)
seaf-serv  90 root   11u  IPv4 43564006      0t0  TCP *:8082 (LISTEN)
python3   142 root    8u  IPv4 43568298      0t0  TCP 127.0.0.1:8000 (LISTEN)
python3   166 root    8u  IPv4 43568298      0t0  TCP 127.0.0.1:8000 (LISTEN)
python3   167 root    8u  IPv4 43568298      0t0  TCP 127.0.0.1:8000 (LISTEN)
python3   168 root    8u  IPv4 43568298      0t0  TCP 127.0.0.1:8000 (LISTEN)
python3   169 root    8u  IPv4 43568298      0t0  TCP 127.0.0.1:8000 (LISTEN)
python3   170 root    8u  IPv4 43568298      0t0  TCP 127.0.0.1:8000 (LISTEN)