This is still happening as of 5/20/2019. I have tried rolling back all the way to 19.1-1-02 and the same results. Here are the latest log files. I notice an issue with supervisord not being on pid 7 like it was previously:
Created by...
___. .__ .__
\_ |__ |__| ____ | |__ ____ ___ ___
| __ \| |/ \| | \_/ __ \\ \/ /
| \_\ \ | | \ Y \ ___/ > <
|___ /__|___| /___| /\___ >__/\_ \
\/ \/ \/ \/ \/
https://hub.docker.com/u/binhex/
2019-05-20 08:00:40.381403 [info] System information Linux b00c02037914 4.19.41-Unraid #1 SMP Wed May 8 14:23:25 PDT 2019 x86_64 GNU/Linux
2019-05-20 08:00:40.418214 [info] PUID defined as '99'
2019-05-20 08:00:40.692285 [info] PGID defined as '100'
2019-05-20 08:00:41.234005 [info] UMASK defined as '000'
2019-05-20 08:00:41.266205 [info] Setting permissions recursively on volume mappings...
2019-05-20 08:00:41.304443 [info] Starting Supervisor...
2019-05-20 08:00:41,489 INFO Included extra file "/etc/supervisor/conf.d/nzbget.conf" during parsing
2019-05-20 08:00:41,489 INFO Set uid to user 0 succeeded
2019-05-20 08:00:41,492 INFO supervisord started with pid 6
2019-05-20 08:00:42,494 INFO spawned: 'nzbget' with pid 45
2019-05-20 08:00:42,494 INFO reaped unknown pid 7
2019-05-20 08:00:42,505 DEBG 'nzbget' stdout output:
[info] NZBGet configuration does not exist, copying default configuration file to /config/...
2019-05-20 08:00:43,506 INFO success: nzbget entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Would appreciate some guidance on a solution.