I am running sonarr and transmission. Sonarr no longer uses transmission. I think I have transmission screwed up. I have one on my browser (firefox) which I can see at http://localhost:9091/transmission/web/#cancel and another which I call as a program. I think one is a program and the other is a service. If I want to download a torrent I goto the one I run the transmission client, not the one in my browser that seems to do nothing but sit there. sonarr just ignores transmission. In the sonarr setup I test the connection to rarbg and it works with no problems (the test).
thank you…
Processor AMD A4-7300 APO with Radeon graphics X 2
Graphics GeForce GT 440/PCIe/SSE2 OS Type:64 bit Disk: 4.9 TB
Memory 7.7 GB
Out of the 400 items, nothing was wanted so nothing was grabbed.
Do you have logs that show an error communicating with transmission?
Are you able to test the connection to transmission?
Are things you expect to be grabbed rejected for another reason? (a manual search may be helpful to determine that).
I saw the same stuff as you and I absolutely agree. My problem was in the sheer number of different logs available and didn’t kniow which was pertinent. If you could tell me what tp search for I could do that. Another question is where these logs are stored - hard to search when I don’t have them . When I read my screen it seemed to be telling me it was in the cloud instead of my machine. Where are the logs kept? What was interesting is that there was absolutely no effort, in the debug log, to even try for a torrent. When I first set it up that was not the case. At first I thought it was how I setup the searcher (rarbg) but the test, plus the log in question, belied that one. I wonder if I would be wise to remove and re-install.
The ((log files)) have their own wiki page and indicates how you can find them (see the app data directory wiki page linked from there).
Unless there is a torrent Sonarr sees as needed it’s not going to grab anything, based on the logs nothing was needed, so nothing was grabbed. If that happens all the time and things that are wanted are missed then the logs will indicate why as well as the debug logs.
Reinstalling won’t fix anything if the configuration is the issue and is persisted during the reinstall.
I think what you are telling me is that sonarr checks for nzb’s before moving onto torrents. There are times, however, when it cannot find anything for a specific show. That means, I think, is that it also tried torrents and fail there too. Now that I know where the log files are hidden I can search them for transmission and see what they have to say. I will, therefore, search the hell out of the files for ‘transmission’ and see what they say. If there is a problem I will post it.
Ok, here is what I did. I went to the logs directory and searched all files for ‘torrent’ and ‘transmission’. I then stuck all the responses into a file that you can find here: http://pastebin.com/VFEUsU3T
There are a LOT of duplicates but I thought it was wiser just to put them all in there as I really have little idea of what I am looking at.
Hopefully, this will help to figure out what is going on.
I saw that stuff too. As far as I know its setup for sonarr but I will re-check that. Remember I am running two separate transmissions. one, I think, is the service and the other is a program (transmission.gtk I think (according to the system monitor). I use this one when I am manually grabbing torrents from extra torrent the other just lays in my firefox browser and neither spins nor weaves. I will take a closer look although it was working at one time and I didn’t think that I had changed anything. Perhaps I should get rid of both transmissions and re-install?
If I do re-install which set of installation directions should I use? (there are a lot of them )
Running two seems pretty confusing, you should be able to use one for both manual and grabs from Sonarr. Re-installing would probably be the best to tighten things up.
Not sure which folders you’ll need to save though.
I continue to mess with this. I checked the status of transmission and got an interesting result:
transmission-daemon.service - LSB: Start or stop the transmission-daemon.
Loaded: loaded (/etc/init.d/transmission-daemon; bad; vendor preset: enabled)
Active: active (running) since Mon 2017-01-23 15:29:54 PST; 3min 40s ago
Docs: man:systemd-sysv-generator(8)
Process: 28150 ExecStop=/etc/init.d/transmission-daemon stop (code=exited, status=0/SUCCESS)
Process: 1953 ExecStart=/etc/init.d/transmission-daemon start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/transmission-daemon.service
└─1972 /usr/bin/transmission-daemon --config-dir /var/lib/transmission-daemon/info
Jan 23 15:29:55 greg-movies transmission-daemon[1972]: Port Forwarding Stopped (port-forwarding.c:180)
Jan 23 15:29:55 greg-movies transmission-daemon[1972]: UDP Failed to set receive buffer: requested 4194304, got 425984 (tr-udp.c:84)
Jan 23 15:29:55 greg-movies transmission-daemon[1972]: UDP Please add the line “net.core.rmem_max = 4194304” to /etc/sysctl.conf (tr
Jan 23 15:29:55 greg-movies transmission-daemon[1972]: UDP Failed to set send buffer: requested 1048576, got 425984 (tr-udp.c:95)
Jan 23 15:29:55 greg-movies transmission-daemon[1972]: UDP Please add the line “net.core.wmem_max = 1048576” to /etc/sysctl.conf (tr
Jan 23 15:29:55 greg-movies transmission-daemon[1972]: DHT Reusing old id (tr-dht.c:307)
Jan 23 15:29:55 greg-movies transmission-daemon[1972]: DHT Bootstrapping from 78 IPv4 nodes (tr-dht.c:156)
Jan 23 15:29:55 greg-movies transmission-daemon[1972]: Using settings from “/var/lib/transmission-daemon/info” (daemon.c:528)
Jan 23 15:29:55 greg-movies transmission-daemon[1972]: Saved “/etc/transmission-daemon/settings.json” (variant.c:1266)
Jan 23 15:29:55 greg-movies transmission-daemon[1972]: transmission-daemon requiring authentication (daemon.c:554)
I could put the settings.json up if you would like to take a look at that one. I suspect I have to deal with transmission, and get that right before I can begin with sonarr. My problem, with setting this stuff up is choosing the right directions. When I google “ubuntu 16.04 setup transmission” I get a pile of hits, some running back over 10 years. Even the current ones give different directions and I think this is where I am running into trouble.
This also applies to sonarr/nzbdrone. The problem there is that config files seem to be a moving target and I keep finding directions as to how to create such a file (and these vary as well). My problem is that when I start flailing, at this stuff, I find I am really likely to screw it up.
Thanks for the reply I will continue to peer at stuff
The config file location for Sonarr only changes if the user changes and is shown in the UI (System: Info). I’m not sure about Transmisison though, I found it dead simple to setup in a docker container, but not very familiar with it’s config.