commands to use for headless system via SSH

[NeilP]

Not sure how to put this question..So basic question first:

Is it possible via ssh to force transmission to search/re-announce/ find the tracker for a specific torrent or all torrents?

Transmission is running on a FreeNAS (FreeBSD) headless system with ssh enabled Transmission 2.11

The only one page I have found
https://trac.transmissionbt.com/wiki/HeadlessUsage
give no useful ssh commands, and is due to be deleted anyway

It has been running fine for a few years now, but after ISP connection issues I reset and re flashed the router..now I can't get Transmission to work correctly with a private tracker. Torrents from tracker.example.com work fine, just this one tracker (xbtmusic.org / Pedro's)


The default port 51413 is open to the FreeNAS box, and P2P is specifically enabled in the router.

In the webgui I just get

xbtmusic.org:2710
Announce error: tracker did not respond - Today 11:52:39 AM
Next announce in 26 min 8 seconds
Scrape error: tracker did not respond - Today 11:36:06 AM
Seeders: N/A
Leechers: N/A
Downloads: N/A

Can I force these torrent to refresh any way via ssh?

[rb07]

Announce error: tracker did not respond - Today 11:52:39 AM
Next announce in 26 min 8 seconds
Scrape error: tracker did not respond - Today 11:36:06 AM
Seeders: N/A
Leechers: N/A
Downloads: N/A

Can I force these torrent to refresh any way via ssh?

Yes, sometimes (the operation has time limits, so you don't abuse a tracker), but you are barking at the wrong tree.

First: stop using the wrong terms, its not "ssh commands", ssh has nothing to do.

Second: the real problem is either (1) the tracker is down / out of commission / overloaded / not responding to you (a.k.a. you have been blacklisted or banned); or (2) you have a DNS problem, bad configuration / the tracker name doesn't resolve, or it resolves to a bogus address.

Simple solution when the problem is not a DNS one: pause the torrent, then start it again, wait a few seconds and see if the tracker info shows. Abusing this procedure is what gets you banned, tracker sites usually have rules about how many times per hour, per torrent (?), you are allowed to query the tracker; Transmission also receives that information, and it tries not to query too often; that's the reason it won't let you force a scrape/announce (transmission-remote --reannounce -t ...) if you try too often.

[NeilP]

I am not using the wrong terms, I am using the exact terms I intended to use. Maybe I misunderstand the access and level of control that an ssh shell can have on running processes on the box, hence my question. I wnated to see if there was a way to force a query of the tracker from a remote terminal rather than the webgui
The webgui has very limited control over individual torrents, apart from the Pause and Restart option, so if it is possible to access the Transmission process from the local console on the box, I was wondering if it was possible to access them via a Mac terminal window and ssh, so maybe in a round-about way you are saying it is not possible, but I was using the exact terminology I meant to.

I know I have not been banned as I have only within a few hours of posting been in contact with one of the mods at the site, and all is now well, They did have an issue but all is now well again, and the problem seems to be my end.

Multiple re boots of the NAS box and re starting the service have resulted in no joy.

[blacke4dawn]

There are no specific ssh-commands unless you are talking about SSH itself, the correct term is shell commands (cmd for short). Those commands are exactly the same regardless of if the shell is a local one on a headless system, a terminal shell run on top of a graphical system, a shell run via SSH or any other remote control method, or any other method that produces a shell. The only differences you might be dealing with are specific to the actual shell used, but never in how said shell is accessed.

Anything you can do via the cmd without needing to restart the server is done via the tool transmission-remote, which should be installed together with the server version.

You mentioned that the site had problems so depending on what said problem was it might take some time before the fix "propagates" to you, especially if the problem was incorrect DNS entries.

[NeilP]

Ok, thanks had forgotten about Transmission remote since moving over to Mac Will have to look and see if I can get it to run from mac or via a Windows VMware machine

Thanks