March 12, 20242 yr I followed this YouTube video to install Immich- Used the docker apps from the standard Unraid Apps page: Immich Postgres 15 Redis I configured them as directed, only a minimal amount of config was needed in the Docket templates, but Immich wouldn't start up as it was meant to. I didn't have much time to troubleshoot, so gave up for the day. I found the following day that Nextcloud wouldn't start, and had numerous issues since: Nextcloud wasn't available. I found that MariaDB-Official wouldn't start. The solution to getting that running again seemed to be a combination of reverting to an earlier ZFS snapshot, installing the rc version, then multiple directories in the docker were read-only: 2024-02-27 20:37:36 0 [Warning] Can't create test file '/var/lib/mysql/1dd699d8d500.lower-test' (Errcode: 13 "Permission denied") 2024-02-27 20:37:36 0 [Note] Starting MariaDB 11.4.1-MariaDB-1:11.4.1+maria~ubu2204-log source revision fa69b085b10f19a3a8b6e7adab27c104924333ae as process 28 2024-02-27 20:37:36 0 [ERROR] mariadbd: File './binlog.index' not found (Errcode: 13 "Permission denied") 2024-02-27 20:37:36 0 [ERROR] Aborting 2024-02-27 20:38:09+00:00 [ERROR] [Entrypoint]: Unable to start server. 2024-02-27 20:37:27+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.4.1+maria~ubu2204 started. 2024-02-27 20:37:35+00:00 [Note] [Entrypoint]: MariaDB upgrade information missing, assuming required 2024-02-27 20:37:35+00:00 [Note] [Entrypoint]: Starting temporary server 2024-02-27 20:37:35+00:00 [Note] [Entrypoint]: Waiting for server startup Once I'd chmod 777'd the directories, it started and was OK. Once that was fixed, I was getting this error when trying to load Nextcloud: To fix that, I had to chmod 777 those directories. Following that, Nextcloud would start up, but it's running far slower than it used to. Plex was running fine initially, albeit loading pages slower than usual and the content on its home screen not displaying on first load, but would load after going to another page and then back again. Then a few days ago, it stopped playing files altogether. I got a "Critical: libusb_init failed" in its log. I managed to fix this by doing a "force update" from the Docker page. It pulled some files and worked fine for a few hours. Now today when we tried it again, it's loading pages, but not playing any files, the "Critical: libusb_init failed" error is back, and doing a "force update" isn't pulling files or making any difference. Generally, everything feels slower. I have tried rebooting twice while trying to troubleshoot since this began, each time I got an unclean shutdown. I understand that it could be complete coincidence that things went wrong just around the time that I'd tried to install Immich, and I'm not saying 100% that's what caused any of this, but as far as I'm aware, that's the only thing that I'd touched on the server before these issues started happening. Weirdnesses: How did installing 3 Docker apps affect anything else? Isn't the whole point of Docker that it's containerised and messing with an App shouldn't be able to affect anything else? I particularly don't get how the directory permissions in appdata of unrelated Docker apps (MariaDB and Nextcloud) were changed when I'd never had any need to go into those directories. Even if it wasn't anything to do with installing Immich, how could those permissions change? After I restored from the Mariadb ZFS snapshots, I still had permissions issues. I didn't think this was possible- shouldn't a snapshot restoration put everything back to exactly how it was when the snapshot was taken? How was Plex slow, but usable for a few weeks, then required a "force reinstall" to start working, which only worked temporarily and now it won't play media at all? tower-diagnostics-20240312-0057.zip I also have syslog enabled, so have logs of the whole timespan. Edited March 12, 20242 yr by -C-
June 28, 20242 yr Im in the same boat. Immich was fine but plex slowed.. I thought it was just plex doing background work. But just narrowed it down to immesh crashing my unread server. Im not sure what is set wrong. or if I need a second server to run just immesh. I like the app a lot and would be willing to do it, but think it's kinda over kill to just run immesh.
January 17, 20251 yr I have the same problem :-( PostgreSQL_Immich in docker is running and it stopps working, for no reson. I've had Immich running on unraid for over 8 months until I had to rebuild all my docker containers. Now it just flips from time to time for noe reson I can figure. It can run for 48h og it just flips afther 3-4h. Anyone seen the same thing? And managed to fix it? My latest log from PostgreSQL_Immich: 2025-01-17 02:31:20.707 CET [1] LOG: starting PostgreSQL 16.3 (Debian 16.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit 2025-01-17 02:31:20.707 CET [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 2025-01-17 02:31:20.707 CET [1] LOG: listening on IPv6 address "::", port 5432 2025-01-17 02:31:20.720 CET [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 2025-01-17 02:31:20.742 CET [30] LOG: database system was shut down at 2025-01-17 02:30:45 CET 2025-01-17 02:31:20.743 [31] LOG: Find directory "pg_vectors/indexes/000000000000000000000000000000006752c6d507887027000040000000448c". 2025-01-17 02:31:20.743 [31] LOG: Find directory "pg_vectors/indexes/000000000000000000000000000000006752c6d5078870270000400000004580". 2025-01-17 02:31:20.743 [31] LOG: Find directory "pg_vectors/indexes/000000000000000000000000000000006752c6d507887027000040000000448c/segments/83f38377-48bd-4f5f-90a1-faa073c514c0". 2025-01-17 02:31:20.751 CET [1] LOG: database system is ready to accept connections 2025-01-17 02:31:20.762 [31] LOG: Find directory "pg_vectors/indexes/000000000000000000000000000000006752c6d5078870270000400000004580/segments/fe30d165-47d3-48a1-8097-eee073dc7432". 2025-01-17 02:36:20.778 CET [28] LOG: checkpoint starting: time 2025-01-17 02:36:27.768 CET [28] LOG: checkpoint complete: wrote 71 buffers (0.4%); 0 WAL file(s) added, 0 removed, 0 recycled; write=6.930 s, sync=0.041 s, total=6.990 s; sync files=12, longest=0.005 s, average=0.004 s; distance=11 kB, estimate=11 kB; lsn=0/C56CB040, redo lsn=0/C56CB008 2025-01-17 04:06:21.975 CET [28] LOG: checkpoint starting: time 2025-01-17 04:06:22.106 CET [28] LOG: checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.101 s, sync=0.009 s, total=0.132 s; sync files=2, longest=0.005 s, average=0.005 s; distance=3 kB, estimate=10 kB; lsn=0/C56CBE40, redo lsn=0/C56CBE08 2025-01-17 06:06:23.112 CET [28] LOG: checkpoint starting: time 2025-01-17 06:06:23.242 CET [28] LOG: checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.101 s, sync=0.009 s, total=0.131 s; sync files=2, longest=0.005 s, average=0.005 s; distance=3 kB, estimate=10 kB; lsn=0/C56CCCD0, redo lsn=0/C56CCC98 2025-01-17 06:11:23.342 CET [28] LOG: checkpoint starting: time 2025-01-17 06:11:23.577 CET [28] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.202 s, sync=0.013 s, total=0.235 s; sync files=3, longest=0.005 s, average=0.005 s; distance=5 kB, estimate=9 kB; lsn=0/C56CE0D0, redo lsn=0/C56CE098 2025-01-17 07:41:25.182 CET [28] LOG: checkpoint starting: time 2025-01-17 07:41:42.664 CET [28] LOG: checkpoint complete: wrote 175 buffers (1.1%); 0 WAL file(s) added, 0 removed, 0 recycled; write=17.434 s, sync=0.027 s, total=17.483 s; sync files=6, longest=0.005 s, average=0.005 s; distance=6 kB, estimate=9 kB; lsn=0/C56CF988, redo lsn=0/C56CF950 2025-01-17 08:06:26.088 CET [28] LOG: checkpoint starting: time 2025-01-17 08:06:26.206 CET [28] LOG: checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.101 s, sync=0.005 s, total=0.118 s; sync files=2, longest=0.003 s, average=0.003 s; distance=3 kB, estimate=8 kB; lsn=0/C56D0898, redo lsn=0/C56D0860 2025-01-17 10:06:28.023 CET [28] LOG: checkpoint starting: time 2025-01-17 10:06:28.154 CET [28] LOG: checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.101 s, sync=0.009 s, total=0.131 s; sync files=2, longest=0.005 s, average=0.005 s; distance=3 kB, estimate=8 kB; lsn=0/C56D1808, redo lsn=0/C56D17D0 2025-01-17 12:06:30.401 CET [28] LOG: checkpoint starting: time 2025-01-17 12:06:30.530 CET [28] LOG: checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.101 s, sync=0.009 s, total=0.130 s; sync files=2, longest=0.005 s, average=0.005 s; distance=4 kB, estimate=7 kB; lsn=0/C56D2810, redo lsn=0/C56D27D8 2025-01-17 12:26:30.930 CET [28] LOG: checkpoint starting: time 2025-01-17 12:26:31.164 CET [28] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.202 s, sync=0.013 s, total=0.234 s; sync files=3, longest=0.005 s, average=0.005 s; distance=5 kB, estimate=7 kB; lsn=0/C56D3D18, redo lsn=0/C56D3CE0 2025-01-17 14:06:31.889 CET [28] LOG: checkpoint starting: time 2025-01-17 14:06:32.123 CET [28] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.201 s, sync=0.012 s, total=0.234 s; sync files=3, longest=0.005 s, average=0.004 s; distance=4 kB, estimate=7 kB; lsn=0/C56D4D98, redo lsn=0/C56D4D60 2025-01-17 14:48:57.659 CET [873] FATAL: could not open file "global/pg_filenode.map": No such file or directory 2025-01-17 14:49:57.702 CET [874] FATAL: could not open file "global/pg_filenode.map": No such file or directory 2025-01-17 14:50:57.761 CET [875] FATAL: could not open file "global/pg_filenode.map": No such file or directory 2025-01-17 14:51:57.820 CET [876] FATAL: could not open file "global/pg_filenode.map": No such file or directory 2025-01-17 14:52:57.879 CET [877] FATAL: could not open file "global/pg_filenode.map": No such file or directory 2025-01-17 14:53:57.936 CET [878] FATAL: could not open file "global/pg_filenode.map": No such file or directory 2025-01-17 14:54:57.987 CET [879] FATAL: could not open file "global/pg_filenode.map": No such file or directory 2025-01-17 14:55:58.045 CET [1] LOG: could not open file "postmaster.pid": No such file or directory 2025-01-17 14:55:58.045 CET [1] LOG: performing immediate shutdown because data directory lock file is invalid 2025-01-17 14:55:58.045 CET [1] LOG: received immediate shutdown request 2025-01-17 14:55:58.045 CET [1] LOG: could not open file "postmaster.pid": No such file or directory 2025-01-17 14:55:58.123 CET [1] LOG: database system is shut down Edited January 17, 20251 yr by mikeofoslo
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.