koyax Posts - Answer Overflow

koyax

•Created by koyax on 6/30/2023 in #help-desk-support

2-pass encoding fails on some media files. Single pass works fine.

I enabled 2-pass encoding for my video previews with h264 and realized, that for some assets the microservice failes with the following error message: This is testet with h264 and h265 videos as source.

[Nest] 8  - 06/30/2023, 1:23:21 PM     LOG [MediaService] Start encoding video c72b957b-9fe4-4bad-8326-f905e57ee5a0 -vcodec h264,-acodec opus,-movflags faststart,-vf scale=720:-2,-preset fast,-threads 3,-x264-params "pools=none",-x264-params "frame-threads=3",-b:v 2483k,-minrate 1241.5k,-maxrate 3600k

[Nest] 8  - 06/30/2023, 1:23:22 PM   ERROR [JobService] Unable to run job handler: Error: ffmpeg was killed with signal SIGSEGV

[Nest] 8  - 06/30/2023, 1:23:22 PM   ERROR [JobService] Error: ffmpeg was killed with signal SIGSEGV

    at ChildProcess.<anonymous> (/usr/src/app/node_modules/fluent-ffmpeg/lib/processor.js:180:22)

    at ChildProcess.emit (node:events:513:28)

    at ChildProcess._handle.onexit (node:internal/child_process:291:12)

[Nest] 8  - 06/30/2023, 1:23:22 PM   ERROR [JobService] Object

[Nest] 8  - 06/30/2023, 1:23:21 PM     LOG [MediaService] Start encoding video c72b957b-9fe4-4bad-8326-f905e57ee5a0 -vcodec h264,-acodec opus,-movflags faststart,-vf scale=720:-2,-preset fast,-threads 3,-x264-params "pools=none",-x264-params "frame-threads=3",-b:v 2483k,-minrate 1241.5k,-maxrate 3600k

[Nest] 8  - 06/30/2023, 1:23:22 PM   ERROR [JobService] Unable to run job handler: Error: ffmpeg was killed with signal SIGSEGV

[Nest] 8  - 06/30/2023, 1:23:22 PM   ERROR [JobService] Error: ffmpeg was killed with signal SIGSEGV

    at ChildProcess.<anonymous> (/usr/src/app/node_modules/fluent-ffmpeg/lib/processor.js:180:22)

    at ChildProcess.emit (node:events:513:28)

    at ChildProcess._handle.onexit (node:internal/child_process:291:12)

[Nest] 8  - 06/30/2023, 1:23:22 PM   ERROR [JobService] Object

4 replies

IImmich

•Created by koyax on 5/28/2023 in #help-desk-support

DB Migration issue for checksum after Upgrade to 1.58.0

After upgrading to 1.58.0 I get migration errors:

2023-05-28T16:08:22.039240445Z QueryFailedError: column "checksum" of relation "assets" contains null values

2023-05-28T16:08:22.039242160Z     at PostgresQueryRunner.query (/usr/src/app/node_modules/typeorm/driver/postgres/PostgresQueryRunner.js:211:19)

2023-05-28T16:08:22.039243684Z     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

2023-05-28T16:08:22.039244952Z     at async RequireChecksumNotNull1684328185099.up (/usr/src/app/dist/apps/immich/libs/infra/src/migrations/1684328185099-RequireChecksumNotNull.js:10:9)

2023-05-28T16:08:22.039246301Z     at async MigrationExecutor.executePendingMigrations (/usr/src/app/node_modules/typeorm/migration/MigrationExecutor.js:225:17)

2023-05-28T16:08:22.039247623Z     at async DataSource.runMigrations (/usr/src/app/node_modules/typeorm/data-source/DataSource.js:260:35)

2023-05-28T16:08:22.039248889Z     at async DataSource.initialize (/usr/src/app/node_modules/typeorm/data-source/DataSource.js:148:17)

2023-05-28T16:08:22.039240445Z QueryFailedError: column "checksum" of relation "assets" contains null values

2023-05-28T16:08:22.039242160Z     at PostgresQueryRunner.query (/usr/src/app/node_modules/typeorm/driver/postgres/PostgresQueryRunner.js:211:19)

2023-05-28T16:08:22.039243684Z     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

2023-05-28T16:08:22.039244952Z     at async RequireChecksumNotNull1684328185099.up (/usr/src/app/dist/apps/immich/libs/infra/src/migrations/1684328185099-RequireChecksumNotNull.js:10:9)

2023-05-28T16:08:22.039246301Z     at async MigrationExecutor.executePendingMigrations (/usr/src/app/node_modules/typeorm/migration/MigrationExecutor.js:225:17)

2023-05-28T16:08:22.039247623Z     at async DataSource.runMigrations (/usr/src/app/node_modules/typeorm/data-source/DataSource.js:260:35)

2023-05-28T16:08:22.039248889Z     at async DataSource.initialize (/usr/src/app/node_modules/typeorm/data-source/DataSource.js:148:17)

I indeed have some assets, that do not have a checksum in the database. Example from the assets table:

00a0dbcf-510b-4faa-bee9-b1866536fbee,1139,6cc0efad-939f-46f6-8aa5-8d0aeafc906d,1eb1fad72832d9d41113245ee1b35bfcdec37abaf7232992501e295e2746467a,IMAGE,upload/library/username/2020/06-24/P1260976.jpg,upload/6cc0efad-939f-46f6-8aa5-8d0aeafc906d/thumb/1eb1fad72832d9d41113245ee1b35bfcdec37abaf7232992501e295e2746467a/19356d3e-0916-4b8e-b323-03b5d2f62b18.jpeg,2020-06-24 16:38:30.000000 +00:00,2020-06-24 16:38:30.000000 +00:00,false,image/jpeg,0:00:00.000000,upload/6cc0efad-939f-46f6-8aa5-8d0aeafc906d/thumb/1eb1fad72832d9d41113245ee1b35bfcdec37abaf7232992501e295e2746467a/19356d3e-0916-4b8e-b323-03b5d2f62b18.webp,"",,true,,2023-05-27 12:38:18.025606 +00:00,2023-02-21 19:54:59.463631 +00:00,false,P1260976

00a0dbcf-510b-4faa-bee9-b1866536fbee,1139,6cc0efad-939f-46f6-8aa5-8d0aeafc906d,1eb1fad72832d9d41113245ee1b35bfcdec37abaf7232992501e295e2746467a,IMAGE,upload/library/username/2020/06-24/P1260976.jpg,upload/6cc0efad-939f-46f6-8aa5-8d0aeafc906d/thumb/1eb1fad72832d9d41113245ee1b35bfcdec37abaf7232992501e295e2746467a/19356d3e-0916-4b8e-b323-03b5d2f62b18.jpeg,2020-06-24 16:38:30.000000 +00:00,2020-06-24 16:38:30.000000 +00:00,false,image/jpeg,0:00:00.000000,upload/6cc0efad-939f-46f6-8aa5-8d0aeafc906d/thumb/1eb1fad72832d9d41113245ee1b35bfcdec37abaf7232992501e295e2746467a/19356d3e-0916-4b8e-b323-03b5d2f62b18.webp,"",,true,,2023-05-27 12:38:18.025606 +00:00,2023-02-21 19:54:59.463631 +00:00,false,P1260976

3 replies

IImmich

•Created by koyax on 5/27/2023 in #help-desk-support

Folder and Storage Migration Mess-up

I use Immich since ~ August 2022. Immich Version: 1.57.1 I wanted to use the new storage label feature and realized after the migration job, I got files in the upload folder as well as in library. And in library there are some assets that apparently could not be migrated from the uuid to the storage template. upload folder:

root@docker:/data/immich/upload# ls -l
insgesamt 44
drwxr-xr-x  7 adminuser adminuser 4096 27. Mai 15:10 1c62e351-3435-4eb7-a2b5-d35b6035c0d2
drwx------  5 adminuser adminuser 4096 27. Mai 13:00 6cc0efad-939f-46f6-8aa5-8d0aeafc906d
drwxr-xr-x 10 root      root      4096 24. Mai 03:47 encoded-video
drwxr-xr-x 14 root      root      4096 27. Mai 14:14 library
drwxr-xr-x  9 root      root      4096 21. Mai 16:43 thumbs
drwxr-xr-x  4 root      root      4096 27. Mai 15:50 upload

root@docker:/data/immich/upload# ls -l
insgesamt 44
drwxr-xr-x  7 adminuser adminuser 4096 27. Mai 15:10 1c62e351-3435-4eb7-a2b5-d35b6035c0d2
drwx------  5 adminuser adminuser 4096 27. Mai 13:00 6cc0efad-939f-46f6-8aa5-8d0aeafc906d
drwxr-xr-x 10 root      root      4096 24. Mai 03:47 encoded-video
drwxr-xr-x 14 root      root      4096 27. Mai 14:14 library
drwxr-xr-x  9 root      root      4096 21. Mai 16:43 thumbs
drwxr-xr-x  4 root      root      4096 27. Mai 15:50 upload

root@docker:/data/immich/upload/library# ls -l
insgesamt 48
drwxr-xr-x  5 root root 4096 27. Mai 14:14 1c62e351-3435-4eb7-a2b5-d35b6035c0d2 (this is the uuid for lars)
drwxr-xr-x  3 root root 4096 27. Mai 14:14 6cc0efad-939f-46f6-8aa5-8d0aeafc906d (this is the uuid for userN)
drwxr-xr-x 11 root root 4096 27. Mai 14:10 lars
drwxr-xr-x 11 root root 4096 27. Mai 14:10 userN

root@docker:/data/immich/upload/library# ls -l
insgesamt 48
drwxr-xr-x  5 root root 4096 27. Mai 14:14 1c62e351-3435-4eb7-a2b5-d35b6035c0d2 (this is the uuid for lars)
drwxr-xr-x  3 root root 4096 27. Mai 14:14 6cc0efad-939f-46f6-8aa5-8d0aeafc906d (this is the uuid for userN)
drwxr-xr-x 11 root root 4096 27. Mai 14:10 lars
drwxr-xr-x 11 root root 4096 27. Mai 14:10 userN

The storage migration job in the microservice container is not throwing any error. If I search for m:FILENAME i can find all files as far as I can tell. I'd like to now, how to deal with this assets now.

16 replies

IImmich

•Created by koyax on 1/9/2023 in #help-desk-support

CLI still finds new images on fresh uploaded folder

https://github.com/immich-app/CLI/issues/52 I have a Folder with 6000+ Assets. After uploading them successfuly (no errors) and waiting for the jobs to succeed I rerun the upload. Now the tool still wants to upload about 780 files again. If I let it do so successfully and rerun the test the tool wants to reupload 760 files again. Does the upload silently fail somehow?

4 replies

Gaming

Programming