I’d been using an old version (git based, can’t remember which version sorry) and had no issues with how FreeBSD started sickrage - but I kept having issues where sometimes the whole daemon would hang, so I pulled and switched to master branch to get latest. When it starts up now it does some extra pip bootstrapping and tries to install a list of modules. For whatever reason this goes in a loop - the init script (daemon launcher) starts sickrage, which spawns pip installs, which must be failing as sickrage then exits, and the daemon relaunches it, pip install, fails, restarts, and so on.
However when I run it manually (as the unprivileged user I run it as) I can see the pip installs work and sickrage launches happily, but if I then go back to the service based startup (which should be running it as same user, same params etc) it still fails.
Only thing I can think of is the service script/daemon tool is not behaving 100% like a normal user, but I’m not too familiar with python3 on freebsd to know what to look for as to why it may be failing (e.g. path problem etc). Nothing is in the logs either to help pinpoint the issue.
Anyone got any ideas? Thanks!