[EFAULT] Failed 'up' action for 'immich' app, please check /var/log/app_lifecycle.log

[lostandjcfound]

Hello all, I am new to truenas and i thought i had figured a few things out… but i was wrong

I have had immich up and running and working great for a few months now, BUT stupid me had to change something

I tried to changed where where it was backed up to, once i changed that to a new data set where I could have access to it with SMB the app will not stat back now, i tried setting the back up location back to what it was before but it will not let me.

I have the permissions set to everyone on the data set that i was try to use,

this is what its says when I try and start the app

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/middlewared/job.py", line 509, in run
    await self.future
  File "/usr/lib/python3/dist-packages/middlewared/job.py", line 556, in __run_body
    rv = await self.middleware.run_in_thread(self.method, *args)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1367, in run_in_thread
    return await self.run_in_executor(io_thread_pool_executor, method, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1364, in run_in_executor
    return await loop.run_in_executor(pool, functools.partial(method, *args, **kwargs))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/middlewared/schema/processor.py", line 183, in nf
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/middlewared/schema/processor.py", line 55, in nf
    res = f(*args, **kwargs)
          ^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/middlewared/plugins/apps/app_scale.py", line 51, in start
    compose_action(app_name, app_config['version'], 'up', force_recreate=True, remove_orphans=True)
  File "/usr/lib/python3/dist-packages/middlewared/plugins/apps/compose_utils.py", line 57, in compose_action
    raise CallError(
middlewared.service_exception.CallError: [EFAULT] Failed 'up' action for 'immich' app, please check /var/log/app_lifecycle.log for more details

I know it probable something super easy but i have read and read watched videos and can not figure it out

I would just uninstall and reinstall it but I have pictures that I had not yet backed up

[lostandjcfound]

Also I do not know how to get to the /var/log/app_lifecycle.log

[Nordlicht-13]

I had the same problem. Was somehow a problem with the postgres-DB. I migrated immich to dockge. Now it’s running without any problems.
When you move immich to dockge and want to restore your backup, you have to change the image of the postgres-DB.

In the compose.yml you have to change this:

    container_name: immich_postgres
    image: tensorchord/pgvecto-rs:pg16-v0.2.0
    # image: docker.io/tensorchord/pgvecto-rs:pg14-v0.2.0@sha256:90724186f0a3517cf6914295b5ab410db9ce23190a2d9d0b9dd6463e3fa298f0
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
      POSTGRES_INITDB_ARGS: --data-checksums```

[Nordlicht-13]

@lostandjcfound

Also I do not know how to get to the /var/log/app_lifecycle.log

You can do a cat on the shell.

$ cat /var/log/app_lifecycle.log

[lostandjcfound]

Thank you for your fast response, I have never messed with any of that, what do I need to change it to and which lines do I need to change?

[Nordlicht-13]

You just have to insert this line:
image: tensorchord/pgvecto-rs:pg16-v0.2.0
and comment out this line:
image: docker.io/tensorchord/pgvecto-rs:pg14-v0.2.0@sha256:90724186f0a3517cf6914295b5ab410db9ce23190a2d9d0b9dd6463e3fa298f0

Then you can manually restore as shown in the immich docs:

Backup and Restore | Immich

[lostandjcfound]

Thank you so much!!! Going to try to do this when I get home!

[DjP-iX]

@Nordlicht-13

I had the same problem. Was somehow a problem with the postgres-DB. I migrated immich to dockge. Now it’s running without any problems.

Glad you got it working with dockge, but FYI the original issue was almost definitely a common permissions problem with postgres datasets. I don’t know how long ago this happened but there’s now an automatic permissions checkbox for PG host paths because of this.

@lostandjcfound if you run cat /var/log/app_lifecycle.log from the shell, like @Nordlicht-13 suggested, then paste the logs here, we can probably figure out the issue.

[lostandjcfound]

Thank you! I will do that as soon as I get home, I’m trying to learn all this but it’s a lot to take in just starting, only ever used windows, this has been my first attempt with any thing else.

[Nordlicht-13]

@DjP-iX

FYI the original issue was almost definitely a common permissions problem with postgres datasets.

It was running fine, didn’t came up again after an update.
I had simmilar problems with nextcloud and paperless that are also using databases. I moved tose now to dockge.

[lostandjcfound]

@DjP-iX

cat /var/log/app_lifecycle.log

[2025/01/09 13:56:09] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘immich’ app: Network ix-immich_default Creating
Network ix-immich_default Created
Container ix-immich-permissions-1 Creating
time=“2025-01-09T13:56:02-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
time=“2025-01-09T13:56:02-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
Container ix-immich-permissions-1 Created
Container ix-immich-redis-1 Creating
Container ix-immich-machine-learning-1 Creating
Container ix-immich-pgvecto-1 Creating
Container ix-immich-redis-1 Created
Container ix-immich-machine-learning-1 Created
Container ix-immich-pgvecto-1 Created
Container ix-immich-server-1 Creating
Container ix-immich-server-1 Created
Container ix-immich-permissions-1 Starting
Container ix-immich-permissions-1 Started
Container ix-immich-permissions-1 Waiting
Container ix-immich-permissions-1 Waiting
Container ix-immich-permissions-1 Waiting
Container ix-immich-permissions-1 Exited
Container ix-immich-machine-learning-1 Starting
Container ix-immich-permissions-1 Exited
Container ix-immich-redis-1 Starting
Container ix-immich-permissions-1 Exited
Container ix-immich-pgvecto-1 Starting
Container ix-immich-pgvecto-1 Started
Container ix-immich-machine-learning-1 Started
Container ix-immich-redis-1 Started
Container ix-immich-machine-learning-1 Waiting
Container ix-immich-permissions-1 Waiting
Container ix-immich-pgvecto-1 Waiting
Container ix-immich-redis-1 Waiting
Container ix-immich-permissions-1 Exited
Container ix-immich-pgvecto-1 Error
Container ix-immich-redis-1 Healthy
Container ix-immich-machine-learning-1 Healthy
dependency failed to start: container ix-immich-pgvecto-1 is unhealthy

[2025/01/09 13:58:54] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘immich’ app: Network ix-immich_default Creating
Network ix-immich_default Created
Container ix-immich-permissions-1 Creating
time=“2025-01-09T13:58:46-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
time=“2025-01-09T13:58:46-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
Container ix-immich-permissions-1 Created
Container ix-immich-machine-learning-1 Creating
Container ix-immich-redis-1 Creating
Container ix-immich-pgvecto-1 Creating
Container ix-immich-redis-1 Created
Container ix-immich-machine-learning-1 Created
Container ix-immich-pgvecto-1 Created
Container ix-immich-server-1 Creating
Container ix-immich-server-1 Created
Container ix-immich-permissions-1 Starting
Container ix-immich-permissions-1 Started
Container ix-immich-permissions-1 Waiting
Container ix-immich-permissions-1 Waiting
Container ix-immich-permissions-1 Waiting
Container ix-immich-permissions-1 Exited
Container ix-immich-redis-1 Starting
Container ix-immich-permissions-1 Exited
Container ix-immich-machine-learning-1 Starting
Container ix-immich-permissions-1 Exited
Container ix-immich-pgvecto-1 Starting
Container ix-immich-machine-learning-1 Started
Container ix-immich-redis-1 Started
Container ix-immich-pgvecto-1 Started
Container ix-immich-machine-learning-1 Waiting
Container ix-immich-permissions-1 Waiting
Container ix-immich-pgvecto-1 Waiting
Container ix-immich-redis-1 Waiting
Container ix-immich-permissions-1 Exited
Container ix-immich-pgvecto-1 Error
Container ix-immich-redis-1 Healthy
Container ix-immich-machine-learning-1 Healthy
dependency failed to start: container ix-immich-pgvecto-1 is unhealthy

[2025/01/09 14:00:44] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘immich’ app: Network ix-immich_default Creating
Network ix-immich_default Created
Container ix-immich-permissions-1 Creating
time=“2025-01-09T14:00:37-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
time=“2025-01-09T14:00:37-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
Container ix-immich-permissions-1 Created
Container ix-immich-machine-learning-1 Creating
Container ix-immich-redis-1 Creating
Container ix-immich-pgvecto-1 Creating
Container ix-immich-pgvecto-1 Created
Container ix-immich-redis-1 Created
Container ix-immich-machine-learning-1 Created
Container ix-immich-server-1 Creating
Container ix-immich-server-1 Created
Container ix-immich-permissions-1 Starting
Container ix-immich-permissions-1 Started
Container ix-immich-permissions-1 Waiting
Container ix-immich-permissions-1 Waiting
Container ix-immich-permissions-1 Waiting
Container ix-immich-permissions-1 Exited
Container ix-immich-machine-learning-1 Starting
Container ix-immich-permissions-1 Exited
Container ix-immich-permissions-1 Exited
Container ix-immich-redis-1 Starting
Container ix-immich-pgvecto-1 Starting
Container ix-immich-pgvecto-1 Started
Container ix-immich-machine-learning-1 Started
Container ix-immich-redis-1 Started
Container ix-immich-permissions-1 Waiting
Container ix-immich-pgvecto-1 Waiting
Container ix-immich-redis-1 Waiting
Container ix-immich-machine-learning-1 Waiting
Container ix-immich-permissions-1 Exited
Container ix-immich-pgvecto-1 Error
Container ix-immich-redis-1 Healthy
Container ix-immich-machine-learning-1 Healthy
dependency failed to start: container ix-immich-pgvecto-1 is unhealthy

[2025/01/09 14:02:43] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘immich’ app: Network ix-immich_default Creating
Network ix-immich_default Created
Container ix-immich-permissions-1 Creating
time=“2025-01-09T14:02:35-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
time=“2025-01-09T14:02:35-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
Container ix-immich-permissions-1 Created
Container ix-immich-redis-1 Creating
Container ix-immich-machine-learning-1 Creating
Container ix-immich-pgvecto-1 Creating
Container ix-immich-machine-learning-1 Created
Container ix-immich-redis-1 Created
Container ix-immich-pgvecto-1 Created
Container ix-immich-server-1 Creating
Container ix-immich-server-1 Created
Container ix-immich-permissions-1 Starting
Container ix-immich-permissions-1 Started
Container ix-immich-permissions-1 Waiting
Container ix-immich-permissions-1 Waiting
Container ix-immich-permissions-1 Waiting
Container ix-immich-permissions-1 Exited
Container ix-immich-redis-1 Starting
Container ix-immich-permissions-1 Exited
Container ix-immich-pgvecto-1 Starting
Container ix-immich-permissions-1 Exited
Container ix-immich-machine-learning-1 Starting
Container ix-immich-pgvecto-1 Started
Container ix-immich-machine-learning-1 Started
Container ix-immich-redis-1 Started
Container ix-immich-redis-1 Waiting
Container ix-immich-machine-learning-1 Waiting
Container ix-immich-permissions-1 Waiting
Container ix-immich-pgvecto-1 Waiting
Container ix-immich-permissions-1 Exited
Container ix-immich-pgvecto-1 Error
Container ix-immich-redis-1 Healthy
Container ix-immich-machine-learning-1 Healthy
dependency failed to start: container ix-immich-pgvecto-1 is unhealthy

[2025/01/09 14:03:03] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘immich’ app: Network ix-immich_default Creating
Network ix-immich_default Created
Container ix-immich-permissions-1 Creating
time=“2025-01-09T14:02:55-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
time=“2025-01-09T14:02:55-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
Container ix-immich-permissions-1 Created
Container ix-immich-pgvecto-1 Creating
Container ix-immich-redis-1 Creating
Container ix-immich-machine-learning-1 Creating
Container ix-immich-redis-1 Created
Container ix-immich-pgvecto-1 Created
Container ix-immich-machine-learning-1 Created
Container ix-immich-server-1 Creating
Container ix-immich-server-1 Created
Container ix-immich-permissions-1 Starting
Container ix-immich-permissions-1 Started
Container ix-immich-permissions-1 Waiting
Container ix-immich-permissions-1 Waiting
Container ix-immich-permissions-1 Waiting
Container ix-immich-permissions-1 Exited
Container ix-immich-redis-1 Starting
Container ix-immich-permissions-1 Exited
Container ix-immich-machine-learning-1 Starting
Container ix-immich-permissions-1 Exited
Container ix-immich-pgvecto-1 Starting
Container ix-immich-pgvecto-1 Started
Container ix-immich-machine-learning-1 Started
Container ix-immich-redis-1 Started
Container ix-immich-pgvecto-1 Waiting
Container ix-immich-redis-1 Waiting
Container ix-immich-machine-learning-1 Waiting
Container ix-immich-permissions-1 Waiting
Container ix-immich-permissions-1 Exited
Container ix-immich-pgvecto-1 Error
Container ix-immich-redis-1 Healthy
Container ix-immich-machine-learning-1 Healthy
dependency failed to start: container ix-immich-pgvecto-1 is unhealthy

[2025/01/09 14:09:54] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘immich’ app: Network ix-immich_default Creating
Network ix-immich_default Created
Container ix-immich-permissions-1 Creating
time=“2025-01-09T14:09:46-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
time=“2025-01-09T14:09:46-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
Container ix-immich-permissions-1 Created
Container ix-immich-redis-1 Creating
Container ix-immich-machine-learning-1 Creating
Container ix-immich-pgvecto-1 Creating
Container ix-immich-pgvecto-1 Created
Container ix-immich-redis-1 Created
Container ix-immich-machine-learning-1 Created
Container ix-immich-server-1 Creating
Container ix-immich-server-1 Created
Container ix-immich-permissions-1 Starting
Container ix-immich-permissions-1 Started
Container ix-immich-permissions-1 Waiting
Container ix-immich-permissions-1 Waiting
Container ix-immich-permissions-1 Waiting
Container ix-immich-permissions-1 Exited
Container ix-immich-pgvecto-1 Starting
Container ix-immich-permissions-1 Exited
Container ix-immich-permissions-1 Exited
Container ix-immich-machine-learning-1 Starting
Container ix-immich-redis-1 Starting
Container ix-immich-redis-1 Started
Container ix-immich-pgvecto-1 Started
Container ix-immich-machine-learning-1 Started
Container ix-immich-permissions-1 Waiting
Container ix-immich-pgvecto-1 Waiting
Container ix-immich-redis-1 Waiting
Container ix-immich-machine-learning-1 Waiting
Container ix-immich-permissions-1 Exited
Container ix-immich-pgvecto-1 Error
Container ix-immich-redis-1 Healthy
Container ix-immich-machine-learning-1 Healthy
dependency failed to start: container ix-immich-pgvecto-1 is unhealthy

[2025/01/10 13:19:41] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘immich’ app: Network ix-immich_default Creating
Network ix-immich_default Created
Container ix-immich-permissions-1 Creating
time=“2025-01-10T13:19:33-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
time=“2025-01-10T13:19:33-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
Container ix-immich-permissions-1 Created
Container ix-immich-machine-learning-1 Creating
Container ix-immich-pgvecto-1 Creating
Container ix-immich-redis-1 Creating
Container ix-immich-redis-1 Created
Container ix-immich-pgvecto-1 Created
Container ix-immich-machine-learning-1 Created
Container ix-immich-server-1 Creating
Container ix-immich-server-1 Created
Container ix-immich-permissions-1 Starting
Container ix-immich-permissions-1 Started
Container ix-immich-permissions-1 Waiting
Container ix-immich-permissions-1 Waiting
Container ix-immich-permissions-1 Waiting
Container ix-immich-permissions-1 Exited
Container ix-immich-pgvecto-1 Starting
Container ix-immich-permissions-1 Exited
Container ix-immich-redis-1 Starting
Container ix-immich-permissions-1 Exited
Container ix-immich-machine-learning-1 Starting
Container ix-immich-redis-1 Started
Container ix-immich-pgvecto-1 Started
Container ix-immich-machine-learning-1 Started
Container ix-immich-machine-learning-1 Waiting
Container ix-immich-permissions-1 Waiting
Container ix-immich-pgvecto-1 Waiting
Container ix-immich-redis-1 Waiting
Container ix-immich-permissions-1 Exited
Container ix-immich-redis-1 Healthy
Container ix-immich-pgvecto-1 Error
Container ix-immich-machine-learning-1 Healthy
dependency failed to start: container ix-immich-pgvecto-1 is unhealthy

[DjP-iX]

@lostandjcfound

ix-immich-pgvecto-1 is unhealthy

Ok so what do you have configured under Postgres Data Storage?

[lostandjcfound]

ixVolume (Dataset created automatically by the system)

[lostandjcfound]

I didn’t change any of that, only Immich Backups Storage

[DjP-iX]

hmm ok I wouldn’t expect that to prevent pgvector from starting, but maybe it’s looking for files from the old backups dataset that are not there in the new one?

So I’m following along now on a test system. It looks like once you’ve already installed using ixVolumes and then go back in to edit the config, it locks every storage location except for Immich Backups Storage. And then if you change Backups to a host path it won’t let you change back to ixVolume. That doesn’t seem right to me. I’d suggest a bug report first and see where that gets us. You can use the Report a Bug link at the top of this page.

[lostandjcfound]

That is exactly what it did, it will not let me change it back

Thank you so much!!!

[lostandjcfound]

just submitted a report

[lostandjcfound]

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-01-18 10:26:25.924 CST [1] LOG: starting PostgreSQL 15.5 (Debian 15.5-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-01-18 10:26:25.925 CST [1] LOG: listening on IPv4 address “0.0.0.0”, port 5432
2025-01-18 10:26:25.925 CST [1] LOG: listening on IPv6 address “::”, port 5432
2025-01-18 10:26:25.926 CST [1] LOG: listening on Unix socket “/var/run/postgresql/.s.PGSQL.5432”
2025-01-18 10:26:26.117 CST [17] LOG: database system shutdown was interrupted; last known up at 2025-01-07 19:23:44 CST
[2025-01-18T16:26:26Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17591”.
[2025-01-18T16:26:26Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17347”.
[2025-01-18T16:26:26Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17591/segments/ebf2b026-4dcd-4208-8528-170b829d4de9”.
2025-01-18 10:26:26.229 CST [17] LOG: invalid primary checkpoint record
2025-01-18 10:26:26.230 CST [17] PANIC: could not locate a valid checkpoint record
[2025-01-18T16:26:26Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17347/segments/0d9155ad-dcbc-468f-bcbf-d6e7d36ad5d8”.
2025-01-18 10:26:27.839 CST [1] LOG: startup process (PID 17) was terminated by signal 6: Aborted
2025-01-18 10:26:27.839 CST [1] LOG: aborting startup due to startup process failure
2025-01-18 10:26:27.840 CST [1] LOG: database system is shut down

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-01-18 10:26:28.265 CST [1] LOG: starting PostgreSQL 15.5 (Debian 15.5-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-01-18 10:26:28.266 CST [1] LOG: listening on IPv4 address “0.0.0.0”, port 5432
2025-01-18 10:26:28.266 CST [1] LOG: listening on IPv6 address “::”, port 5432
2025-01-18 10:26:28.266 CST [1] LOG: listening on Unix socket “/var/run/postgresql/.s.PGSQL.5432”
2025-01-18 10:26:28.269 CST [15] LOG: database system shutdown was interrupted; last known up at 2025-01-07 19:23:44 CST
[2025-01-18T16:26:28Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17591”.
[2025-01-18T16:26:28Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17347”.
[2025-01-18T16:26:28Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17591/segments/ebf2b026-4dcd-4208-8528-170b829d4de9”.
[2025-01-18T16:26:28Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17347/segments/0d9155ad-dcbc-468f-bcbf-d6e7d36ad5d8”.
2025-01-18 10:26:28.288 CST [15] LOG: invalid primary checkpoint record
2025-01-18 10:26:28.288 CST [15] PANIC: could not locate a valid checkpoint record
2025-01-18 10:26:29.856 CST [1] LOG: startup process (PID 15) was terminated by signal 6: Aborted
2025-01-18 10:26:29.856 CST [1] LOG: aborting startup due to startup process failure
2025-01-18 10:26:29.858 CST [1] LOG: database system is shut down
truenas_admin@truenas[~]$ sudo docker logs ix-immich-pgvecto-1 -f

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-01-18 10:26:25.924 CST [1] LOG: starting PostgreSQL 15.5 (Debian 15.5-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-01-18 10:26:25.925 CST [1] LOG: listening on IPv4 address “0.0.0.0”, port 5432
2025-01-18 10:26:25.925 CST [1] LOG: listening on IPv6 address “::”, port 5432
2025-01-18 10:26:25.926 CST [1] LOG: listening on Unix socket “/var/run/postgresql/.s.PGSQL.5432”
2025-01-18 10:26:26.117 CST [17] LOG: database system shutdown was interrupted; last known up at 2025-01-07 19:23:44 CST
[2025-01-18T16:26:26Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17591”.
[2025-01-18T16:26:26Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17347”.
[2025-01-18T16:26:26Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17591/segments/ebf2b026-4dcd-4208-8528-170b829d4de9”.
2025-01-18 10:26:26.229 CST [17] LOG: invalid primary checkpoint record
2025-01-18 10:26:26.230 CST [17] PANIC: could not locate a valid checkpoint record
[2025-01-18T16:26:26Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17347/segments/0d9155ad-dcbc-468f-bcbf-d6e7d36ad5d8”.
2025-01-18 10:26:27.839 CST [1] LOG: startup process (PID 17) was terminated by signal 6: Aborted
2025-01-18 10:26:27.839 CST [1] LOG: aborting startup due to startup process failure
2025-01-18 10:26:27.840 CST [1] LOG: database system is shut down

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-01-18 10:26:28.265 CST [1] LOG: starting PostgreSQL 15.5 (Debian 15.5-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-01-18 10:26:28.266 CST [1] LOG: listening on IPv4 address “0.0.0.0”, port 5432
2025-01-18 10:26:28.266 CST [1] LOG: listening on IPv6 address “::”, port 5432
2025-01-18 10:26:28.266 CST [1] LOG: listening on Unix socket “/var/run/postgresql/.s.PGSQL.5432”
2025-01-18 10:26:28.269 CST [15] LOG: database system shutdown was interrupted; last known up at 2025-01-07 19:23:44 CST
[2025-01-18T16:26:28Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17591”.
[2025-01-18T16:26:28Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17347”.
[2025-01-18T16:26:28Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17591/segments/ebf2b026-4dcd-4208-8528-170b829d4de9”.
[2025-01-18T16:26:28Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17347/segments/0d9155ad-dcbc-468f-bcbf-d6e7d36ad5d8”.
2025-01-18 10:26:28.288 CST [15] LOG: invalid primary checkpoint record
2025-01-18 10:26:28.288 CST [15] PANIC: could not locate a valid checkpoint record
2025-01-18 10:26:29.856 CST [1] LOG: startup process (PID 15) was terminated by signal 6: Aborted
2025-01-18 10:26:29.856 CST [1] LOG: aborting startup due to startup process failure
2025-01-18 10:26:29.858 CST [1] LOG: database system is shut down

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-01-18 10:26:30.330 CST [1] LOG: starting PostgreSQL 15.5 (Debian 15.5-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-01-18 10:26:30.331 CST [1] LOG: listening on IPv4 address “0.0.0.0”, port 5432
2025-01-18 10:26:30.331 CST [1] LOG: listening on IPv6 address “::”, port 5432
2025-01-18 10:26:30.331 CST [1] LOG: listening on Unix socket “/var/run/postgresql/.s.PGSQL.5432”
2025-01-18 10:26:30.334 CST [16] LOG: database system shutdown was interrupted; last known up at 2025-01-07 19:23:44 CST
[2025-01-18T16:26:30Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17591”.
[2025-01-18T16:26:30Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17347”.
[2025-01-18T16:26:30Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17347/segments/0d9155ad-dcbc-468f-bcbf-d6e7d36ad5d8”.
[2025-01-18T16:26:30Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17591/segments/ebf2b026-4dcd-4208-8528-170b829d4de9”.
2025-01-18 10:26:30.355 CST [16] LOG: invalid primary checkpoint record
2025-01-18 10:26:30.355 CST [16] PANIC: could not locate a valid checkpoint record
2025-01-18 10:26:31.980 CST [1] LOG: startup process (PID 16) was terminated by signal 6: Aborted
2025-01-18 10:26:31.980 CST [1] LOG: aborting startup due to startup process failure
2025-01-18 10:26:31.981 CST [1] LOG: database system is shut down

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-01-18 10:26:32.634 CST [1] LOG: starting PostgreSQL 15.5 (Debian 15.5-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-01-18 10:26:32.634 CST [1] LOG: listening on IPv4 address “0.0.0.0”, port 5432
2025-01-18 10:26:32.634 CST [1] LOG: listening on IPv6 address “::”, port 5432
2025-01-18 10:26:32.635 CST [1] LOG: listening on Unix socket “/var/run/postgresql/.s.PGSQL.5432”
2025-01-18 10:26:32.638 CST [16] LOG: database system shutdown was interrupted; last known up at 2025-01-07 19:23:44 CST
[2025-01-18T16:26:32Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17591”.
[2025-01-18T16:26:32Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17347”.
[2025-01-18T16:26:32Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17591/segments/ebf2b026-4dcd-4208-8528-170b829d4de9”.
[2025-01-18T16:26:32Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17347/segments/0d9155ad-dcbc-468f-bcbf-d6e7d36ad5d8”.
2025-01-18 10:26:32.657 CST [16] LOG: invalid primary checkpoint record
2025-01-18 10:26:32.657 CST [16] PANIC: could not locate a valid checkpoint record
2025-01-18 10:26:34.388 CST [1] LOG: startup process (PID 16) was terminated by signal 6: Aborted
2025-01-18 10:26:34.388 CST [1] LOG: aborting startup due to startup process failure
2025-01-18 10:26:34.389 CST [1] LOG: database system is shut down

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-01-18 10:26:35.432 CST [1] LOG: starting PostgreSQL 15.5 (Debian 15.5-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-01-18 10:26:35.432 CST [1] LOG: listening on IPv4 address “0.0.0.0”, port 5432
2025-01-18 10:26:35.432 CST [1] LOG: listening on IPv6 address “::”, port 5432
2025-01-18 10:26:35.433 CST [1] LOG: listening on Unix socket “/var/run/postgresql/.s.PGSQL.5432”
2025-01-18 10:26:35.435 CST [16] LOG: database system shutdown was interrupted; last known up at 2025-01-07 19:23:44 CST
[2025-01-18T16:26:35Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17591”.
[2025-01-18T16:26:35Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17347”.
[2025-01-18T16:26:35Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17347/segments/0d9155ad-dcbc-468f-bcbf-d6e7d36ad5d8”.
[2025-01-18T16:26:35Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17591/segments/ebf2b026-4dcd-4208-8528-170b829d4de9”.
2025-01-18 10:26:35.455 CST [16] LOG: invalid primary checkpoint record
2025-01-18 10:26:35.455 CST [16] PANIC: could not locate a valid checkpoint record
2025-01-18 10:26:36.951 CST [1] LOG: startup process (PID 16) was terminated by signal 6: Aborted
2025-01-18 10:26:36.951 CST [1] LOG: aborting startup due to startup process failure
2025-01-18 10:26:36.952 CST [1] LOG: database system is shut down

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-01-18 10:26:38.807 CST [1] LOG: starting PostgreSQL 15.5 (Debian 15.5-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-01-18 10:26:38.808 CST [1] LOG: listening on IPv4 address “0.0.0.0”, port 5432
2025-01-18 10:26:38.808 CST [1] LOG: listening on IPv6 address “::”, port 5432
2025-01-18 10:26:38.808 CST [1] LOG: listening on Unix socket “/var/run/postgresql/.s.PGSQL.5432”
2025-01-18 10:26:38.811 CST [16] LOG: database system shutdown was interrupted; last known up at 2025-01-07 19:23:44 CST
[2025-01-18T16:26:38Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17591”.
[2025-01-18T16:26:38Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17347”.
[2025-01-18T16:26:38Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17347/segments/0d9155ad-dcbc-468f-bcbf-d6e7d36ad5d8”.
[2025-01-18T16:26:38Z INFO service::utils::clean] Find directory “pg_vectors/indexes/17591/segments/ebf2b026-4dcd-4208-8528-170b829d4de9”.
2025-01-18 10:26:38.830 CST [16] LOG: invalid primary checkpoint record
2025-01-18 10:26:38.830 CST [16] PANIC: could not locate a valid checkpoint record
2025-01-18 10:26:40.559 CST [1] LOG: startup process (PID 16) was terminated by signal 6: Aborted
2025-01-18 10:26:40.559 CST [1] LOG: aborting startup due to startup process failure
2025-01-18 10:26:40.560 CST [1] LOG: database system is shut down

[lostandjcfound]

so this is the final decision.

could someone help me get my pictures from where ever they are so i can reinstall immich with out losing them, i am VERY new to all this but i am trying to learn

Sadly it appears that database have corrupted its files somehow.

```2025-01-18 10:26:26.229 CST [17] LOG: invalid primary checkpoint record``2025-01-18 10:26:26.230 CST [17] PANIC: could not locate a valid`

checkpoint record

I’ve looked into it a bit in case I could find something that would block the clean shutdown on our end, but it appears to receive the stop signal and safely stop every time.

Now I wouldn’t expect such issues from Postgres, but in this case immich uses a project built on top of postgres with called pgvecto.
I can’t say that is their issue or not. I can’t know. But I saw more frequent corruptions with immich than any other app with postgres.

Now all ixvolumes are under /mnt/.ix-apps/app_mounts
For immich it would be /mnt/.ix-apps/app_mounts/immich

I think photos are stored under library in there.
You can get the files without the app running. Considering there will be the backups there, you might be able to restore the database as well. But you’d need to find someone to help you with restoring a db backup.

[lostandjcfound]

could someone help me get my pictures from where ever they are so i can reinstall immich with out losing them, i am VERY new to all this but i am trying to learn