Photoprism docker fails to start

SelfContained1981 · Nov 18th 2022

Hello Folks,

I've used OpenmediaVault in the past and love the product, but the issue im facing now is driving me bonkers.

I waned to try out the Photoprism plugin but it keeps failing to start.

Install went without issue and I was able to define the path etc. However there seems to be an issue with permissions and I dont see anywhere where i can assign photoprism user the necessaryt ACLs. Through ssh i added photoprism user to sudo even and allowed the folders to be accessible to everyone and still get the following:

Code

 root@openmediavault:/srv/dev-disk-by-uuid-FA17-EBB8# podman logs -l
started 221118-jammy as root (amd64-prod)
init: updating filesystem permissions
PHOTOPRISM_DISABLE_CHOWN="true" disables permission updates
Problems? Our Troubleshooting Checklists help you quickly diagnose and solve them:
https://docs.photoprism.app/getting-started/troubleshooting/
file umask....: "0002" (u=rwx,g=rwx,o=rx)
home directory: /photoprism
assets path...: /opt/photoprism/assets
storage path..: /photoprism/storage
config path...: default
cache path....: default
backup path...: /photoprism/storage/backups
import path...: /photoprism/import
originals path: /photoprism/originals
switching to uid 996:100
/opt/photoprism/bin/photoprism start
Failed creating test file in storage folder, see https://docs.photoprism.app/getting-started/troubleshooting/docker/#file-permissions
root@openmediavault:/srv/dev-disk-by-uuid-FA17-EBB8# podman logs -l

Display More

What am I doing wrong:

At the moment Im running openmediavault in a vm for testing:

Version
6.0.46-5 (Shaitan)

Processor

Kernel
Linux 5.19.0-0.deb11.2-amd64

This is the only plugin that is installed and all the latest updates are applied

Any and all help greatly appreciated

raulfg3 · Nov 18th 2022

do you use NTFS or FAT for your shared folder?

SelfContained1981 · Nov 18th 2022

Quote from raulfg3

do you use NTFS or FAT for your shared folder?

exFAT, should i format it as ext4?

SelfContained1981 · Nov 18th 2022

ok so i took your hint and reformatted the file system to ext4 and got ahead a bit more:

Code

root@openmediavault:~# podman ps --all
CONTAINER ID  IMAGE                     COMMAND   CREATED        STATUS            PORTS                   NAMES
2d953fa32075  k8s.gcr.io/pause:3.2                8 minutes ago  Up 8 minutes ago  0.0.0.0:2342->2342/tcp  5b45fc3d6595-infra
f7278a082081  docker.io/mariadb:latest  mariadbd  8 minutes ago  Up 8 minutes ago  0.0.0.0:2342->2342/tcp  photoprism-db

However photoprism-app still crashes and i dont see it spin up. Any thoughts?

SelfContained1981 · Nov 18th 2022

ok quick update... it works now!

Steps to fix:

1. Listen to raulfg3

2. Create an ext4 filesystem

3. reboot openmediavault

4. reinstall photoprism

5. apply changes and reboot

6. enable photoprism service + apply changes ---> if this still fails check that db and infra is up then reboot openmediavault:

Code

dcce5872a37d  k8s.gcr.io/pause:3.2                                          4 minutes ago  Up 4 minutes ago  0.0.0.0:2342->2342/tcp  0bbc3caef4ae-infra
3673a85fe0d3  docker.io/mariadb:latest                mariadbd              4 minutes ago  Up 4 minutes ago  0.0.0.0:2342->2342/tcp  photoprism-db

7. After reboot everything should work

lukas1760 · Nov 26th 2022

Hi all,

I don't want to spam with new topic. I have similiar problem. When I try to open photoprism page, I'm getting HTTP ERROR 502.

Photoprism is running under OMV 6.0.46-5 (Shaitan) in ESXi virtual enviroment. File Browser plugin works correctly. What I found out is:

Code

CONTAINER ID  IMAGE                                     COMMAND               CREATED       STATUS           PORTS                   NAMES
575937c358af  k8s.gcr.io/pause:3.2                                            41 hours ago  Up 41 hours ago  0.0.0.0:2342->2342/tcp  6827a070f618-infra
46b15ed82ed4  k8s.gcr.io/pause:3.2                                            41 hours ago  Up 41 hours ago  0.0.0.0:3670->8443/tcp  f5f7164356e3-infra
3757bb6f4040  docker.io/filebrowser/filebrowser:latest                        41 hours ago  Up 41 hours ago  0.0.0.0:3670->8443/tcp  filebrowser-app
6e9b5bb5a467  docker.io/library/caddy:latest            caddy run --confi...  41 hours ago  Up 41 hours ago  0.0.0.0:3670->8443/tcp  filebrowser-proxy
befc6ec32398  docker.io/library/caddy:latest            caddy run --confi...  41 hours ago  Up 41 hours ago  0.0.0.0:2342->2342/tcp  photoprism-proxy
77e9bb903128  docker.io/mariadb:latest                  mariadbd              41 hours ago  Up 41 hours ago  0.0.0.0:2342->2342/tcp  photoprism-db

and

Code

root@omv:~# podman logs -l
2022-11-24 20:06:22+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.9.3+maria~ubu2204 started.
2022-11-24 20:06:23+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2022-11-24 20:06:23+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.9.3+maria~ubu2204 started.
2022-11-24 20:06:24+00:00 [Note] [Entrypoint]: MariaDB upgrade information missing, assuming required
2022-11-24 20:06:24+00:00 [Note] [Entrypoint]: MariaDB upgrade (mariadb-upgrade) required, but skipped due to $MARIADB_AUTO_UPGRADE setting
2022-11-24 20:06:24 0 [Note] mariadbd (server 10.9.3-MariaDB-1:10.9.3+maria~ubu2204) starting as process 1 ...
2022-11-24 20:06:24 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-11-24 20:06:24 0 [Note] InnoDB: Number of transaction pools: 1
2022-11-24 20:06:24 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2022-11-24 20:06:24 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
2022-11-24 20:06:24 0 [Warning] mariadbd: io_uring_queue_init() failed with errno 1
2022-11-24 20:06:24 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF
2022-11-24 20:06:24 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2022-11-24 20:06:24 0 [Note] InnoDB: Completed initialization of buffer pool
2022-11-24 20:06:24 0 [Note] InnoDB: Buffered log writes (block size=512 bytes)
2022-11-24 20:06:25 0 [Note] InnoDB: 128 rollback segments are active.
2022-11-24 20:06:25 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2022-11-24 20:06:25 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2022-11-24 20:06:25 0 [Note] InnoDB: log sequence number 46640; transaction id 14
2022-11-24 20:06:25 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-11-24 20:06:25 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2022-11-24 20:06:25 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
2022-11-24 20:06:25 0 [Note] Server socket created on IP: '0.0.0.0'.
2022-11-24 20:06:25 0 [Note] Server socket created on IP: '::'.
2022-11-24 20:06:25 0 [Note] InnoDB: Buffer pool(s) load completed at 221124 20:06:25
2022-11-24 20:06:26 0 [Warning] 'user' entry 'root@photoprism' ignored in --skip-name-resolve mode.
2022-11-24 20:06:26 0 [Warning] 'proxies_priv' entry '@% root@photoprism' ignored in --skip-name-resolve mode.
2022-11-24 20:06:27 0 [Note] mariadbd: ready for connections.
Version: '10.9.3-MariaDB-1:10.9.3+maria~ubu2204'  socket: '/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
2022-11-24 20:06:30 3 [Warning] Access denied for user 'photoprism'@'127.0.0.1' (using password: YES)
2022-11-24 20:06:30 4 [Warning] Access denied for user 'photoprism'@'127.0.0.1' (using password: YES)
2022-11-24 20:06:35 5 [Warning] Access denied for user 'photoprism'@'127.0.0.1' (using password: YES)
2022-11-24 20:06:40 6 [Warning] Access denied for user 'photoprism'@'127.0.0.1' (using password: YES)

Display More

It looks like problem with access bud under ACL permission in OMV all linked folder are set to read/write access for photoprism user.

What can be wrong with it? Thanks in advance!

Photoprism docker fails to start

Participate now!

Tags