Docker Sonarr/Radarr SMA not processing files

[tscibilia]

@mdhiggins I've been around the issues for a while now trying to get this wonderful script working for me. I switched my setup a couple of times, now I'm running everything in docker containers on a coreOS machine. Separately, I still have all my data served from my Synology NAS (btrsfs). I put references to my settings up on hastebin to limit the length of this post

My Issues:

• It seems like sonarr/radarr never trigger the custom script to run after the file is downloaded!
• The file gets removed from the activity list but remains in deluge.
• I checked the file /var/log/sickbeard_mp4_automator/index.log but nothing was logged.
• Please check my sonarr log to see if you can glean any info I'm missing.

Also, this is my autoProcess.ini. I also chown-ed the file to make sure UID/GID 1044/100 owned the file.

Docker:

• I've setup the docker-compose file similar to your suggestion here.
  My docker-compose.yml looks like this...
• I also saw the issue Radarr-SMA ffmpeg binary not found #926 and I feel like I have it all setup right (no relative paths, etc).
• The reason I made docker volumes for the config files is because of a btrfs error I was getting with SQlite (see here)

Sonarr/Radarr:

• I also set my sonarr custom script to look just like the image you posted with the following info...
  Path: /usr/local/bin/sma/env/bin/python3
  Arg: /usr/local/bin/sma/sickbeard_mp4_automator/postSonarr.py
• I disabled Completed Download Handling in sonarr & radarr

Deluge:

I'm using a custom deluge setup currently to handle conversions that I need to manually trigger for the time being, but I'd like to have the sonarr/radarr script call the video conversion to take place (as it seems you intended).

As usual, any help would be appreciated! Thanks!

[mdhiggins]

Are you using completed download handling for Sonarr/Radarr? From: tscibilia Sent: Monday, November 5, 2018 1:27 PM To: mdhiggins/sickbeard_mp4_automator Cc: Michael Higgins; Mention Subject: [mdhiggins/sickbeard_mp4_automator] Docker Sonarr/Radarr SMA notprocessing files (#951) @mdhiggins I've been around the issues for a while now trying to get this wonderful script working for me. I switched my setup a couple of times, now I'm running everything in docker containers on a coreOS machine. Separately, I still have all my data served from my Synology NAS (btrsfs). I put references to my settings up on hastebin to limit the length of this post My Issues: • It seems like sonarr/radarr never trigger the custom script to run after the file is downloaded! • The file gets removed from the activity list but remains in deluge. • I checked the file /var/log/sickbeard_mp4_automator/index.log but nothing was logged. • Please check my sonarr log to see if you can glean any info I'm missing. Also, this is my autoProcess.ini. I also chown-ed the file to make sure UID/GID 1044/100 owned the file. Docker: • I've setup the docker-compose file similar to your suggestion here. My docker-compose.yml looks like this... • I also saw the issue #926 and I feel like I have it all setup right (no relative paths, etc). • The reason I made docker volumes for the config files is because of a btrfs error I was getting with SQlite (see here) Sonarr/Radarr: • I also set my sonarr custom script to look just like the image you posted with the following info... Path: /usr/local/bin/sma/env/bin/python3 Arg: /usr/local/bin/sma/sickbeard_mp4_automator/postSonarr.py • I disabled Completed Download Handling in sonarr & radarr Deluge: I'm using a custom deluge setup currently to handle conversions that I need to manually trigger for the time being, but I'd like to have the sonarr/radarr script call the video conversion to take place (as it seems you intended). As usual, any help would be appreciated! Thanks! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[tscibilia]

no, i turned it off. I thought that was one of the requirements to get it to process.
I'll turn it on and see what happens?

[mdhiggins]

Yeah the docker setup I use doesn’t bother with the post downloader scripts and just uses completed download handling The only advantage of NOT using it is that you can trigger the conversions before the files are passed back to Sonarr/Radarr but for most setups that doesn’t matter but it introduces another point of potential failure so you could try turning completed download handling on. It seems like from your logs that the files are never sent back to Sonarr/Radarr and therefore they don't get their final processing sweep done because that is trigger on passback. Without completed download handling though no files are ever sent back unless you have properly configured your postDeluge and postNZBGet scripts From: tscibilia Sent: Monday, November 5, 2018 1:33 PM To: mdhiggins/sickbeard_mp4_automator Cc: Michael Higgins; Mention Subject: Re: [mdhiggins/sickbeard_mp4_automator] Docker Sonarr/Radarr SMA notprocessing files (#951) no, i turned it off. I thought that was one of the requirements to get it to process. I'll turn it on and see what happens? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[tscibilia]

Ah, ok.
But I do want the files converted into mp4 format as set in the ini file. Will that happen with the completed download handling ON? I thought I read that the postSonarr file can process video conversions?

I'll give it a go tonight/tomorrow with the new settings and see what happens. Thanks!

[mdhiggins]

Yeah the conversion just shifts to postSonarr/postRadarr, it will still happen

[tscibilia]

HA HA! I think it just worked!
I just checked and it seems to have run fine and logged to the container's /var/log/directory

I'm gonna verify a few more downloads before I close this, but thank you so much!
Please let me know if you have a way to donate.

2018-11-05 18:37:17 - SonarrPostConversion - INFO - Sonarr extra script post processing started.
2018-11-05 18:37:17 - readSettings - INFO - /usr/local/bin/sma/env/bin/python3
2018-11-05 18:37:17 - SonarrPostConversion - INFO - Processing /tv/Doctor Who (2005)/Season 11/Doctor Who (2005) - S11E05 - The Tsuranga Conundrum.mkv.
2018-11-05 18:37:17 - mkvtomp4 - INFO - Reading video stream.
2018-11-05 18:37:17 - mkvtomp4 - INFO - Video codec detected: h264.
2018-11-05 18:37:17 - mkvtomp4 - INFO - Pix Fmt: yuv420p.
2018-11-05 18:37:17 - mkvtomp4 - INFO - Profile: High.
2018-11-05 18:37:17 - mkvtomp4 - INFO - Reading audio streams.
2018-11-05 18:37:17 - mkvtomp4 - INFO - Audio detected for stream #1: aac [eng].
2018-11-05 18:37:17 - mkvtomp4 - INFO - Creating audio stream 0 from source stream 1.
2018-11-05 18:37:17 - mkvtomp4 - WARNING - Unable to determine audio bitrate from source stream 1, defaulting to 256 per channel.
2018-11-05 18:37:17 - mkvtomp4 - INFO - Audio Track is number 1 setting disposition to default
2018-11-05 18:37:17 - mkvtomp4 - INFO - Reading subtitle streams.
2018-11-05 18:37:17 - mkvtomp4 - INFO - Subtitle detected for stream #2: subrip [und].
2018-11-05 18:37:17 - mkvtomp4 - INFO - Creating subtitle stream 0 from source stream 2.
2018-11-05 18:37:17 - mkvtomp4 - ERROR - No valid subtitle language specified, cannot download subtitles.
2018-11-05 18:37:17 - mkvtomp4 - INFO - Starting conversion.
2018-11-05 18:37:30 - mkvtomp4 - INFO - /tv/Doctor Who (2005)/Season 11/Doctor Who (2005) - S11E05 - The Tsuranga Conundrum.mp4 created.
2018-11-05 18:37:32 - SonarrPostConversion - INFO - Tagging /tv/Doctor Who (2005)/Season 11/Doctor Who (2005) - S11E05 - The Tsuranga Conundrum.mkv with ID 78804 season 11 episode 5.
2018-11-05 18:37:41 - tvdb_mp4 - INFO - Tagging file: /tv/Doctor Who (2005)/Season 11/Doctor Who (2005) - S11E05 - The Tsuranga Conundrum.mp4.
2018-11-05 18:37:41 - tvdb_mp4 - INFO - Trying to write tags.
2018-11-05 18:37:41 - tvdb_mp4 - INFO - Tags written successfully.
2018-11-05 18:37:41 - mkvtomp4 - INFO - Relocating MOOV atom to start of file.
2018-11-05 18:37:41 - qtfaststart - INFO - Removing free atom at 32 (8 bytes)
2018-11-05 18:37:41 - qtfaststart - INFO - Patching stco with 142551 entries
2018-11-05 18:37:41 - qtfaststart - INFO - Patching stco with 142548 entries
2018-11-05 18:37:41 - qtfaststart - INFO - Patching stco with 1036 entries
2018-11-05 18:37:41 - qtfaststart - INFO - Writing output...
2018-11-05 18:37:51 - SonarrPostConversion - INFO - Sonarr response: ID 1053364 started.
2018-11-05 18:37:51 - SonarrPostConversion - INFO - {'body': {'trigger': 'manual', 'name': 'RescanSeries', 'sendUpdatesToClient': True, 'seriesId': 70, 'updateScheduledTask': True, 'completionMessage': 'Completed'}, 'state': 'started', 'id': 1053364, 'sendUpdatesToClient': True, 'trigger': 'manual', 'queued': '2018-11-05T18:37:50.715993Z', 'startedOn': '2018-11-05T18:37:50.715993Z', 'manual': True, 'priority': 'normal', 'updateScheduledTask': True, 'started': '2018-11-05T18:37:51.05712Z', 'stateChangeTime': '2018-11-05T18:37:51.05712Z', 'name': 'RescanSeries', 'status': 'started'}
2018-11-05 18:37:51 - SonarrPostConversion - INFO - Requesting episode information from Sonarr for series ID 70.
2018-11-05 18:37:51 - SonarrPostConversion - INFO - started
2018-11-05 18:38:01 - SonarrPostConversion - INFO - Command completed
2018-11-05 18:38:01 - SonarrPostConversion - INFO - {'body': {'trigger': 'manual', 'name': 'RescanSeries', 'sendUpdatesToClient': True, 'seriesId': 70, 'updateScheduledTask': True, 'completionMessage': 'Completed'}, 'duration': '00:00:06.3245690', 'name': 'RescanSeries', 'updateScheduledTask': True, 'sendUpdatesToClient': True, 'state': 'completed', 'trigger': 'manual', 'queued': '2018-11-05T18:37:50.715993Z', 'ended': '2018-11-05T18:37:57.381689Z', 'startedOn': '2018-11-05T18:37:50.715993Z', 'priority': 'normal', 'id': 1053364, 'stateChangeTime': '2018-11-05T18:37:51.05712Z', 'started': '2018-11-05T18:37:51.05712Z', 'manual': True, 'message': 'Completed', 'status': 'completed'}
2018-11-05 18:38:01 - SonarrPostConversion - INFO - Requesting updated episode information from Sonarr for series ID 70.
2018-11-05 18:38:01 - SonarrPostConversion - INFO - Sending PUT request with following payload:
2018-11-05 18:38:01 - SonarrPostConversion - INFO - {'hasFile': True, 'airDateUtc': '2018-11-04T18:45:00Z', 'airDate': '2018-11-04', 'episodeFile': {'relativePath': 'Season 11/Doctor Who (2005) - S11E05 - The Tsuranga Conundrum.mp4', 'path': '/tv/Doctor Who (2005)/Season 11/Doctor Who (2005) - S11E05 - The Tsuranga Conundrum.mp4', 'id': 81975, 'mediaInfo': {'videoCodec': 'x264', 'audioCodec': 'AAC', 'audioChannels': 2.0}, 'qualityCutoffNotMet': False, 'size': 369682659, 'dateAdded': '2018-11-05T18:37:56.888694Z', 'seriesId': 70, 'quality': {'quality': {'source': 'television', 'resolution': 480, 'name': 'SDTV', 'id': 1}, 'revision': {'version': 1, 'real': 0}}, 'seasonNumber': 11}, 'id': 9755, 'overview': '“Risk to life: absolute.” Injured and stranded in the wilds of a far-flung galaxy, The Doctor, Yaz, Graham and Ryan must band together with a group of strangers to survive against one of the universe’s most deadly — and unusual — creatures.', 'episodeFileId': 81975, 'unverifiedSceneNumbering': False, 'episodeNumber': 5, 'monitored': True, 'seriesId': 70, 'absoluteEpisodeNumber': 135, 'seasonNumber': 11, 'title': 'The Tsuranga Conundrum'}
2018-11-05 18:38:01 - SonarrPostConversion - INFO - PUT request returned:
2018-11-05 18:38:01 - SonarrPostConversion - INFO - {'hasFile': True, 'airDateUtc': '2018-11-04T18:45:00Z', 'airDate': '2018-11-04', 'episodeFile': {'relativePath': 'Season 11/Doctor Who (2005) - S11E05 - The Tsuranga Conundrum.mp4', 'path': '/tv/Doctor Who (2005)/Season 11/Doctor Who (2005) - S11E05 - The Tsuranga Conundrum.mp4', 'id': 81975, 'mediaInfo': {'videoCodec': 'x264', 'audioCodec': 'AAC', 'audioChannels': 2.0}, 'qualityCutoffNotMet': False, 'size': 369682659, 'dateAdded': '2018-11-05T18:37:56.888694Z', 'seriesId': 70, 'quality': {'quality': {'source': 'television', 'resolution': 480, 'name': 'SDTV', 'id': 1}, 'revision': {'version': 1, 'real': 0}}, 'seasonNumber': 11}, 'id': 9755, 'overview': '“Risk to life: absolute.” Injured and stranded in the wilds of a far-flung galaxy, The Doctor, Yaz, Graham and Ryan must band together with a group of strangers to survive against one of the universe’s most deadly — and unusual — creatures.', 'series': {'firstAired': '2005-03-26T00:00:00Z', 'tags': [], 'titleSlug': 'doctor-who-2005', 'seasonCount': 11, 'imdbId': 'tt0436992', 'tvRageId': 3332, 'ratings': {'value': 9.4, 'votes': 905}, 'profileId': 2, 'runtime': 45, 'qualityProfileId': 2, 'certification': 'TV-PG', 'sortTitle': 'doctor who 2005', 'lastInfoSync': '2018-11-05T16:01:45.183185Z', 'tvdbId': 78804, 'seasons': [{'monitored': False, 'seasonNumber': 0}, {'monitored': True, 'seasonNumber': 1}, {'monitored': True, 'seasonNumber': 2}, {'monitored': True, 'seasonNumber': 3}, {'monitored': True, 'seasonNumber': 4}, {'monitored': True, 'seasonNumber': 5}, {'monitored': True, 'seasonNumber': 6}, {'monitored': True, 'seasonNumber': 7}, {'monitored': True, 'seasonNumber': 8}, {'monitored': True, 'seasonNumber': 9}, {'monitored': True, 'seasonNumber': 10}, {'monitored': True, 'seasonNumber': 11}], 'images': [{'coverType': 'fanart', 'url': 'https://www.thetvdb.com/banners/fanart/original/5bbce25777d44.jpg'}, {'coverType': 'banner', 'url': 'https://www.thetvdb.com/banners/graphical/5ba3fac3a4813.jpg'}, {'coverType': 'poster', 'url': 'https://www.thetvdb.com/banners/posters/5bbce35987375.jpg'}], 'seriesType': 'standard', 'cleanTitle': 'doctorwho2005', 'id': 70, 'airTime': '18:45', 'overview': 'The Doctor is an alien Time Lord from the planet Gallifrey who travels through all of time and space in the TARDIS. The Doctor has a long list of friends and companions who have shared journeys along the way. Instead of dying, the Doctor is able to “regenerate” into a new body, taking on a new personality with each regeneration.', 'year': 2005, 'seasonFolder': True, 'genres': ['Adventure', 'Drama', 'Science-Fiction'], 'path': '/tv/Doctor Who (2005)', 'useSceneNumbering': False, 'network': 'BBC One', 'monitored': True, 'tvMazeId': 210, 'added': '2017-08-17T19:26:02.594821Z', 'status': 'continuing', 'title': 'Doctor Who (2005)'}, 'episodeFileId': 81975, 'unverifiedSceneNumbering': False, 'episodeNumber': 5, 'monitored': True, 'seriesId': 70, 'absoluteEpisodeNumber': 135, 'seasonNumber': 11, 'title': 'The Tsuranga Conundrum'}
2018-11-05 18:38:01 - SonarrPostConversion - INFO - Sonarr monitoring information updated for episode The Tsuranga Conundrum.

[mdhiggins]

Glad its working! keep me posted

[tscibilia]

Oh man. it works so well!
Thanks for all your hard work.

[CoderKiwi]

@tscibilia I've been trying to figure out where the logs were in the sonarr-sma Docker container for a while. Thanks for the tip!

[CoderKiwi]

@mdhiggins Is there any documentation on how to set up sonarr-sma and radarr-sma? I don't see it in the README. I'm wondering if others who are using Docker may find that useful.

[mdhiggins]

Not aside from what’s documented on the docket container readme and in the issues discussed here

…

Sent from my iPhone

On Dec 14, 2018, at 9:39 PM, CoderKiwi ***@***.***> wrote: @mdhiggins Is there any documentation on how to set up sonarr-sma and radarr-sma? I don't see it in the README. I'm wondering if others who are using Docker may find that useful. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.