Closed Deathproof76 closed 4 months ago
I don't know if it's my place to do so, probably too early also, but I'd like to encourage @wardwygaerts @xs2usun @jarelllama to try out the apk from https://github.com/immich-app/immich/pull/9980#issuecomment-2149070097 In my case it helped with identifying a single asset with problematic metadata, which caused the whole problem for me. After deleting the asset from the database (as a quick fix) everything works for me now with the standard Playstore v1.105 apk too. If it's the same issue with your instance you need to turn on fine logging in the mobile app with the pr apk to identify the exact id of the offender. Thank you again @fyfrey and @alextran1502
Thank you! It fixed it!
With the app I could locate the same strange date in the db. Some movie of a Toyota Supra I had saved from the internet was causing the problem. My error log:
2024-06-05 14:14:41.575437 | SEVERE | AssetService | getRemoteAssets received too many almost empty chunks, stopping. Not all remote assets could be fetched from the server for user user. | 2024-06-05 14:14:41.575311 | FINE | AssetService | Received 1 assets ranging from (1731-08-07 07:03:48.000Z,f9f05b1b-7b69-485b-9821-d68f18ac8d8f) to (1731-08-07 07:03:48.000Z,f9f05b1b-7b69-485b-9821-d68f18ac8d8f) |
In table assets with id='f9f05b1b-7b69-485b-9821-d68f18ac8d8f' I looked up which file was causing the problem with the weird date. I removed the row from the table.
Then I opened the Immich app on my iPad and the timeline appears correct. I deinstalled the immich app from my Android phone. Installed the latest app from the Play store and the timeline appears fine. So everything was also caused by this strange date in the db. I inspected the file with ExifTool and the Exif data was empty. I also checked the properties of the file in WIndows and it showed the creation date and modified date of 2002-1-7 09:11. I have no idea what caused the strange line in the db.
I quicky checked the apk from #9980, and noticed my timeline loaded almost immediately, with all my assets (as far as I can see). So I thought, maybe I already removed a 'bad' asset (I cleaned up my pictures last week), so I installed the PlayStore version, but loading timeline was taking ages. Reinstalled the apk and timeline back ok... What are the best settings for the logs to troubleshoot or receive more info?
Itβs mentioned above in: https://github.com/immich-app/immich/issues/9534#issuecomment-2149436869
What are the best settings for the logs to troubleshoot or receive more info?
@wardwygaerts With the pr apk like this
Thanks!
I also found the bad asset!
2024-06-06 01:27:20.394787 | FINE | AssetService | Received 1 assets ranging from (0004-04-04 16:06:30.000Z,7f6a33c8-986e-4036-be11-608a02c686bb) to (0004-04-04 16:06:30.000Z,7f6a33c8-986e-4036-be11-608a02c686bb) |
2024-06-06 01:27:20.370140 | FINE | AssetService | Requesting assets older than (0004-04-04 16:06:30.000Z,7f6a33c8-986e-4036-be11-608a02c686bb) |
And this was due my own fault, I changed the date for this image, and entered 004 in stead of 2024...
Corrected the date for this image, reinstalled 1.105 from Playstore, timeline build in couple of seconds!
This may be a silly question, however, I'm just checking the basics here... is immich.mydomain.com
the configured domain or was that replaced/redacted by you?
If so, perhaps in the future you can put some type of placeholder there ( like immich.[DOMAIN].com
or immich.<DOMAIN>.com
), just so we can identify when something is purposefully changed and not and not assume a typo.
Just a small suggestion is all π
@safehome-jdev Oh, I didn't think of the possibility that there might be any confusion. Sorry about that. I've redacted my domain that way. Next time I'll use immich.[DOMAIN].com for sure ππ
The bug
Using the android mobile app from the playstore on a Samsung S23U: Since v1.105.0 I get weird errors where photos will get uploaded but not refreshed in the app. Tried to logout and in again via google oauth and mail/pw. But after relogin the timelime is building indefinitely.
I also tried direct ip in LAN. It somehow helps switching between Wifi and mobile Data. After doing that I'm able to see the remote photos and can upload photos but the gallery won't refresh and the backup cloud icon is crossed out*. The uploaded photos can be seen in the Webui though. I used a secondary android phone (some rooted xiaomi with a custom rom) to install v1.105.0 from github and compare with v1.104.0. due to https://github.com/immich-app/immich/issues/9495#issuecomment-2113818459
v1.104.0. works perfectly on the secondary phone but v1.105.0 shows the exact same issues as on the primary android phone.
*(after turning wifi off and waiting for mobile data, the "building timeline" vanishes and I can see photos but it seems to keep building in the background, down left "fotos" is still spinning)
update: I can access remote albums, which also show the correct backup status (only on server/on device and server) it seems to be mainly a problem with the timeline. I can search things and filter people/places.
Can't see any unusual in the docker logs, no warnings, errors, nothing:
The mobile logs show Key 'currentUser' not found in Store, Error while getting remote assets | ApiException 401: {"message":"Invalid user token","error":"Unauthorized","statusCode":401} , PersonService | Error while fetching curated people | ApiException 400: Socket operation failed: GET /person (Inner exception: Failed host lookup: 'immich.mydomain.com')
The OS that Immich Server is running on
docker
Version of Immich Server
v1.105.1
Version of Immich Mobile App
v1.105.0
Platform with the issue
Your docker-compose.yml content
Your .env content
Reproduction steps
Relevant log output
Additional information
I'm using the https://github.com/imagegenius/docker-immich monolythic dockerimage with tensorchord/pgvecto-rs:pg16-v0.2.0