Throwing errors with respect to not being able to connect to the server

[pluim003]

Yesterday I stumbled on this little tool and immediately it worked like a charm. But now occassionally I'm getting some errors. And can't figure out why.
And after that it keeps complaining with errors. At first I thought it might be that my immich-server connected remotely via a domain would give a timeout but it also happened when accessing with the internal url:

2025-12-15 07:48:53 INF metadata updated file=2016:05/Vrijgezellenfeest Corine/20160507 - 011 - Vrijgezellenfeest Corine.jpg
2025-12-15 07:48:59 ERR server error file=2016:2016-nef/07/20160726-Profronde_Surhuisterveen/20160726 - 38 - Profronde Surhuisterveen.NEF error=AssetUpload, POST, https://immich.xxxxxx/api/assets
Post "https://immich.xxxxxxx/api/assets": dial tcp: lookup immich.xxxxxxxxxx:: no such host

io: read/write on closed pipe

2025-12-15 17:06:12 INF uploaded successfully file=2016:11/VID_20161120_113258.mp4
2025-12-15 17:06:14 INF uploaded successfully file=2016:2016-nef/05/Vrijgezellenfeest Corine/20160507 - 109 - Vrijgezellenfeestje Corine.NEF
2025-12-15 17:06:16 ERR server error file=2016:09/20160924-Meindert_Talma_in_Vera/20160924 - 15 - Meindert Talma in Vera.jpg error=AssetUpload, POST, http://192.168.178.11:2283/api/assets
Post "http://192.168.178.11:2283/api/assets": EOF

2025-12-15 17:06:16 ERR Error err=AssetUpload, POST, http://192.168.178.11:2283/api/assets
Post "http://192.168.178.11:2283/api/assets": EOF

io: read/write on closed pipe
2025-12-15 07:49:00 INF Immich Job command sent resume=thumbnailGeneration
2025-12-15 07:49:00 INF Immich Job command sent resume=metadataExtraction
2025-12-15 07:49:01 INF Immich Job command sent resume=videoConversion
2025-12-15 07:49:01 INF Immich Job command sent resume=faceDetection
2025-12-15 07:49:01 INF Immich Job command sent resume=smartSearch
2025-12-15 07:49:01 INF
2025-12-15 07:49:01 INF Asset Tracking Report:
2025-12-15 07:49:01 INF =====================
2025-12-15 07:49:01 INF Total Assets: 5868 (83.3 GB)
2025-12-15 07:49:01 INF Processed: 1390 (16.3 GB)
2025-12-15 07:49:01 INF Discarded: 15 (53.7 MB)
2025-12-15 07:49:01 INF Errors: 17 (2.3 GB)
2025-12-15 07:49:01 INF Pending: 4446 (64.7 GB)
2025-12-15 07:49:01 INF
2025-12-15 07:49:01 INF ⚠️ WARNING: 4446 assets did not reach a final state!
2025-12-15 07:49:01 INF
2025-12-15 07:49:01 INF
2025-12-15 07:49:01 INF Event Report:
2025-12-15 07:49:01 INF =============
2025-12-15 07:49:01 INF
2025-12-15 07:49:01 INF Discovery (Assets):
2025-12-15 07:49:01 INF discovered image : 5574 (65.0 GB)
2025-12-15 07:49:01 INF discovered video : 294 (18.3 GB)
2025-12-15 07:49:01 INF
2025-12-15 07:49:01 INF Discovery (Non-Assets):
2025-12-15 07:49:01 INF discovered unknown file : 2 (-)
2025-12-15 07:49:01 INF
2025-12-15 07:49:01 INF Asset Lifecycle (PROCESSED):
2025-12-15 07:49:01 INF uploaded successfully : 1322 (16.2 GB)
2025-12-15 07:49:01 INF metadata updated : 273 (161.3 MB)
2025-12-15 07:49:01 INF
2025-12-15 07:49:01 INF Asset Lifecycle (DISCARDED):
2025-12-15 07:49:01 INF server has duplicate : 63 (117.1 MB)
2025-12-15 07:49:01 INF discarded local duplicate : 6 (95.7 MB)
2025-12-15 07:49:01 INF
2025-12-15 07:49:01 INF Asset Lifecycle (ERROR):
2025-12-15 07:49:01 INF server error : 17
2025-12-15 07:49:01 INF
2025-12-15 16:33:37 ERR context canceled
2025-12-15 16:33:37 ERR context canceled
....
2025-12-15 16:33:37 ERR context canceled
2025-12-15 16:33:37 ERR Some errors have occurred. Look at the log file for details

What can be a cause?

Or is 5500 files in one run too much? Actually I could/should skip the NEF.

[pluim003]

Update: I gave it a try by excluding NEF but that didn't help.

Then decided to do only the folder and subfolder where the problems occur with debugmode but still throws the error:

2025-12-15 19:13:50 ERR server error file=06:20160612-Ladiesrun7.5-10km-klein/20160612 - 150 - Ladiesrun 7,5-10km.JPG error=AssetUpload, POST, http://192.168.178.11:2283/api/assets
Post "http://192.168.178.11:2283/api/assets": EOF

2025-12-15 19:13:50 DBG upload asset file.OriginalFileName=20160612 - 150 - Ladiesrun 7,5-10km.JPG file.FileName=06:20160612-Ladiesrun7.5-10km-klein/20160612 - 150 - Ladiesrun 7,5-10km.JPG file.ID= file.FileDate=2016-06-12 16:37:43 file.Description= file.FileSize=219757 file.CaptureDate=2016-06-12 15:18:46 file.Trashed=false file.Archived=false file.FromPartner=false file.Favorite=false file.Stars=0 file.Latitude=0.xxxxx file.Longitude=0.xxxxx
2025-12-15 19:13:50 ERR Error err=AssetUpload, POST, http://192.168.178.11:2283/api/assets
Post "http://192.168.178.11:2283/api/assets": EOF

I'm using version 0.31.0.

[simulot]

5500 photos doesn't hurt. I heard about successful load of several hundred photos.

Could you give more context?
Where immich-go is running?
Were are the photos? Local or on a shared drive?
What was the command line?

[pluim003]

Thanx, I'll look up the command when I'm at home at the end of the afternoon. It's running on Windows and photos are locally stored. Could there be something with a pathlength? As the total length is quite long with files in a subfolder of a subfolder of a subfolder of a folder.

[simulot]

Maybe. I'm not an OS specialist.

Apparently there is a limit:
https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry

Also the file name 06:20160612-Ladiesrun7.5-10km-klein/20160612 - 150 - Ladiesrun 7,5-10km.JPG is not valid with Windows.

[pluim003]

It doesn't reach the limit it seems. What makes the file name not valid with Windows? As those files are created over 9 years ago.

The 06:20160612-part is confusing. Because the whole path including filename is E:\Afbeeldingen\Foto\2016\06\Ladiesrun7.5-10km-klein\20160612 - 150 - Ladiesrun 7,5-10km.JPG and there are a bunch of those filenames. And it looks like filenames with 2,5 in it are imported. I'll check and post my command when I'm at at home.

[pluim003]

As promised the used command:

c:\tools\immich-go upload from-folder E:\Afbeeldingen\Foto\2016\ --server=https://xxxxxxxx --api-key=xxxxxxxxxxxxxxxxxxxxI --ban-file *.NEF --log-level=DEBUG

[yamada-sexta]

I have a similar issue:

Asset Tracking Report:
=====================
Total Assets:       4560  (48.0 GB)
  Processed:        3976  (15.9 GB)
  Discarded:           1  (2.0 MB)
  Errors:              0  (0 B)
  Pending:           583  (32.1 GB)

⚠️  WARNING: 583 assets did not reach a final state!


Event Report:
=============

Discovery (Assets):
  discovered image                   :    4419  (8.4 GB)
  discovered video                   :     141  (39.6 GB)

Discovery (Non-Assets):
  discovered sidecar                 :    4242  (3.0 MB)
  discovered unknown file            :     106  (175.5 MB)
  discovered banned file             :     187  (-)

Asset Lifecycle (PROCESSED):
  uploaded successfully              :       2  (3.1 MB)
  metadata updated                   :    3977  (15.9 GB)

Asset Lifecycle (DISCARDED):
  server has duplicate               :    3974  (15.9 GB)

Processing Events:
  associated metadata                :    3977
  missing metadata                   :     583
  stacked                            :       9
  tagged                             :       2

And I am on Linux using the command:
upload from-google-photos --server=http://x.x.x.x::2283 --api-key=xxxxxxx /mnt/takeout-xxxxx..zip --log-file xxxxx --ban-file "*.dng" --client-timeout=120m;

I wonder if that has anything to do with the file filter?