bobbintb

Your torrent client is probably downloading it to one directory and Sonarr is looking for it in the wrong place. The log information you provided doesn't provide any insight. It appears to be from when the download was sent to transmission. What does the log say when it tries to import?

Why is that odd?

I'm pretty sure that's just a remnant from Sonarr's development. I see it in all the logs.

Hard to say. It's just saying it cannot import the episode. It should give a reason somewhere in the log. Check the activity page. The CIFS error has to do with a samba share. The two might be related. Maybe it cannot access your mounted share where your files are stored. From the looks of things, I think you've got problems that go way beyond Sonarr.

Are you just trying to power down now?

Ah, yes. Good catch.

That looks right. Input in the terminal.

The correct command to get to the docker shell is: docker exec -it rutorrent bash I don't think midnight commander will help as I don't believe the rutorrent docher has it. To install a plugin you'd have to copy it to the docker config folder. Then within the docker shell, copy it to the plug-in folder. But this will get wiped out after updates. You might be able to specify a plugin directory in the config folder but I'm not sure.

It shouldn't break the other containers. Each docker should have its own config directory. Try this: chmod 755 -R -f /your/sonarr/config/directory

It says the disk is full: But that may just mean it cannot write to the location. If it isn't full, it seems like a permissions issue, as if it cannot write to the /config folder.

It should already since the config files aren't saved in the image. The issue I've had is with restarts, not necessarily updates. If so, shut down the docker, manually edit the config file, and start it again.

I know it has been discussed here before. I don't think anything has come of it yet. It's been a while since I've looked into it. I know there are GUI frontends out there but I don't think any of them are webUIs yet. There are talks of official webUIs though.

You might just be able to mount the path. vi isn't so bad once you get used to it, as I recently had to do. Some dockers don't even have vi, oddly enough.

I'll probably go back to the stable now as well. I was only on EAP because the newsletter was broken.

As @CHBMB said, it isn't supported. But to do it just hit the update button in Ombi, under where you change the branch. I have found subsequent updates to be problematic. You have to remove the docker and re-add it and switch to EAP again to do so.

There are many ways to do it, just depends on what you need/want. I would probably use this to backup to another folder and then use rclone to backup that folder. The reason being is the backup app is capable of stopping dockers cleanly before backup and other things that rclone cannot.

Jackett should just send the search results back to Sonarr and then Sonarr should send the torrent to Deluge to download. Honestly, I've never seen that "manual download black hole" option in Jacket before but I know it's not needed with Sonarr. All Jackett does it act as a middle man between Sonarr and any indexer that Sonarr doesn't directly support. If searching in Sonarr triggers a search in Jackett, it sounds like it's working properly. My suspicion is that "black hole" setting is screwing things up. If the test connection to Jackett is working in Sonarr and Jackett "test" to your indexer is working, that should be all you need. Get rid of any setting in Jackett related "black hole" and try again. Also, check the Sonarr logs to make sure it is receiving the search results from Jackett.

I'm confused as to what you are saying. Which logs? Jackett or Sonarr? This makes it sound like Jackett it working with Sonarr just fine. If by "it" you mean Sonarr, then it sounds like the issue is between Sonarr and Deluge. What folder? You say you have it set as downloads but you are talking about 3 different programs. I don't know what downloads folder you are referring to. Well, now this seems to conflict with what you said in the first statement I quoted, if searches and results are working fine. Lastly, your settings photos aren't useful as they don't show what any of those folder are mapped to. Still, I don't know how that is relevant anyway. I thought the issue is that the results aren't getting sent. What is your issue exactly? Is Jackett not communicating with Sonarr?

For those having login issues, are you using your Plex username? It needs the username, not the email. You also have to add Plex users to Ombi that are allowed to make requests.

I did actually see that first but didn't look into it since modifying the base image would cause problems every time it is updated. I was looking for something built into the base image. But once I did look at it I realized it's just a single binary so I put it in the config folder and can call it from there. Thanks.

Most cloud providers have some kind of version control. If you get infected with ransomware and the files get overwritten just restore them from the deleted files on your cloud provider. There are ways to do what you need. You just need to plan it out.

I need to write a custom script for Sonarr. Other than bash, what options are available in this image? I specifically need something to parse JSON and I'd rather use something more adapt to the task than awk or something. It doesn't look like python is installed. It looks like perl is but I don't think the JSON module is. Anything else?

I wrote a daemon. I think it's in the rclone thread. It's much more complicated your way, even if it were possible.

I don't see how. Why does it matter if it's run within the Sonarr? It doesn't need to be accessible.