[Error: EAGAIN: resource temporarily unavailable, statfs 'upload/library'] Failed to get server info

[luyzfernando08]

The bug

I'm using a NAS to store photos and for some reason the storage information is no longer shown.

Additionally, when trying to access the administrator area I receive the error below.

`Failed to get server info (500)

Stacktrace
Error: Error: 500
at Object.ie [as ok] (http://fotos.local/_app/immutable/chunks/fetch-client.DbGu7UYN.js:1:2832)
at async v (http://fotos.local/_app/immutable/chunks/auth.BSeebS59.js:1:636)
at async ml (http://fotos.local/_app/immutable/nodes/39.DZd7bJfn.js:1:1738)
at async Ie (http://fotos.local/_app/immutable/chunks/entry.gs5-sG3j.js:1:13443)`

2024-04-03 07:35:52 [Nest] 6 - 04/03/2024, 10:35:52 AM ERROR [Error: EAGAIN: resource temporarily unavailable, statfs 'upload/library'] Failed to get server info
2024-04-03 07:35:52 [Nest] 6 - 04/03/2024, 10:35:52 AM ERROR [Error: EAGAIN: resource temporarily unavailable, statfs 'upload/library'] Error: EAGAIN: resource temporarily unavailable, statfs 'upload/library'

I'm not sure which version of Immich the problem started with

The OS that Immich Server is running on

Windows 11

Version of Immich Server

v1.100.0

Version of Immich Mobile App

v1.100.0 build 130

Platform with the issue

• Server
• Web
• Mobile

Your docker-compose.yml content

version: "3.8"

services:
  immich-server:
    container_name: immich_server
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    command: ["start.sh", "immich"]
    volumes: 
      - upload:/usr/src/app/upload
      - /etc/localtime:/etc/localtime:ro
    env_file:
      - .env
    ports:
      - 2283:3001
    depends_on:
      - redis
      - database
    restart: always

  immich-microservices:
    container_name: immich_microservices
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    # extends:
    #   file: hwaccel.yml
    #   service: hwaccel
    command: ["start.sh", "microservices"]
    volumes:
      - upload:/usr/src/app/upload
      - /etc/localtime:/etc/localtime:ro
    env_file:
      - .env
    depends_on:
      - redis
      - database
    restart: always

  immich-machine-learning:
    container_name: immich_machine_learning
    image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}
    volumes:
      - model-cache:/cache
    env_file:
      - .env
    restart: always

  redis:
    container_name: immich_redis
    image: redis:6.2-alpine@sha256:70a7a5b641117670beae0d80658430853896b5ef269ccf00d1827427e3263fa3
    restart: always

  database:
    container_name: immich_postgres
    image: tensorchord/pgvecto-rs:pg14-v0.2.0@sha256:90724186f0a3517cf6914295b5ab410db9ce23190a2d9d0b9dd6463e3fa298f0
    env_file:
      - .env
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
    volumes:
      - "D:/Immich/pgdata:/var/lib/postgresql/data"
    restart: always

volumes:
  model-cache:
    driver: local
    driver_opts:
      type: cifs
      device: //192.168.0.199/Immich/cache
      o: addr=192.168.0.199,vers=2.0,username=XXXXXX,password=XXXXX,file_mode=0777,dir_mode=0777
  upload: 
    driver: local
    driver_opts:
      type: cifs
      device: //192.168.0.199/Immich/upload
      o: addr=192.168.0.199,vers=2.0,username=XXXXX,password=XXXXX,file_mode=0777,dir_mode=0777

Your .env content

# You can find documentation for all the supported env variables at https://immich.app/docs/install/environment-variables

# The location where your uploaded files are stored
UPLOAD_LOCATION=immich-upload

# The Immich version to use. You can pin this to a specific version like "v1.71.0"
IMMICH_VERSION=v1.100.0

# Connection secrets for postgres and typesense. You should change these to random passwords
TYPESENSE_API_KEY=TYPESENSE_API_KEY
DB_PASSWORD=XXXXXXXXX

# The values below this line do not need to be changed
###################################################################################
DB_HOSTNAME=immich_postgres
DB_USERNAME=postgres
DB_DATABASE_NAME=immich

REDIS_HOSTNAME=immich_redis

Reproduction steps

1. open the web or mobile app
2. access the area to view "Server Storage"

Additional information

No response

[bo0tzz]

That looks like your network mount broke, I don't think this is an issue in Immich.

[luyzfernando08]

It's not a network problem, everything else works.

Access to photos on the NAS is normal, as is the backup.

See the image below for recent photos.

It's a specific problem that has appeared in recent versions, but unfortunately I can't confirm which one.

[luyzfernando08]

@bo0tzz Could it be that problem 8202 and 8426 is unrelated to this?

[bo0tzz]

I think those are different issues. What you're seeing isn't inconsistency but just straight up errors. If you try to browse the files locally on your system, or from the shell inside of the immich containers, does that work as expected?

[luyzfernando08]

To test, I took a photo now.

In docker and windows explorer the file is there.

In Immich, the photo is loaded in the browser.

[mmomjian]

Can you download that image?

[luyzfernando08]

Yes, however, a strange thing happens.

When requesting download, the image is downloaded twice.

There are two files left, one good and one corrupt.

But I think that could be another problem.

[mmomjian]

I suspect this is due to a weird interplay of Windows / Docker Desktop / network storage creating a perfect storm. While it would ideally work, there is a limit to the systems we can test / support. We recommend Linux with plain Docker, as Docker Desktop + Windows can introduce a lot of issues due to the virtual machine structure and file/network permissions.

[odedia]

I seem to face the same/similar issue on macOS (ARM, M1 Max). The images are on a TrueNAS Scale SMB share. I've added a volume to server and microservices in docker-compose as follows:

      - /Volumes/Data-1/Pictures/PhotoPrism/Originals:/mnt/media/originals:ro

The docker logs output the following in microservices:

2024-04-09 18:19:31 [Nest] 7  - 04/09/2024, 3:19:31 PM   ERROR [JobService] Unable to run job handler (library/library-refresh): Error: EAGAIN: resource temporarily unavailable, scandir '/mnt/media/originals/2007/2007-09-02'
2024-04-09 18:19:31 [Nest] 7  - 04/09/2024, 3:19:31 PM   ERROR [JobService] Error: EAGAIN: resource temporarily unavailable, scandir '/mnt/media/originals/2007/2007-09-02'
2024-04-09 18:19:31 [Nest] 7  - 04/09/2024, 3:19:31 PM   ERROR [JobService] Object:
2024-04-09 18:19:31 {
2024-04-09 18:19:31   "id": "776bb755-95d6-4fb6-8623-61ee9cccb703",
2024-04-09 18:19:31   "refreshModifiedFiles": false,
2024-04-09 18:19:31   "refreshAllFiles": true
2024-04-09 18:19:31 }
2024-04-09 18:19:31 

This is a brand new install, library is empty, all I did was add the external library /mnt/media/originals and ran "Force Rescan". It's currenly at zero.

[HardoA]

I appear to have the same issue.

Immich v1.101.0 run as a docker container in Ubuntu 22.04.4 LTS with the latest updates. Photos on SMB share from Truenas. I have been using Immich for over a year with continued updates as they come out but I did skip v1.100.0.

Rebooted the containers, restarted the host and attempted administrator self fix page but that now times out.

Some logs attached from immich_server. I have not enabled DEBUG yet.

[tspirtle]

Same issue here, seeing log entries containing "Error: EAGAIN: resource temporarily unavailable, statfs 'upload/library'"

I've been running v1.101.0 since release day. Today, suddenly photos backed up via Android and iOS apps appear as grey broken thumbnails and images. Photos uploaded via the web are working correctly. No changes have been made to my environment to cause this. The timing of the issue seems to coincide with backing up ~300 images from my phone. Thumbnails stopped generating and images became broken midway through the upload.

Additionally, Storage Stats will not display (constantly spinning), and "Users" and "External Libraries" result in Error 500:

Failed to get server info (500)

Stacktrace
Error: Error: 500
    at Object.de [as ok] (https://photos.redacted.com/_app/immutable/chunks/fetch-client.CUHQ0TcQ.js:1:2835)
    at async v (https://photos.redacted.com/_app/immutable/chunks/auth.Ceg-WeSQ.js:1:636)
    at async ml (https://photos.redacted.com/_app/immutable/nodes/39.DLgPt8r1.js:1:1694)
    at async Ie (https://photos.redacted.com/_app/immutable/chunks/entry.Cvo-FpGt.js:1:13444)

[tspirtle]

Bingo! Good find! I was running kernel 5.15.0-102. I rolled back to 5.15.0-101, and uploads are working correctly. I had to refresh thumbnails on assets uploaded before I rolled back the kernel.

[Baker53054]

TI waws on 5.15, i updated to 6.5 and it is all good, sweet and thanks

[HardoA]

Confirmed, fixed it for me as well. I updated to 6.5.

[waliaabhishek]

Confirmed working. kernel 5.15.102 is broken if anyone else comes looking for a similar issue. Kernal upgrade otr downgrade might help.

[DevGoran]

Solved it also for me, upgraded from 5.15.102 to 6.5

[kkoshelev]

I have the same issue. I beleive it is because of recent kernel update.

Linux version 5.15.0-102-generic (buildd@lcy02-amd64-080) (gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #112-Ubuntu SMP Tue Mar 5 16:50:32 UTC 2024

Can anyone suggest a command to downgrade kernel to the previous 101 version?

[gruenheit]

I solved it by downgrading, following this guide.
5.15.0-102-generic -> 5.15.0-101-generic x86_64

[engkad]

Worth noting that I have this issue on docker on Ubuntu and ended up trying an SMB docker volume instead of the one mounted on the host, and that seems to solve the problem as well. Maybe easier than rolling back kernel if you only have remote access like me.

Edit: Nope never mind, samba is definitely a problem here - I realized the volume that worked was a new local volume, not the smb volume.

[raikes]

Just been battling with this myself. Changed my storage over to an SMB mount (using autofs) and suddenly couldn't access the Administration tab via the web gui. Server logs were showing:

immich_server | 2024-04-14T08:58:36.826248020Z [Nest] 7 - 04/14/2024, 8:58:36 AM ERROR [Error: EAGAIN: resource temporarily unavailable, statfs 'upload/library'] Failed to get server info

immich_server | 2024-04-14T08:58:36.826294662Z [Nest] 7 - 04/14/2024, 8:58:36 AM ERROR [Error: EAGAIN: resource temporarily unavailable, statfs 'upload/library'] Error: EAGAIN: resource temporarily unavailable, statfs 'upload/library'

Server is running Ubuntu 22.04 LTS, the kernel was 5.15.0-102. Downgraded kernel to 5.15.0-101 and everything is working again

[engkad]

I just tried that but the 101 kernel broke some of my other containers - I'm hoping someone finds another workaround.

[TheCanadian42]

Any ideas for a windows docker desktop workaround?

[roks531]

Same problem here, ubuntu server, kernel 5.15.0-102. Kernel downgrade is not a real solution...

[mgaudieri]

Same issue here unfortunately.

[Edzioindra]

Tried several rolling back and forth. Issue is the same. Using Ubuntu Server VM in proxmix and upload library is in TrueNas.

[Master-of-Mouse]

I'm setting up an immich container in a docker environment.
Proxmox -> Debian VM -> docker ->immich

I have another Truenas VM with an SMB share that I would like to use for immich
Proxmox -> VM Truenas -> Share SMB immich

I would like to replace "UPLOAD_LOCATION=./library" in the .env with something that points to the share on Truenas.

I understand that many of you have already done this but I didn't understand how you configured the connection in the docker-compose.yml and .env files.
I would like to keep only the database on the Debian VM disk. Images, videos and previews in Truenas.

[kkoshelev]

Is it safe to upgrade kernel from 5.15.0-101 version? Do you know if the issue is still there?

Edited: new 5.15.0-112-generic kernel doesn't seem to have that issue