Host OS is Ubuntu Server 18; but using docker image
Ombi Applicable Logs (from /logs/ directory or the Admin page):
I checked logs via docker-compose logs -ft ombi and there's nothing useful there:
ombi | 2018-10-18T18:29:07.282457194Z [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
ombi | 2018-10-18T18:29:07.342469726Z [s6-init] ensuring user provided files have correct perms...exited 0.
ombi | 2018-10-18T18:29:07.343432989Z [fix-attrs.d] applying ownership & permissions fixes...
ombi | 2018-10-18T18:29:07.343693473Z [fix-attrs.d] done.
ombi | 2018-10-18T18:29:07.344390590Z [cont-init.d] executing container initialization scripts...
ombi | 2018-10-18T18:29:07.347672706Z [cont-init.d] 10-adduser: executing...
ombi | 2018-10-18T18:29:07.505929646Z
ombi | 2018-10-18T18:29:07.505999606Z -------------------------------------
ombi | 2018-10-18T18:29:07.506023224Z _ ()
ombi | 2018-10-18T18:29:07.506040925Z | | ___ _ __
ombi | 2018-10-18T18:29:07.506056918Z | | / __| | | / \
ombi | 2018-10-18T18:29:07.506073986Z | | \__ \ | | | () |
ombi | 2018-10-18T18:29:07.506091197Z |_| |___/ |_| \__/
ombi | 2018-10-18T18:29:07.506107879Z
ombi | 2018-10-18T18:29:07.506122918Z
ombi | 2018-10-18T18:29:07.506138859Z Brought to you by linuxserver.io
ombi | 2018-10-18T18:29:07.506154895Z We gratefully accept donations at:
ombi | 2018-10-18T18:29:07.506170599Z https://www.linuxserver.io/donate/
ombi | 2018-10-18T18:29:07.506186086Z -------------------------------------
ombi | 2018-10-18T18:29:07.506202508Z GID/UID
ombi | 2018-10-18T18:29:07.506218531Z -------------------------------------
ombi | 2018-10-18T18:29:07.515934551Z
ombi | 2018-10-18T18:29:07.515988582Z User uid: 1000
ombi | 2018-10-18T18:29:07.516002980Z User gid: 1000
ombi | 2018-10-18T18:29:07.516014372Z -------------------------------------
ombi | 2018-10-18T18:29:07.516025006Z
ombi | 2018-10-18T18:29:07.528835854Z [cont-init.d] 10-adduser: exited 0.
ombi | 2018-10-18T18:29:07.531128803Z [cont-init.d] 30-config: executing...
ombi | 2018-10-18T18:29:18.890067702Z [cont-init.d] 30-config: exited 0.
ombi | 2018-10-18T18:29:18.892209311Z [cont-init.d] done.
ombi | 2018-10-18T18:29:18.894584655Z [services.d] starting services
ombi | 2018-10-18T18:29:18.912617013Z [services.d] done.
ombi | 2018-10-18T18:29:19.125903602Z Hello, welcome to Ombi
ombi | 2018-10-18T18:29:19.125923294Z Valid options are:
ombi | 2018-10-18T18:29:19.125926542Z Ombi 3.0.3919-master
ombi | 2018-10-18T18:29:19.125928610Z Copyright (C) 2018 Ombi
ombi | 2018-10-18T18:29:19.125930724Z
ombi | 2018-10-18T18:29:19.125932727Z --host (Default: http://*:5000) Set to a semicolon-separated (;) list
ombi | 2018-10-18T18:29:19.125934680Z of URL prefixes to which the server should respond. For example,
ombi | 2018-10-18T18:29:19.125936552Z http://localhost:123. Use "*" to indicate that the server should
ombi | 2018-10-18T18:29:19.125938625Z listen for requests on any IP address or hostname using the
ombi | 2018-10-18T18:29:19.125946900Z specified port and protocol (for example, http://*:5000). The
ombi | 2018-10-18T18:29:19.125949074Z protocol (http:// or https://) must be included with each URL.
ombi | 2018-10-18T18:29:19.125951130Z Supported formats vary between servers.
ombi | 2018-10-18T18:29:19.125953041Z
ombi | 2018-10-18T18:29:19.125955097Z --storage Storage path, where we save the logs and database
ombi | 2018-10-18T18:29:19.125956982Z
ombi | 2018-10-18T18:29:19.125958770Z --baseurl The base URL for reverse proxy scenarios
ombi | 2018-10-18T18:29:19.125960662Z
ombi | 2018-10-18T18:29:19.125962633Z --help Display this help screen.
ombi | 2018-10-18T18:29:19.125964642Z
ombi | 2018-10-18T18:29:19.125966436Z --version Display version information.
ombi | 2018-10-18T18:29:19.125968261Z
ombi | 2018-10-18T18:29:19.125970069Z
ombi | 2018-10-18T18:29:19.125971817Z
ombi | 2018-10-18T18:29:20.257643295Z We are running on
ombi | 2018-10-18T18:29:20.380812602Z /opt/ombi
ombi | 2018-10-18T18:29:23.019537481Z Hosting environment: Production
ombi | 2018-10-18T18:29:23.019561890Z Content root path: /opt/ombi
ombi | 2018-10-18T18:29:23.019687348Z Now listening on: http://[::]:3579
ombi | 2018-10-18T18:29:23.019698068Z Application started. Press Ctrl+C to shut down.
ombi | 2018-10-18T18:30:07.432207508Z info: Ombi.Schedule.Jobs.Plex.PlexContentSync[0]
ombi | 2018-10-18T18:30:07.432250365Z Starting Plex Content Cacher
ombi | 2018-10-18T18:30:07.435590590Z info: Ombi.Schedule.Jobs.Plex.PlexContentSync[0]
ombi | 2018-10-18T18:30:07.435609974Z Starting to cache the content on server Nami
ombi | 2018-10-18T18:34:11.241775529Z info: Ombi.Notifications.Agents.MobileNotification[0]
ombi | 2018-10-18T18:34:11.241803800Z there are no admins to send a notification for RequestAvailable, for agent Mobile
And there's not really any logs under the Logs directory (logs with today's timestamp only have 3 log lines in it, and those were from hours ago).
Problem Description:
I set up and enabled Radarr in settings. I tested the connection and it passes. I had someone log in and add a few movies to the request queue. This user was imported and has auto-approve status. Once these movies were added, they did not get added to the Wanted list in Radarr.
The integration with Radarr is confusing. I'm not sure how it's supposed to work. There's a Jobs section in Ombi that makes me think that every 15th minute of each hour, it's supposed to sync the request list to Radarr, but this never happened and there's no logs I could find to show that it even was attempted. I also don't see a mechanism I can use to force Ombi to push the requested movies to Radarr.
I need some help understanding how this works, the wiki is pretty bare (or maybe I just haven't found the relevant page for this).
Ombi build Version:
V 3.0.3919
Update Branch:
Using docker image
Media Sever:
Plex
Operating System:
Host OS is Ubuntu Server 18; but using docker image
Ombi Applicable Logs (from
/logs/
directory or the Admin page):I checked logs via
docker-compose logs -ft ombi
and there's nothing useful there:And there's not really any logs under the
Logs
directory (logs with today's timestamp only have 3 log lines in it, and those were from hours ago).Problem Description:
I set up and enabled Radarr in settings. I tested the connection and it passes. I had someone log in and add a few movies to the request queue. This user was imported and has auto-approve status. Once these movies were added, they did not get added to the Wanted list in Radarr.
The integration with Radarr is confusing. I'm not sure how it's supposed to work. There's a Jobs section in Ombi that makes me think that every 15th minute of each hour, it's supposed to sync the request list to Radarr, but this never happened and there's no logs I could find to show that it even was attempted. I also don't see a mechanism I can use to force Ombi to push the requested movies to Radarr.
I need some help understanding how this works, the wiki is pretty bare (or maybe I just haven't found the relevant page for this).