Photoprism several issues

monsen · 30. Juni 2022

First of all i was astonished to see that Photoprism changed the ownership of my Fotos folder. Not quite what i would expect. It potentially breaks things for other applications.

Secondly i cannot get it to work.

When i try to access the URL, it times out.

Log is empty and here is systemctl:

Code

● pod-photoprism.service - Podman pod-photoprism.service
     Loaded: loaded (/etc/systemd/system/pod-photoprism.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2022-06-30 16:33:17 CEST; 1min 17s ago
   Main PID: 1048700 (conmon)
      Tasks: 2 (limit: 8809)
     Memory: 836.0K
        CPU: 1.232s
     CGroup: /system.slice/pod-photoprism.service
             └─1048700 /usr/bin/conmon --api-version 1 -c d2e4d4d3ee9d9dbd1d4c2a89d4d45435921ed0fe1f5ab1808b3ec7da5840f838 -u d2e4d4d3ee9d9dbd1d4c2a89d4d45435921ed0fe1f5ab1808b3ec7da5840f838 -r /usr/bin/crun -b /var/lib/containers/storage/overlay-containers/d2e4d4d3ee9d9dbd1d4c2a89d4d45435921ed0fe1f5ab1808b3ec7da58>

Jun 30 16:33:15 debNAS systemd[1]: Starting Podman pod-photoprism.service...
Jun 30 16:33:16 debNAS podman[1048525]: 2022-06-30 16:33:16.137417471 +0200 CEST m=+0.638962398 container create d2e4d4d3ee9d9dbd1d4c2a89d4d45435921ed0fe1f5ab1808b3ec7da5840f838 (image=k8s.gcr.io/pause:3.2, name=18409166bb35-infra)
Jun 30 16:33:16 debNAS podman[1048525]: 2022-06-30 16:33:16.203659687 +0200 CEST m=+0.705204565 pod create 18409166bb3585b1113686e937d0fa39a3d4bf99dd14dc83b53e0933368e1a78 (image=, name=photoprism)
Jun 30 16:33:16 debNAS podman[1048525]: 18409166bb3585b1113686e937d0fa39a3d4bf99dd14dc83b53e0933368e1a78
Jun 30 16:33:17 debNAS podman[1048572]: 2022-06-30 16:33:17.455226044 +0200 CEST m=+1.191714953 container init d2e4d4d3ee9d9dbd1d4c2a89d4d45435921ed0fe1f5ab1808b3ec7da5840f838 (image=k8s.gcr.io/pause:3.2, name=18409166bb35-infra)
Jun 30 16:33:17 debNAS podman[1048572]: 2022-06-30 16:33:17.726698348 +0200 CEST m=+1.463187244 container start d2e4d4d3ee9d9dbd1d4c2a89d4d45435921ed0fe1f5ab1808b3ec7da5840f838 (image=k8s.gcr.io/pause:3.2, name=18409166bb35-infra)
Jun 30 16:33:17 debNAS podman[1048572]: 18409166bb3585b1113686e937d0fa39a3d4bf99dd14dc83b53e0933368e1a78
Jun 30 16:33:17 debNAS podman[1048572]: 2022-06-30 16:33:17.726829964 +0200 CEST m=+1.463318897 pod start 18409166bb3585b1113686e937d0fa39a3d4bf99dd14dc83b53e0933368e1a78 (image=, name=photoprism)
Jun 30 16:33:17 debNAS systemd[1]: Started Podman pod-photoprism.service.

Alles anzeigen

GaoGao · 25. September 2022

Hi,

I have a similar issue, time out or a connection refused, often the Photoprism page is not responding. When this appends Nmap show the 2342 IP port as "filtered", but I am on a flat home network, there is no firewall or so, internaly. My OpenMediaVault is on Linux Debian and command like netstat show the port open and listening. I created a firewall rule on the NAS to force open the port 2342, but to no effect. All the other ports and associated services are accessible (OMV, File browser plugins, Web console). It is just Photoprism returning a time out or a "connection refused" about 50% of the time until without any specific reason it works again. I can't reproduce the issue, it seems totally random. My guess is something odd with the Debian resource's allocation for the Photoprism processes.

Photoprism several issues

Jetzt mitmachen!

Tags