Topic Background
Continued from
Leading to:
I would suggest that you start an entirely new topic that focuses on helping you diagnose the issues with
https://github.com/evercam/evercam-server/blob/master/lib/evercam_media/repo.ex#L9
It must have had problems for some time now since exists?/1 was added over a year ago in order to add the capability of determining whether or not the repo was still responsive.
It’s configured to start up with the rest of the application here:
https://github.com/evercam/evercam-server/blob/master/lib/evercam_media.ex#L22
the supervisor strategy being
https://github.com/evercam/evercam-server/blob/master/lib/evercam_media.ex#L36
:one_for_one means that it would simply be restarted once it crashes.
Just a guess: the failures you have been witnessing may have happened shortly after the repo crashed but before it was restarted by the application. Basically scour your logs to collect any evidence that may reveal why the repo is behaving so erratically.
