#Trouble adding external library

1 messages · Page 1 of 1 (latest)

jovial tide
#

Hello, I am a new user. I am trying to set up Immich to test it out as an alternative to PhotoPrism. I am unfamiliar with Docker and learning as I go.

I have set up Immich on an Ubuntu 22.04 VM under TrueNAS Core. I do not have GUI access to the install, only SSH.

I am trying to add an external library with my 8000+ existing photos using this guide. https://immich.app/docs/guides/external-library/ When I scan for new files in Immich, I get the notification that it has begun scanning but nothing happens. **No images appear and all Jobs are listed as 0 in the Jobs section.
**
The folder with the photos is mounted to the VM through an NFS share. To eliminate this as a potential problem, I created a local folder on the VM with a simple png in it and tried adding this as an external library. This also did not work.

I apologies if this is a simple fix and I am being dumb.

.env file:
OCATION=./library
DB_DATA_LOCATION=./postgres
IMMICH_VERSION=release
DB_PASSWORD=
DB_USERNAME=postgres
DB_DATABASE_NAME=immich
EXTERNAL_PATH=/home/Photos_NFS_Share
EXTERNAL_PATH2=/home/adam/Pictures

docker-compose.yml:
attached as a screenshot

mellow lintelBOT
#

:wave: Hey @jovial tide,

Thanks for reaching out to us. Please follow the recommended actions below; this will help us be more effective in our support effort and leave more time for building Immich immich.

References

Checklist

  1. :ballot_box_with_check: I have verified I'm on the latest release(note that mobile app releases may take some time).
  2. :ballot_box_with_check: I have read applicable release notes.
  3. :ballot_box_with_check: I have reviewed the FAQs for known issues.
  4. :blue_square: I have reviewed Github for known issues.
  5. :blue_square: I have tried accessing Immich via local ip (without a custom reverse proxy).
  6. :ballot_box_with_check: I have uploaded the relevant logs, docker compose, and .env files using the buttons below or the /upload command.
  7. :blue_square: I have tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable

(an item can be marked as "complete" by reacting with the appropriate number)

If this ticket can be closed you can use the /close command, and re-open it later if needed.

stark spindle
#

Can you also share the configuration that you're entering into the UI?

jovial tide
#

Is this what you were looking for?

stark spindle
#

Yup, that looks ok

#

More things to check: Did you apply the changes in the compose file and start the containers again? (docker compose up -d). Are there any errors in the logs?

jovial tide
#

I made sure to save the changes to the compose file and then checked using "cat" command. Yes, I restarted the containers a few times when troubleshooting. I cannot see any errors in the log file. (docker logs immich_server)

sacred blade
jovial tide
sacred blade
#

Can you run docker exec -it immich-server /bin/bash?

jovial tide
sacred blade
#

Sorry, with a underscore

jovial tide
#

immich_server?

sacred blade
#

Yea

#

I'm always confusing them lol

jovial tide
#

that worked, i now seem to be in another cli

sacred blade
#

K cool

#

Can you cd /usr/src/app/external?

jovial tide
#

yes, in the dir now

sacred blade
#

ls?

jovial tide
#

yup, gave me all 8k photos lmao

sacred blade
#

Hmmm

#

You did hit save in the UI, did you? lol

jovial tide
#

so this means the folder is being successfully passed to the docker container?

sacred blade
#

Yep

jovial tide
#

nothing :(

sacred blade
#

Can you show me the docker server logs as well?

#

(Even though they seem to be uninteresting)

jovial tide
#

whats the best way to do that? there are a lot of lines

sacred blade
#

You can use /upload

#

And the last like 100-200 lines should probably be sufficient

#

Also, which button did you click for initiating the scan?

jovial tide
sacred blade
#

Hm k, sad lol

jovial tide
#

i am not sure how to get the log file, ill just send a screenshot. also thanks for showing me how to get into the cli of the container, this looks useful

sacred blade
#

Yeah, that is great for debugging

#

Screenshot is probably fine :)

jovial tide
sacred blade
#

Can you go to Settings -> Logging and switch to a higher logging level?

#

Ideally Verbose

jovial tide
#

cool will do

sacred blade
#

So the scan endpoint is hit and then just nothing? lol

#

That's odd

#

@stark spindle ideas?

stark spindle
#

No 😅

sacred blade
#

Oh wait something is odd

#

Which version are you on?

#

The web says 106.4

#

But you have the startup command in your compose file, which shouldn't be there

#

I think microservices did not start up because of this

stark spindle
#

Aha, that'll be the issue yes

jovial tide
#

before i made the post i was on 1.105something. then i realised that i was out of date, so i did this from the immich website "docker compose pull && docker compose up -d"

sacred blade
#

You should always read the release notes when updating :)

jovial tide
#

should i have done something else

sacred blade
jovial tide
#

i did ctrl f for external library in the release notes, maybe that wasnt enough

sacred blade
#

You always want to read through the breaking changes section

#

Unrelated to whether you think it directly affects you or not

#

Any changes that are stated there should be done

jovial tide
#

ohhhhh ok, so that stuff at the start could be the source of the problem?

#

about changing stuff in the yml

sacred blade
#

That would be an explanation, yes

#

The scanning is done by microservices, which now is its own worker within the immich server container. Since you still only start immich though (by having that command line there), there is no microservices process/thread

jovial tide
#

ok, that is on me, i should have read that. apologies for taking your time. ill be back at it in about 1.5hrs, i will do the stuff mentioned in the release notes and update the thread here

sacred blade
#

All good, no worries :)

#

Just general advice for any software, especially the one you're selfhosting

#

In OSS breaking changes are more likely, so the release notes are always worth a read

#

Plus you can read about shiny new features :D

jovial tide
#

coolio, will make sure to do this in the future

jovial tide
#

yeeeees, thanks for the help @sacred blade @stark spindle