Closed zguithues closed 1 year ago
OMG i can't believe i spent ALLLLLL that time banging my head against the fact that i am very stupid and used the wrong port... after looking at sonarr's 8989, i transcribed radarr to 7979. i swear i double-checked it, but here we are...
It's working fine and I'm ashamed...
Hope everyone has a nice day.
Is there an existing issue for this?
Current Behavior
When i start a fresh docker compose of radarr it spits out a bunch of db messages then
stops.
no web interface. log ends with:there are also a bunch of:
2023-01-14 14:18:52.8|Info|AppFolderInfo|Data directory is being overridden to [/config]
if i restart it the log is much shorter. both are attached.
restart log ends with:
Fresh install radarr.log: (it cuts off the top, i can make effort to get the ENTIRE log if needed. radarr-fresh.txt
restarted radarr.log: radarr-restart.txt
output from docker logs from reboot docker log from reboot.txt
This is supposed to be part of a stack of other dockers including sonarr, jackett, etc. i'm rebuilding a system i've been using for a long time. I have tried a multitude of options and permission changes. even splitting it out into it's own compose just in case. i also tried copying the config from my previous install. it chugs a bunch info, not finding movies and such, then it just stops again in a similar manor.
I also tried it on an EXT4 volume, incase the btrfs rootfs was creating the issue. same results.
Only thing i haven't tried is another Linux os...
Expected Behavior
it should start up and present the web interface.
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
Container logs