Hi,
quite a while ago I’ve given Seatable a first look (closed thread here). Unfortunately I didn’t find a lot time since to see how updates may have fixed some stuff. Yesterday I finally found some time, wen to the server and did a system update first and a docker-compose pull afterwards. Unfortunately this seems to have broken some stuff. I’m not sure what but while docker-compose seems to start more or less without errors that look terribly bad to me, I can’t reach the installation via the browser anymore.
Here’s the output:
root@table:/opt/seatable# docker-compose up
Starting seatable-redis ... done
Starting seatable-memcached ... done
Starting seatable-mysql ... done
Starting seatable ... done
Attaching to seatable-memcached, seatable-mysql, seatable-redis, seatable
seatable-mysql | 2021-12-09 09:13:32+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.5.13+maria~focal started.
seatable-mysql | 2021-12-09 09:13:32+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
seatable-mysql | 2021-12-09 09:13:32+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.5.13+maria~focal started.
seatable-redis | 1:C 09 Dec 2021 09:13:32.282 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
seatable-redis | 1:C 09 Dec 2021 09:13:32.282 # Redis version=5.0.7, bits=64, commit=00000000, modified=0, pid=1, just started
seatable-redis | 1:C 09 Dec 2021 09:13:32.282 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
seatable-redis | 1:M 09 Dec 2021 09:13:32.286 * Running mode=standalone, port=6379.
seatable-redis | 1:M 09 Dec 2021 09:13:32.286 # Server initialized
seatable-redis | 1:M 09 Dec 2021 09:13:32.286 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
seatable-redis | 1:M 09 Dec 2021 09:13:32.286 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
seatable-redis | 1:M 09 Dec 2021 09:13:32.287 * DB loaded from disk: 0.001 seconds
seatable-redis | 1:M 09 Dec 2021 09:13:32.287 * Ready to accept connections
seatable-mysql | 2021-12-09 9:13:33 0 [Note] mysqld (mysqld 10.5.13-MariaDB-1:10.5.13+maria~focal) starting as process 1 ...
seatable | *** Running /etc/my_init.d/01_init.sh...
seatable-mysql | 2021-12-09 9:13:33 0 [Note] InnoDB: Uses event mutexes
seatable-mysql | 2021-12-09 9:13:33 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
seatable-mysql | 2021-12-09 9:13:33 0 [Note] InnoDB: Number of pools: 1
seatable-mysql | 2021-12-09 9:13:33 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
seatable-mysql | 2021-12-09 9:13:33 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
seatable-mysql | 2021-12-09 9:13:33 0 [Note] InnoDB: Using Linux native AIO
seatable-mysql | 2021-12-09 9:13:33 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
seatable-mysql | 2021-12-09 9:13:33 0 [Note] InnoDB: Completed initialization of buffer pool
seatable | *** Booting runit daemon...
seatable | *** Runit started as PID 18
seatable | *** Running /templates/enterpoint.sh...
seatable | 2021-12-09 09:13:33 Conf exists
seatable-mysql | 2021-12-09 9:13:33 0 [Note] InnoDB: 128 rollback segments are active.
seatable-mysql | 2021-12-09 9:13:33 0 [Note] InnoDB: Creating shared tablespace for temporary tables
seatable-mysql | 2021-12-09 9:13:33 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
seatable-mysql | 2021-12-09 9:13:33 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
seatable-mysql | 2021-12-09 9:13:33 0 [Note] InnoDB: 10.5.13 started; log sequence number 19400827; transaction id 37144
seatable-mysql | 2021-12-09 9:13:33 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
seatable-mysql | 2021-12-09 9:13:33 0 [Note] Plugin 'FEEDBACK' is disabled.
seatable-mysql | 2021-12-09 9:13:33 0 [Note] Server socket created on IP: '::'.
seatable-mysql | 2021-12-09 9:13:33 0 [Warning] 'proxies_priv' entry '@% root@e187c7f38374' ignored in --skip-name-resolve mode.
seatable | 2021-12-09 09:13:33 Nginx ready
seatable-mysql | 2021-12-09 9:13:33 0 [Note] Reading of all Master_info entries succeeded
seatable-mysql | 2021-12-09 9:13:33 0 [Note] Added new Master_info '' to hash table
seatable-mysql | 2021-12-09 9:13:33 0 [Note] mysqld: ready for connections.
seatable-mysql | Version: '10.5.13-MariaDB-1:10.5.13+maria~focal' socket: '/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
seatable | Certificate will not expire
seatable | 2021-12-09 09:13:33 This is a idle script (infinite loop) to keep container running.
seatable-mysql | 2021-12-09 9:13:33 0 [Note] InnoDB: Buffer pool(s) load completed at 211209 9:13:33
(the date formatting in the log seems to be broken due to discourse formatting)
I tried accessing the app right before the update and it still worked fine after all the months. All i’m getting now is a Bad Gateway error from nginx. Did I just miss something important over time?
