Skip to content
This repository has been archived by the owner on Aug 3, 2024. It is now read-only.

Since 7/27 no longer receiving common from sonarr and a-train #215

Open
GettingTechnicl opened this issue Aug 27, 2023 · 0 comments
Open

Comments

@GettingTechnicl
Copy link

GettingTechnicl commented Aug 27, 2023

I'm here because I'm at a complete loss. I don't believe that it's necessary to share my config file at this time.

I've had a-train set up with autoscan and notifying plex for changes for some time and all working well.

At some point we also incorporated sonarr and Radarr to notify autoscan as well. However we had the paths wrong so it wasn't working right.

Regardless of it not working, sonarr and Radarr were still talking to autoscan.

Last week I resolved the issue of the arr apps having the incorrect path as we had noticed nothing was updating in plex for new downloads.

Since, we've noticed we're getting updates right away for movies, but not TV shows.

I investigated earlier and I was able to see from the autoscan log that the last time it heard from a-train and sonarr (not including the test last week when I reconfigured paths) was 7/27.

Regardless if pathing is right or wrong, I should be seeing communication in autoscan that it's being notified by a-train and sonarr.

This is driving me in circles in my head. Radarr and sonarr set up exactly the same.... But sonarr doesn't work. Kind of seems like it could be a sonarr issue. But then when you bring in that a train and sonarr stopped communicating with autoscan same day 7/27, it almost seems like more of an autoscan issue.

Has anyone experienced anything similar or any advice to get me through this?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant