JaviPas Posted February 21 Share Posted February 21 Thanks. I've tried, but somehow the ALTER EXTENSION vectors UPDATE TO '0.2.0'; fails It shows the message: ERROR: extension "vectors" has no update path from version "0.1.11" to version "0.2.0" So I'm again stuck. Quote Link to comment
JaviPas Posted February 21 Share Posted February 21 2 hours ago, gottoesplosivo said: What I did was actually following the instructions that you linked, and it seems to be working. ... Sorry, I fixed it. After trying your method I just edited the Postgres14 container to change the Repository parameter and put "0.2.0" instead of the 0.1.11 I had before. After restarting both containers (Immich and Postgres) the thing works. Yay! Thank you! Quote Link to comment
rutherford Posted February 21 Author Share Posted February 21 @JaviPas did you have to do all those SQL commands above? Or only change the pgvecto-rs repository? Quote Link to comment
gottoesplosivo Posted February 21 Share Posted February 21 24 minutes ago, JaviPas said: Sorry, I fixed it. After trying your method I just edited the Postgres14 container to change the Repository parameter and put "0.2.0" instead of the 0.1.11 I had before. After restarting both containers (Immich and Postgres) the thing works. Yay! Thank you! Well I'm glad it worked! I updated my guide specifying to use the v0.2.0 1 Quote Link to comment
Dalmate Posted February 21 Share Posted February 21 2 hours ago, rutherford said: @JaviPas did you have to do all those SQL commands above? Or only change the pgvecto-rs repository? I had to run the commands to get it to work. Some people are reporting they didnt need to but mine wouldnt start without doing that. Quote Link to comment
rutherford Posted February 22 Author Share Posted February 22 (edited) I'd switched over to Spaceinvader postgresql docker, called PostgreSQL_Immich. I changed only one thing, the Repository to "tensorchord/pgvecto-rs:pg16-v0.2.0" restarted Immich, logged back in, good to go. Updated the post #1. Please let me know if it needs more changes. Specifically those sql commands: are they are still necessary? Or the SWAG process. I haven't touched that part of the install for a few months. Edited February 22 by rutherford 1 Quote Link to comment
Moll Posted February 22 Share Posted February 22 (edited) [SOLVED] : i had the wrong IP adress for redis... Hello, I just installed Immich i use PostgreSQL_Immich and changed to tensorchord/pgvecto-rs:pg16-v0.2.0 I can access the WebUI but the Immich Docker log constatnly promts: Error: connect ETIMEDOUT at Socket.<anonymous> (/app/immich/server/node_modules/ioredis/built/Redis.js:170:41) at Object.onceWrapper (node:events:632:28) at Socket.emit (node:events:518:28) at Socket._onTimeout (node:net:589:8) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) { errorno: 'ETIMEDOUT', code: 'ETIMEDOUT', syscall: 'connect' can someone help with this? I tried to open /admon/jobs-status it took an long time and then i got this error. Don't know if these are connected. Quote Failed to fetch (500) Stacktrace TypeError: Failed to fetch at window.fetch (http://192.168.2.57:8089/_app/immutable/chunks/entry.PBSYdUyr.js:1:1677) at c (http://192.168.2.57:8089/_app/immutable/chunks/fetch-client.VozrW5mA.js:1:1986) at n (http://192.168.2.57:8089/_app/immutable/chunks/fetch-client.VozrW5mA.js:1:1352) at Object.o [as fetchJson] (http://192.168.2.57:8089/_app/immutable/chunks/fetch-client.VozrW5mA.js:1:1562) at Qe (http://192.168.2.57:8089/_app/immutable/chunks/fetch-client.VozrW5mA.js:1:8294) at xt (http://192.168.2.57:8089/_app/immutable/nodes/34.7II-aP-s.js:1:1298) at async be (http://192.168.2.57:8089/_app/immutable/chunks/entry.PBSYdUyr.js:1:12871) Edited February 25 by Moll second error Quote Link to comment
JaviPas Posted February 23 Share Posted February 23 On 2/21/2024 at 7:18 PM, rutherford said: @JaviPas did you have to do all those SQL commands above? Or only change the pgvecto-rs repository? Sorry, I didn't see this. I tried the commands and got an error, so after that I just closed the terminal, changed the repository in the Postgres docker config and restarted it. After that, it worked fine. Don't ask me why 😛 1 Quote Link to comment
adminmat Posted February 23 Share Posted February 23 On 2/21/2024 at 10:24 AM, gottoesplosivo said: What I did was actually following the instructions that you linked, and it seems to be working. Hi thanks for this. I have my containers set to auto update so my immich is broken. Was working prior. A few questions for you so I don't screw this up. 1. Can you clarify what values I use where you say: "Change the values in brackets with the one for your database, and remove the brackets" For example, to backup you use: docker exec -t (postgrescontainer) pg_dump -c -U (usernamedatabaseimmich) -d (immichdatabase) | gzip > (/mnt/user/Data/)immich.sql.gz What values do I use? I'm using Postgresql14 ; My username in the Postgresql14 template is adminmat ; for immichdatabase what do I use? For the (/mnt/user/Data/)immich.sql.gz part, this this the path to the unRAID share where I want to back up to? So for example I could use /mnt/user/Backups/ ? 2, I'm using Postgresql14. So I will continue to use 14? And just update the repository to tensorchord/pgvecto-rs:pg14-v0.2.0 ? 4. "Run the postgres command (making sure to change the name of the database if needed where it says “ALTER DATABASE immich”)" ; So I just copy and paste this entire block of commands? And what is my database name where it says “ALTER DATABASE immich” ? Thanks and sorry for all the noob questions. Quote Link to comment
gottoesplosivo Posted February 23 Share Posted February 23 5 minutes ago, adminmat said: Hi thanks for this. I have my containers set to auto update so my immich is broken. Was working prior. A few questions for you so I don't screw this up. Quote 1. Can you clarify what values I use where you say: "Change the values in brackets with the one for your database, and remove the brackets" For example, to backup you use: docker exec -t (postgrescontainer) pg_dump -c -U (usernamedatabaseimmich) -d (immichdatabase) | gzip > (/mnt/user/Data/)immich.sql.gz What values do I use? I'm using Postgresql14 ; My username in the Postgresql14 template is adminmat ; for immichdatabase what do I use? For the (/mnt/user/Data/)immich.sql.gz part, this this the path to the unRAID share where I want to back up to? So for example I could use /mnt/user/Backups/ ? like my postgrescontainer is named "postgresql15". Use the same username and password you put in as "DB_USERNAME" and "DB_PASSWORD" Quote 2, I'm using Postgresql14. So I will continue to use 14? And just update the repository to tensorchord/pgvecto-rs:pg14-v0.2.0 ? Correct Quote 4. "Run the postgres command (making sure to change the name of the database if needed where it says “ALTER DATABASE immich”)" ; So I just copy and paste this entire block of commands? And what is my database name where it says “ALTER DATABASE immich” ? Yes Quote Thanks and sorry for all the noob questions. no worries 1 Quote Link to comment
Rewrap Posted February 23 Share Posted February 23 I had Docker-composer.yml perfectly working, however, after the recent immich update. It stopped working. I have deleted all the data to set it up again, I can't see to make it work. Can someone guide me settings up immch docker container and immich_postgres. I have installed and set all the required variables, however the web-ui doesn't work. Quote Link to comment
rutherford Posted February 23 Author Share Posted February 23 19 minutes ago, captainland said: Can someone guide me settings up immch docker container and immich_postgres This thread is dedicated to the imagegenius docker app and connected postgresql_immich dockers. Are you going that route again, or following the full docker compose method over at Immich.app documentation? I can help with the former but imagegenius route. And you start by backing up what you have so far, then going to the top of post #1 and seeing how far you can get. Quote Link to comment
ThatGuyOrlando Posted February 24 Share Posted February 24 Thanks gottoesplosivo did the postgres update prior to updating immich and it went as smooth as butter. 1 Quote Link to comment
Rewrap Posted February 24 Share Posted February 24 On 2/22/2024 at 11:37 AM, Moll said: Hello, I just installed Immich i use PostgreSQL_Immich and changed to tensorchord/pgvecto-rs:pg16-v0.2.0 I can access the WebUI but the Immich Docker log constatnly promts: Error: connect ETIMEDOUT at Socket.<anonymous> (/app/immich/server/node_modules/ioredis/built/Redis.js:170:41) at Object.onceWrapper (node:events:632:28) at Socket.emit (node:events:518:28) at Socket._onTimeout (node:net:589:8) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) { errorno: 'ETIMEDOUT', code: 'ETIMEDOUT', syscall: 'connect' can someone help with this? I tried to open /admon/jobs-status it took an long time and then i got this error. Don't know if these are connected. After following all those steps from this post, I'm seeing the same error. And immich web-ui unable to connect Quote Link to comment
rutherford Posted February 24 Author Share Posted February 24 (edited) 23 hours ago, Rewrap said: settings up immch docker container and immich_postgres So the connection to your postgres docker isn't working. That's what you need to focus on. I added a screenshot of my Immich container settings, so you have both of those. Check those over carefully. And focus on the connection between Immich and PostgreSQL_Immich containers. This command can be helpful for some action root@mayorgoodway:~# lsof -n -i :5432 | grep LISTEN You run that from the regular unraid command line, and it will tell you WHAT, if anything, is listening on that port. I did these two, I have postgresql listening on 5432, and nothing listening on 5433. I remembered this command (not specifically, but generally) when I searched for "troubleshoot postgresql connection docker" and this site popped Edited February 24 by rutherford Quote Link to comment
rutherford Posted February 24 Author Share Posted February 24 (edited) 1 hour ago, Rewrap said: Redis.js:170:41 Looks like you have Redis connection problems. Check out the first post I modified a bit in this thread. There are settings for Redis, and those need all the correct port numbers. For me that's 6379, no password. Redis hostname is the statis IP of the unraid server. You do have Redis installed right? I'll keep with this lsof thing! Here you can see that 6379 says <something> is listening on port 6379. It doesn't report that it's Redis. Then I check another port that's nothing, and it returns nothing: nothing on that other port. So that's a pulse! Edited February 24 by rutherford Quote Link to comment
Moll Posted February 25 Share Posted February 25 23 hours ago, rutherford said: Looks like you have Redis connection problems. Check out the first post I modified a bit in this thread. There are settings for Redis, and those need all the correct port numbers. For me that's 6379, no password. Redis hostname is the statis IP of the unraid server. You do have Redis installed right? I'll keep with this lsof thing! Here you can see that 6379 says <something> is listening on port 6379. It doesn't report that it's Redis. Then I check another port that's nothing, and it returns nothing: nothing on that other port. So that's a pulse! Thanks for your help! I checked the port multiple times but never looked at the IP.... So my immich is running now! 1 Quote Link to comment
Rewrap Posted February 27 Share Posted February 27 On 2/25/2024 at 7:17 PM, Moll said: Thanks for your help! I checked the port multiple times but never looked at the IP.... So my immich is running now! I still couldn't find any fix for this: syscall: 'connect' } Error: connect ETIMEDOUT at Socket.<anonymous> (/app/immich/server/node_modules/ioredis/built/Redis.js:170:41) at Object.onceWrapper (node:events:632:28) at Socket.emit (node:events:518:28) at Socket._onTimeout (node:net:589:8) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) { errorno: 'ETIMEDOUT', code: 'ETIMEDOUT', syscall: 'connect' } Error: connect ETIMEDOUT at Socket.<anonymous> (/app/immich/server/node_modules/ioredis/built/Redis.js:170:41) at Object.onceWrapper (node:events:632:28) at Socket.emit (node:events:518:28) at Socket._onTimeout (node:net:589:8) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) { errorno: 'ETIMEDOUT', code: 'ETIMEDOUT', syscall: 'connect' } Error: connect ETIMEDOUT at Socket.<anonymous> (/app/immich/server/node_modules/ioredis/built/Redis.js:170:41) at Object.onceWrapper (node:events:632:28) at Socket.emit (node:events:518:28) at Socket._onTimeout (node:net:589:8) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) { errorno: 'ETIMEDOUT', code: 'ETIMEDOUT', syscall: 'connect' } Error: connect ETIMEDOUT at Socket.<anonymous> (/app/immich/server/node_modules/ioredis/built/Redis.js:170:41) at Object.onceWrapper (node:events:632:28) at Socket.emit (node:events:518:28) at Socket._onTimeout (node:net:589:8) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) { errorno: 'ETIMEDOUT', code: 'ETIMEDOUT', syscall: 'connect' } Error: connect ETIMEDOUT at Socket.<anonymous> (/app/immich/server/node_modules/ioredis/built/Redis.js:170:41) at Object.onceWrapper (node:events:632:28) at Socket.emit (node:events:518:28) at Socket._onTimeout (node:net:589:8) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) { errorno: 'ETIMEDOUT', code: 'ETIMEDOUT', syscall: 'connect' } Error: connect ETIMEDOUT at Socket.<anonymous> (/app/immich/server/node_modules/ioredis/built/Redis.js:170:41) at Object.onceWrapper (node:events:632:28) at Socket.emit (node:events:518:28) at Socket._onTimeout (node:net:589:8) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) { errorno: 'ETIMEDOUT', code: 'ETIMEDOUT', syscall: 'connect' } Error: connect ETIMEDOUT at Socket.<anonymous> (/app/immich/server/node_modules/ioredis/built/Redis.js:170:41) at Object.onceWrapper (node:events:632:28) at Socket.emit (node:events:518:28) at Socket._onTimeout (node:net:589:8) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) { errorno: 'ETIMEDOUT', code: 'ETIMEDOUT', syscall: 'connect' } Error: connect ETIMEDOUT at Socket.<anonymous> (/app/immich/server/node_modules/ioredis/built/Redis.js:170:41) at Object.onceWrapper (node:events:632:28) at Socket.emit (node:events:518:28) at Socket._onTimeout (node:net:589:8) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) { errorno: 'ETIMEDOUT', code: 'ETIMEDOUT', syscall: 'connect' } Error: connect ETIMEDOUT at Socket.<anonymous> (/app/immich/server/node_modules/ioredis/built/Redis.js:170:41) at Object.onceWrapper (node:events:632:28) at Socket.emit (node:events:518:28) at Socket._onTimeout (node:net:589:8) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) { errorno: 'ETIMEDOUT', code: 'ETIMEDOUT', syscall: 'connect' } Error: connect ETIMEDOUT at Socket.<anonymous> (/app/immich/server/node_modules/ioredis/built/Redis.js:170:41) at Object.onceWrapper (node:events:632:28) at Socket.emit (node:events:518:28) at Socket._onTimeout (node:net:589:8) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) { errorno: 'ETIMEDOUT', code: 'ETIMEDOUT', syscall: 'connect' } Error: connect ETIMEDOUT at Socket.<anonymous> (/app/immich/server/node_modules/ioredis/built/Redis.js:170:41) at Object.onceWrapper (node:events:632:28) at Socket.emit (node:events:518:28) at Socket._onTimeout (node:net:589:8) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) { errorno: 'ETIMEDOUT', code: 'ETIMEDOUT', syscall: 'connect' } Error: connect ETIMEDOUT at Socket.<anonymous> (/app/immich/server/node_modules/ioredis/built/Redis.js:170:41) at Object.onceWrapper (node:events:632:28) at Socket.emit (node:events:518:28) at Socket._onTimeout (node:net:589:8) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) { errorno: 'ETIMEDOUT', code: 'ETIMEDOUT', syscall: 'connect' } Error: connect ETIMEDOUT at Socket.<anonymous> (/app/immich/server/node_modules/ioredis/built/Redis.js:170:41) at Object.onceWrapper (node:events:632:28) at Socket.emit (node:events:518:28) at Socket._onTimeout (node:net:589:8) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) { errorno: 'ETIMEDOUT', code: 'ETIMEDOUT', syscall: 'connect' } Error: connect ETIMEDOUT at Socket.<anonymous> (/app/immich/server/node_modules/ioredis/built/Redis.js:170:41) at Object.onceWrapper (node:events:632:28) at Socket.emit (node:events:518:28) at Socket._onTimeout (node:net:589:8) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) { errorno: 'ETIMEDOUT', code: 'ETIMEDOUT', syscall: 'connect' } Error: connect ETIMEDOUT at Socket.<anonymous> (/app/immich/server/node_modules/ioredis/built/Redis.js:170:41) at Object.onceWrapper (node:events:632:28) at Socket.emit (node:events:518:28) at Socket._onTimeout (node:net:589:8) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) { errorno: 'ETIMEDOUT', code: 'ETIMEDOUT', syscall: 'connect' } Error: connect ETIMEDOUT at Socket.<anonymous> (/app/immich/server/node_modules/ioredis/built/Redis.js:170:41) at Object.onceWrapper (node:events:632:28) at Socket.emit (node:events:518:28) at Socket._onTimeout (node:net:589:8) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) { errorno: 'ETIMEDOUT', code: 'ETIMEDOUT', syscall: 'connect' } Error: connect ETIMEDOUT at Socket.<anonymous> (/app/immich/server/node_modules/ioredis/built/Redis.js:170:41) at Object.onceWrapper (node:events:632:28) at Socket.emit (node:events:518:28) at Socket._onTimeout (node:net:589:8) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) { errorno: 'ETIMEDOUT', code: 'ETIMEDOUT', syscall: 'connect' } Error: connect ETIMEDOUT at Socket.<anonymous> (/app/immich/server/node_modules/ioredis/built/Redis.js:170:41) at Object.onceWrapper (node:events:632:28) at Socket.emit (node:events:518:28) at Socket._onTimeout (node:net:589:8) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) { errorno: 'ETIMEDOUT', code: 'ETIMEDOUT', syscall: 'connect' } Error: connect ETIMEDOUT at Socket.<anonymous> (/app/immich/server/node_modules/ioredis/built/Redis.js:170:41) at Object.onceWrapper (node:events:632:28) at Socket.emit (node:events:518:28) at Socket._onTimeout (node:net:589:8) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) { errorno: 'ETIMEDOUT', code: 'ETIMEDOUT', syscall: 'connect' } Error: connect ETIMEDOUT at Socket.<anonymous> (/app/immich/server/node_modules/ioredis/built/Redis.js:170:41) at Object.onceWrapper (node:events:632:28) at Socket.emit (node:events:518:28) at Socket._onTimeout (node:net:589:8) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) { errorno: 'ETIMEDOUT', code: 'ETIMEDOUT', syscall: 'connect' } Redis: Postgres: Immich: Quote Link to comment
rutherford Posted February 27 Author Share Posted February 27 So Redis is complaining about connection errors. Did you see the post two above this one with the lsof command? Have you confirmed that redis is listening on that port? Then change the command to bump it up a couple ports so you see what a failure looks like, and make sure it's not that on the port you think Redis should be listening on. A google search about testing Redis docker connections found this stuff https://stackoverflow.com/questions/41371402/connecting-to-redis-running-in-docker-container-from-host-machine Not much applies, but you could try the last parts of the troubleshooting from there about redis-cli stuff, if you can find that binary somewhere, perhaps in the Redis console. Quote Link to comment
Mattaton Posted March 9 Share Posted March 9 Anyone been successful getting Fail2Ban setup with Immich? Quote Link to comment
Greygoose Posted March 11 Share Posted March 11 hey, so my docker filled up today, i located the issue to immich. ive checked my mapings in docker and they all seem fine, any ideas? Quote Link to comment
rutherford Posted March 11 Author Share Posted March 11 @Greygoose go to unraid gui > Docker scroll to bottom, hit Docker size. my Immich install is the biggest thing I have at 2.1G, it’s logs (a frequent a user of size!) are 550Kb. Keep an eye on those things. Quote Link to comment
T_Matz Posted March 22 Share Posted March 22 Has anyone gotten an intel iGPU working with immich? Quote Link to comment
brucejobs Posted April 12 Share Posted April 12 Machine Learning using Nvidia GPU I have it configured as such but not confident its working as expected. CPU runs at 100% and I am not seeing any activity in GPU monitor. Anyone else have ML working? Cheers, brucey Quote Link to comment
Rewrap Posted April 12 Share Posted April 12 On 3/11/2024 at 1:57 PM, rutherford said: @Greygoose go to unraid gui > Docker scroll to bottom, hit Docker size. my Immich install is the biggest thing I have at 2.1G, it’s logs (a frequent a user of size!) are 550Kb. Keep an eye on those things. This could be the problem I'm encountering. When uploading media, the thumbnails become broken, disappearing after upload. Additionally, when accessing the immch web-ui, it operates sluggishly, taking ages to open settings and other functions. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.