-
After some minutes of running photoprism, it starts to show errors in the UI (either "no x found" or "connect: connection refused"). There are no error messages in the MariaDB log during that state. Connecting to the DB using the mysql CLI on the MariaDB docker container is still possible. The log of PhotoPrism is pasted below (using To get the system working again, I have to restart both containers (MariaDB and PhotoPrism). I am using PhotoPrism® Plus Docker is running in version There is no swap space configured, because there is no built in option to do that in Unraid and I do not know how to savely enable it. I think it should not be required because of the installed 32 GB of memory. The originals folder already contains 228G of image files. Because I filled in a lot of images in a short time I can not tell if the problems started at some point importing images. I went though the troubleshooting guide but found no hint what could cause the connection errors. Could you please give me some advice? 1st log ("metadata: running face recognition" => "dial tcp 10.1.0.10:3306: connect: connection refused")
2nd log ("closing bad idle connection: connection reset by peer")
3rd log ("metadata: running face recognition" => "dial tcp 10.1.0.10:3306: connect: connection refused")
4th log ("closing bad idle connection: connection reset by peer")
5th log ("metadata: running face recognition" => "closing bad idle connection: connection reset by peer")
6th log ("metadata: running face recognition" => "dial tcp 10.1.0.10:3306: connect: connection refused")
7th log ("metadata: running face recognition" => "closing bad idle connection: connection reset by peer")
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
10.1.x.x is not a default internal Docker IP range, so I would check your DNS and network configuration first. |
Beta Was this translation helpful? Give feedback.
-
Since I use the host name in the environment variable |
Beta Was this translation helpful? Give feedback.
Since I use the host name in the environment variable
PHOTOPRISM_DATABASE_SERVER
instead of the fixed IP, the connection issues are gone, while still using a non default network config. I have no idea why this happens, but I am happy to have a flawlessly working photorpism app now.