Thunder Comments - Answer Overflow

checklist for myself: - set sane memory limits for the containers... just in case - investigate cpu_shares and cpuset.. removing the settings / or alternatively leave a core completely free for the system and test that

39 replies

IImmich

•Created by Thunder on 5/11/2025 in #help-desk-support

NAS completely froze overnight

hm yeah that was me trying to get the system to be more responsive when immich is hammering it - my first crash was when I didn't add those settings and they managed to reduce CPU usage a bit and make the system more responsive again while ingesting images

39 replies

IImmich

•Created by Thunder on 5/11/2025 in #help-desk-support

NAS completely froze overnight

39 replies

IImmich

•Created by Thunder on 5/11/2025 in #help-desk-support

NAS completely froze overnight

39 replies

IImmich

•Created by Thunder on 5/11/2025 in #help-desk-support

NAS completely froze overnight

cpu also seems alright to me hm..

39 replies

IImmich

•Created by Thunder on 5/11/2025 in #help-desk-support

NAS completely froze overnight

I see, thanks. I'll look into it - though from the history of the resource monitor RAM usage doesn't seem to be very high though

39 replies

IImmich

•Created by Thunder on 5/11/2025 in #help-desk-support

NAS completely froze overnight

the latest logs look like this:

2025-05-11 08:27:05.721 UTC [1] LOG:  starting PostgreSQL 14.10 (Debian 14.10-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-05-11 08:27:05.722 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2025-05-11 08:27:05.722 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2025-05-11 08:27:05.758 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-05-11 08:27:05.780 UTC [27] LOG:  database system was interrupted; last known up at 2025-05-11 01:42:26 UTC
[2025-05-11T08:27:05Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/100440".
[2025-05-11T08:27:05Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/100442".
[2025-05-11T08:27:05Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/100440/segments/66016ac2-6cd7-4f79-95f9-6b119b043678".
2025-05-11 08:27:05.931 UTC [27] LOG:  database system was not properly shut down; automatic recovery in progress
2025-05-11 08:27:05.981 UTC [27] LOG:  redo starts at 1/1122D1E0
2025-05-11 08:27:05.981 UTC [27] LOG:  invalid record length at 1/1122D2C8: wanted 24, got 0
2025-05-11 08:27:05.981 UTC [27] LOG:  redo done at 1/1122D290 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2025-05-11 08:27:06.276 UTC [1] LOG:  database system is ready to accept connections
[2025-05-11T08:27:06Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/100442/segments/f4744856-cfdc-40b9-bc44-7ad70a845bee".

2025-05-11 08:27:05.721 UTC [1] LOG:  starting PostgreSQL 14.10 (Debian 14.10-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-05-11 08:27:05.722 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2025-05-11 08:27:05.722 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2025-05-11 08:27:05.758 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-05-11 08:27:05.780 UTC [27] LOG:  database system was interrupted; last known up at 2025-05-11 01:42:26 UTC
[2025-05-11T08:27:05Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/100440".
[2025-05-11T08:27:05Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/100442".
[2025-05-11T08:27:05Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/100440/segments/66016ac2-6cd7-4f79-95f9-6b119b043678".
2025-05-11 08:27:05.931 UTC [27] LOG:  database system was not properly shut down; automatic recovery in progress
2025-05-11 08:27:05.981 UTC [27] LOG:  redo starts at 1/1122D1E0
2025-05-11 08:27:05.981 UTC [27] LOG:  invalid record length at 1/1122D2C8: wanted 24, got 0
2025-05-11 08:27:05.981 UTC [27] LOG:  redo done at 1/1122D290 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2025-05-11 08:27:06.276 UTC [1] LOG:  database system is ready to accept connections
[2025-05-11T08:27:06Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/100442/segments/f4744856-cfdc-40b9-bc44-7ad70a845bee".

39 replies

IImmich

•Created by Thunder on 5/11/2025 in #help-desk-support

NAS completely froze overnight

39 replies

IImmich

•Created by Thunder on 5/11/2025 in #help-desk-support

NAS completely froze overnight

seems like some are empty there

39 replies

IImmich

•Created by Thunder on 5/11/2025 in #help-desk-support

NAS completely froze overnight

yeah mean the ones in /immich/postgres/log folder?

39 replies

IImmich

•Created by Thunder on 5/11/2025 in #help-desk-support

NAS completely froze overnight

39 replies

IImmich

•Created by Thunder on 5/11/2025 in #help-desk-support

NAS completely froze overnight

# 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.

39 replies

IImmich

•Created by Thunder on 5/11/2025 in #help-desk-support

NAS completely froze overnight

also redis has a warning in the logs when booting up?

2025/05/11 10:27:05    stdout    1:M 11 May 2025 08:27:05.161 * Server initialized
2025/05/11 10:27:05    stdout    1:M 11 May 2025 08:27:05.161 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
2025/05/11 10:27:05    stdout    1:M 11 May 2025 08:27:05.161 * Running mode=standalone, port=6379.
2025/05/11 10:27:05    stdout    1:M 11 May 2025 08:27:05.160 * monotonic clock: POSIX clock_gettime
2025/05/11 10:27:05    stdout    1:M 11 May 2025 08:27:05.159 # Warning: no config file specified, using the default config. In order to specify a config file use valkey-server /path/to/valkey.conf
2025/05/11 10:27:05    stdout    1:M 11 May 2025 08:27:05.159 * Valkey version=8.1.0, bits=64, commit=00000000, modified=0, pid=1, just started
2025/05/11 10:27:05    stdout    1:M 11 May 2025 08:27:05.159 * oO0OoO0OoO0Oo Valkey is starting oO0OoO0OoO0Oo
2025/05/11 10:27:05    stdout    1:M 11 May 2025 08:27:05.159 # 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.
2025/05/11 04:40:57    stdout    1:M 11 May 2025 02:40:57.152 * Background saving terminated with success
2025/05/11 04:40:57    stdout    6278:C 11 May 2025 02:40:57.082 * Fork CoW for RDB: current 1 MB, peak 1 MB, average 1 MB
2025/05/11 04:40:57    stdout    6278:C 11 May 2025 02:40:57.082 * DB saved on disk
2025/05/11 04:40:57    stdout    1:M 11 May 2025 02:40:57.051 * Background saving started by pid 6278
2025/05/11 04:40:57    stdout    1:M 11 May 2025 02:40:57.051 * 100 changes in 300 seconds. Saving...

2025/05/11 10:27:05    stdout    1:M 11 May 2025 08:27:05.161 * Server initialized
2025/05/11 10:27:05    stdout    1:M 11 May 2025 08:27:05.161 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
2025/05/11 10:27:05    stdout    1:M 11 May 2025 08:27:05.161 * Running mode=standalone, port=6379.
2025/05/11 10:27:05    stdout    1:M 11 May 2025 08:27:05.160 * monotonic clock: POSIX clock_gettime
2025/05/11 10:27:05    stdout    1:M 11 May 2025 08:27:05.159 # Warning: no config file specified, using the default config. In order to specify a config file use valkey-server /path/to/valkey.conf
2025/05/11 10:27:05    stdout    1:M 11 May 2025 08:27:05.159 * Valkey version=8.1.0, bits=64, commit=00000000, modified=0, pid=1, just started
2025/05/11 10:27:05    stdout    1:M 11 May 2025 08:27:05.159 * oO0OoO0OoO0Oo Valkey is starting oO0OoO0OoO0Oo
2025/05/11 10:27:05    stdout    1:M 11 May 2025 08:27:05.159 # 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.
2025/05/11 04:40:57    stdout    1:M 11 May 2025 02:40:57.152 * Background saving terminated with success
2025/05/11 04:40:57    stdout    6278:C 11 May 2025 02:40:57.082 * Fork CoW for RDB: current 1 MB, peak 1 MB, average 1 MB
2025/05/11 04:40:57    stdout    6278:C 11 May 2025 02:40:57.082 * DB saved on disk
2025/05/11 04:40:57    stdout    1:M 11 May 2025 02:40:57.051 * Background saving started by pid 6278
2025/05/11 04:40:57    stdout    1:M 11 May 2025 02:40:57.051 * 100 changes in 300 seconds. Saving...

39 replies

IImmich

•Created by Thunder on 5/11/2025 in #help-desk-support

NAS completely froze overnight

I never really had issues with this NAS, but now with immich I managed to crash it twice

39 replies

IImmich

•Created by Thunder on 5/11/2025 in #help-desk-support

NAS completely froze overnight

massively overloaded could be the case tbh

39 replies

IImmich

•Created by Thunder on 5/11/2025 in #help-desk-support

NAS completely froze overnight

can you explain what you mean with "check your memory limits on immich to make sure it doesn't crash your system."?

maybe you need more memory .

unfortunately 8GB is the max officially supported amount of RAM for this NAS

39 replies

Gaming

Programming