Mai Comments - Answer Overflow

Mai

Posts Comments

IImmich

•Created by Mai on 5/18/2025 in #help-desk-support

System crashed and corrupted multiple files

Thanks a lot for your help, really appreciate it!

113 replies

IImmich

•Created by Mai on 5/18/2025 in #help-desk-support

System crashed and corrupted multiple files

hey Mraedis, here are some additional updates: the bind mounts are also working now, at first the bind mount pictures are "broken", however, after a container restart, thumbnails are generated properly.

113 replies

IImmich

•Created by Mai on 5/18/2025 in #help-desk-support

System crashed and corrupted multiple files

@Mraedis Hello Mraedis, I am happy to report that after restarting my Synology, immich is working fine now (I didn't rebuild after restart, it is the same build as before restart).

113 replies

IImmich

•Created by Mai on 5/18/2025 in #help-desk-support

System crashed and corrupted multiple files

might have to reboot my synology nas, will report back

113 replies

IImmich

•Created by Mai on 5/18/2025 in #help-desk-support

System crashed and corrupted multiple files

yep, there is none

113 replies

IImmich

•Created by Mai on 5/18/2025 in #help-desk-support

System crashed and corrupted multiple files

there is nothing in the external library section, and I didn't add any.

113 replies

IImmich

•Created by Mai on 5/18/2025 in #help-desk-support

System crashed and corrupted multiple files

113 replies

IImmich

•Created by Mai on 5/18/2025 in #help-desk-support

System crashed and corrupted multiple files

in the admin section, "GENERATE THUMBNAILS" tab, it was showing 0 active, 3 waiting. After I pressed the "missing", 4 is waiting

113 replies

IImmich

•Created by Mai on 5/18/2025 in #help-desk-support

System crashed and corrupted multiple files

the thumbnails are broken

113 replies

IImmich

•Created by Mai on 5/18/2025 in #help-desk-support

System crashed and corrupted multiple files

Really have no idea here. Maybe I rebuilt way too many time yesterday, and somehow the docker daemon cached some werid errors and corruptted my new build? doesn't make any sense. Should restart my host (synology NAS)?

113 replies

IImmich

•Created by Mai on 5/18/2025 in #help-desk-support

System crashed and corrupted multiple files

All the logs above are from a fresh rebuild (built just 5 mins before I post on Discord), so all the logs are from the very begining

113 replies

IImmich

•Created by Mai on 5/18/2025 in #help-desk-support

System crashed and corrupted multiple files

machine learning:

[05/19/25 18:33:24] INFO     Starting gunicorn 23.0.0                           

[05/19/25 18:33:24] INFO     Listening at: http://[::]:3003 (8)                 

[05/19/25 18:33:24] INFO     Using worker: immich_ml.config.CustomUvicornWorker 

[05/19/25 18:33:24] INFO     Booting worker with pid: 9                         

[05/19/25 18:34:32] INFO     Started server process [9]                         

[05/19/25 18:34:32] INFO     Waiting for application startup.                   

[05/19/25 18:34:32] INFO     Created in-memory cache with unloading after 300s  

                             of inactivity.                                     

[05/19/25 18:34:32] INFO     Initialized request thread pool with 4 threads.    

[05/19/25 18:34:32] INFO     Application startup complete.

[05/19/25 18:33:24] INFO     Starting gunicorn 23.0.0                           

[05/19/25 18:33:24] INFO     Listening at: http://[::]:3003 (8)                 

[05/19/25 18:33:24] INFO     Using worker: immich_ml.config.CustomUvicornWorker 

[05/19/25 18:33:24] INFO     Booting worker with pid: 9                         

[05/19/25 18:34:32] INFO     Started server process [9]                         

[05/19/25 18:34:32] INFO     Waiting for application startup.                   

[05/19/25 18:34:32] INFO     Created in-memory cache with unloading after 300s  

                             of inactivity.                                     

[05/19/25 18:34:32] INFO     Initialized request thread pool with 4 threads.    

[05/19/25 18:34:32] INFO     Application startup complete.

113 replies

IImmich

•Created by Mai on 5/18/2025 in #help-desk-support

System crashed and corrupted multiple files

Postgres also looks fine:

The files belonging to this database system will be owned by user "postgres".

This user must also own the server process.

The database cluster will be initialized with locale "en_US.utf8".

The default database encoding has accordingly been set to "UTF8".

The default text search configuration will be set to "english".

Data page checksums are enabled.

fixing permissions on existing directory /var/lib/postgresql/data ... ok

creating subdirectories ... ok

selecting dynamic shared memory implementation ... posix

selecting default max_connections ... 100

selecting default shared_buffers ... 128MB

selecting default time zone ... Etc/UTC

creating configuration files ... ok

running bootstrap script ... ok

performing post-bootstrap initialization ... ok

syncing data to disk ... ok

initdb: warning: enabling "trust" authentication for local connections

You can change this by editing pg_hba.conf or using the option -A, or

--auth-local and --auth-host, the next time you run initdb.

Success. You can now start the database server using:

    pg_ctl -D /var/lib/postgresql/data -l logfile start

waiting for server to start.......2025-05-19 10:33:56.289 UTC [49] LOG:  redirecting log output to logging collector process

2025-05-19 10:33:56.289 UTC [49] HINT:  Future log output will appear in directory "log".

...... done

server started

CREATE DATABASE

/usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*

waiting for server to shut down............ done

server stopped

PostgreSQL init process complete; ready for start up.

2025-05-19 10:34:36.489 UTC [1] LOG:  redirecting log output to logging collector process

2025-05-19 10:34:36.489 UTC [1] HINT:  Future log output will appear in directory "log".

The files belonging to this database system will be owned by user "postgres".

This user must also own the server process.

The database cluster will be initialized with locale "en_US.utf8".

The default database encoding has accordingly been set to "UTF8".

The default text search configuration will be set to "english".

Data page checksums are enabled.

fixing permissions on existing directory /var/lib/postgresql/data ... ok

creating subdirectories ... ok

selecting dynamic shared memory implementation ... posix

selecting default max_connections ... 100

selecting default shared_buffers ... 128MB

selecting default time zone ... Etc/UTC

creating configuration files ... ok

running bootstrap script ... ok

performing post-bootstrap initialization ... ok

syncing data to disk ... ok

initdb: warning: enabling "trust" authentication for local connections

You can change this by editing pg_hba.conf or using the option -A, or

--auth-local and --auth-host, the next time you run initdb.

Success. You can now start the database server using:

    pg_ctl -D /var/lib/postgresql/data -l logfile start

waiting for server to start.......2025-05-19 10:33:56.289 UTC [49] LOG:  redirecting log output to logging collector process

2025-05-19 10:33:56.289 UTC [49] HINT:  Future log output will appear in directory "log".

...... done

server started

CREATE DATABASE

/usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*

waiting for server to shut down............ done

server stopped

PostgreSQL init process complete; ready for start up.

2025-05-19 10:34:36.489 UTC [1] LOG:  redirecting log output to logging collector process

2025-05-19 10:34:36.489 UTC [1] HINT:  Future log output will appear in directory "log".

113 replies

IImmich

•Created by Mai on 5/18/2025 in #help-desk-support

System crashed and corrupted multiple files

The redis looks fine too:

1:M 19 May 2025 10:33:37.018 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.

1:M 19 May 2025 10:33:37.018 * oO0OoO0OoO0Oo Valkey is starting oO0OoO0OoO0Oo

1:M 19 May 2025 10:33:37.018 * Valkey version=8.1.0, bits=64, commit=00000000, modified=0, pid=1, just started

1:M 19 May 2025 10:33:37.018 # Warning: no config file specified, using the default config. In order to specify a config file use valkey-server /path/to/valkey.conf

1:M 19 May 2025 10:33:37.019 * monotonic clock: POSIX clock_gettime

1:M 19 May 2025 10:33:37.020 * Running mode=standalone, port=6379.

1:M 19 May 2025 10:33:37.020 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.

1:M 19 May 2025 10:33:37.020 * Server initialized

1:M 19 May 2025 10:33:37.020 * Ready to accept connections tcp

1:M 19 May 2025 10:42:49.812 * 100 changes in 300 seconds. Saving...

1:M 19 May 2025 10:42:49.813 * Background saving started by pid 137

137:C 19 May 2025 10:42:50.877 * DB saved on disk

137:C 19 May 2025 10:42:50.877 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB

1:M 19 May 2025 10:42:50.921 * Background saving terminated with success

1:M 19 May 2025 10:50:51.841 * 100 changes in 300 seconds. Saving...

1:M 19 May 2025 10:50:51.841 * Background saving started by pid 245

245:C 19 May 2025 10:50:54.448 * DB saved on disk

245:C 19 May 2025 10:50:54.449 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB

1:M 19 May 2025 10:50:54.455 * Background saving terminated with success

1:M 19 May 2025 10:57:24.702 * 100 changes in 300 seconds. Saving...

1:M 19 May 2025 10:57:24.702 * Background saving started by pid 331

331:C 19 May 2025 10:57:29.352 * DB saved on disk

331:C 19 May 2025 10:57:29.353 * Fork CoW for RDB: current 1 MB, peak 1 MB, average 1 MB

1:M 19 May 2025 10:57:29.427 * Background saving terminated with success

1:M 19 May 2025 11:05:49.920 * 100 changes in 300 seconds. Saving...

1:M 19 May 2025 11:05:49.920 * Background saving started by pid 446

446:C 19 May 2025 11:05:52.758 * DB saved on disk

446:C 19 May 2025 11:05:52.759 * Fork CoW for RDB: current 1 MB, peak 1 MB, average 0 MB

1:M 19 May 2025 11:05:52.837 * Background saving terminated with success

1:M 19 May 2025 11:12:49.906 * 100 changes in 300 seconds. Saving...

1:M 19 May 2025 11:12:49.906 * Background saving started by pid 537

537:C 19 May 2025 11:12:50.982 * DB saved on disk

537:C 19 May 2025 11:12:50.983 * Fork CoW for RDB: current 1 MB, peak 1 MB, average 0 MB

1:M 19 May 2025 11:12:51.013 * Background saving terminated with success

1:M 19 May 2025 10:33:37.018 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.

1:M 19 May 2025 10:33:37.018 * oO0OoO0OoO0Oo Valkey is starting oO0OoO0OoO0Oo

1:M 19 May 2025 10:33:37.018 * Valkey version=8.1.0, bits=64, commit=00000000, modified=0, pid=1, just started

1:M 19 May 2025 10:33:37.018 # Warning: no config file specified, using the default config. In order to specify a config file use valkey-server /path/to/valkey.conf

1:M 19 May 2025 10:33:37.019 * monotonic clock: POSIX clock_gettime

1:M 19 May 2025 10:33:37.020 * Running mode=standalone, port=6379.

1:M 19 May 2025 10:33:37.020 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.

1:M 19 May 2025 10:33:37.020 * Server initialized

1:M 19 May 2025 10:33:37.020 * Ready to accept connections tcp

1:M 19 May 2025 10:42:49.812 * 100 changes in 300 seconds. Saving...

1:M 19 May 2025 10:42:49.813 * Background saving started by pid 137

137:C 19 May 2025 10:42:50.877 * DB saved on disk

137:C 19 May 2025 10:42:50.877 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB

1:M 19 May 2025 10:42:50.921 * Background saving terminated with success

1:M 19 May 2025 10:50:51.841 * 100 changes in 300 seconds. Saving...

1:M 19 May 2025 10:50:51.841 * Background saving started by pid 245

245:C 19 May 2025 10:50:54.448 * DB saved on disk

245:C 19 May 2025 10:50:54.449 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB

1:M 19 May 2025 10:50:54.455 * Background saving terminated with success

1:M 19 May 2025 10:57:24.702 * 100 changes in 300 seconds. Saving...

1:M 19 May 2025 10:57:24.702 * Background saving started by pid 331

331:C 19 May 2025 10:57:29.352 * DB saved on disk

331:C 19 May 2025 10:57:29.353 * Fork CoW for RDB: current 1 MB, peak 1 MB, average 1 MB

1:M 19 May 2025 10:57:29.427 * Background saving terminated with success

1:M 19 May 2025 11:05:49.920 * 100 changes in 300 seconds. Saving...

1:M 19 May 2025 11:05:49.920 * Background saving started by pid 446

446:C 19 May 2025 11:05:52.758 * DB saved on disk

446:C 19 May 2025 11:05:52.759 * Fork CoW for RDB: current 1 MB, peak 1 MB, average 0 MB

1:M 19 May 2025 11:05:52.837 * Background saving terminated with success

1:M 19 May 2025 11:12:49.906 * 100 changes in 300 seconds. Saving...

1:M 19 May 2025 11:12:49.906 * Background saving started by pid 537

537:C 19 May 2025 11:12:50.982 * DB saved on disk

537:C 19 May 2025 11:12:50.983 * Fork CoW for RDB: current 1 MB, peak 1 MB, average 0 MB

1:M 19 May 2025 11:12:51.013 * Background saving terminated with success

113 replies

IImmich

•Created by Mai on 5/18/2025 in #help-desk-support

System crashed and corrupted multiple files

For immich_server, all the logs are green, I don't see any errors:

113 replies

IImmich

•Created by Mai on 5/18/2025 in #help-desk-support

System crashed and corrupted multiple files

Thanks for replying so quickly! nope, I didn't mount external library

113 replies

IImmich

•Created by Mai on 5/18/2025 in #help-desk-support

System crashed and corrupted multiple files

should I upload my compose and eni variables here? but everything is just simply copy and paste from official docs

113 replies

IImmich

•Created by Mai on 5/18/2025 in #help-desk-support

System crashed and corrupted multiple files

@Mraedis Hello Mraedis, I can really use some help here! I build a fresh one using the compose and env. from immich official guide, but all the uploads are broken. I rebuilt immich multiple times yesterday trying to fix the eternal library mount, everytime I rebuilt, I always uploaded a few photos to make sure immich is functioning properly, and it always worked well. So right now I am scratching my head here, I haven't done anything differently. I've also tried force refresh/using a different brower, tear down everything and make sure it is a fresh rebuild, but it is still broken.

113 replies

IImmich

•Created by StanRex on 4/15/2025 in #help-desk-support

Broken Immich install with PGSQL exiting

Hello, sorry to jump into your discussion! I encountered similar problem like yours. I've included user: ${UID}:${GID} in every section for a fresh rebuild, but it won't start. I am hosting on Synology NAS, deploying through portainer. The reason I wanted to include UID&GID is becuase I am hoping to bind mount some existing photos on my NAS, I've tried adding a path in the volume for bind mount, immich can validate the path, but the photo won't show up, I figured it is some permission issue.

86 replies

IImmich

•Created by Mai on 5/18/2025 in #help-desk-support

System crashed and corrupted multiple files

thanks Mraedis！will check it out!

113 replies

Gaming

Programming