Closed gab9281 closed 1 year ago
Hi thank you for opening the issue.
Based on your logs please check your Sonarr environment variables are correct. Also, if there are no series to show from Sonarr it will crash like this too. Are you running Sonarr v3?
I am using sonarr development branch sadly. With what I see , It doesn't even connect to the database ( tried using -it )
It’s does connect to the database, your migrations / db setup was completed.
It’s crashing on Sonarr unfortunately.
Oh okay , well ... I'll wait for support then . Thanks
As an aside, I'm glad this issue exists as I couldn't figure why Midarr was crashing like this for me; I don't use Sonarr and was hoping to use Midarr to serve files I manually placed in the media folder. Is this possible at all?
As an aside, I'm glad this issue exists as I couldn't figure why Midarr was crashing like this for me; I don't use Sonarr and was hoping to use Midarr to serve files I manually placed in the media folder. Is this possible at all?
Hi, unfortunately no this is not possible. Midarr relies on both Radarr and Sonarr for an index to your media.
@trueChazza I appreciate the reply, though -- thanks for clarifying!
I was getting the same errors, then I realised I too was running on sonarr develop (and radarr nightly).
I see you're add more details to the error logs https://github.com/midarrlabs/midarr-server/issues/403#issuecomment-1703632855, big thumbs up. May I suggest mentioning in the logs to check what brand/version of sonarr / radarr they're running too, if it's failing. As it looks like at least develop isn't supported yet. (and I don't blame you, just my feedback)
PS, loving the project, and can't wait to give it a try.
Describe the bug Midarr doesn't start due to missing socket under podman
To Reproduce Steps to reproduce the behavior:
copy the docker-compose file
Expected behavior The app should be starting
Additional context
Investigation : After some investigation of the
entry-local.sh
file I was able to validate the connexion of the database with thepg_isready -q -h $DB_HOSTNAME -U $DB_USERNAME
The issue seem to stem from the fact that podman-compose does not share correctly the socket and crashed when using the
psql -Atqc "\\list $DB_DATABASE"
command.Crash log :