Another new installation problem

Ask for help and report issues not specific to either the Mac OS X or GTK+ versions of Transmission
Post Reply
sabretache
Posts: 21
Joined: Mon Mar 07, 2011 5:07 pm

Another new installation problem

Post by sabretache »

I have been running T on a Centos 5.5 vps for a couple of years now. See these threads for the issues I faced when I started:
search.php?search_id=egosearch
The installation worked out-of-the-box and ran with no issues for over 2 years - (used only for distributing weekly site backups so v low volume)

I recently relinquished the T vps and have been trying to get it going again on my main vps (the subject of most of the above posts). It too is a Centos 5.5 and I did a quick yum install from the geekery repository - version 2.76. Web client works fine. It reports [port 51413 open]. Also, transmission-remote --port-test says it is open and transmission-remote -si says port forwarding, uTP, LPD and DHT are all enabled

I cannot get any torrents to work - either way. I have logging set to level 3. Here is the startup output with 2 x high volume torrents ready to go:

Code: Select all

[20:17:24.956] Transmission 2.76 (13786) started (session.c:722)
[20:17:24.956] Couldn't read "/var/lib/transmission/stats.json": No such file or directory (utils.c:445)
[20:17:24.956] Couldn't read "/var/lib/transmission/stats.benc": No such file or directory (utils.c:445)
[20:17:24.956] Cache Maximum cache size set to 4.00 MiB (256 blocks) (cache.c:262)
[20:17:24.956] RPC Server Adding address to whitelist: 127.0.0.1 (rpc-server.c:803)
[20:17:24.956] RPC Server Serving RPC and Web requests on port 127.0.0.1:9091/transmission/ (rpc-server.c:997)
[20:17:24.956] RPC Server Whitelist enabled (rpc-server.c:1001)
[20:17:24.956] Bound socket 13 to port 51413 on 0.0.0.0 (net.c:377)
[20:17:24.956] Bound socket 14 to port 51413 on :: (net.c:377)
[20:17:24.956] UDP Failed to set receive buffer: requested 4194304, got 262142 (tr-udp.c:77)
[20:17:24.956] UDP Please add the line "net.core.rmem_max = 4194304" to /etc/sysctl.conf (tr-udp.c:82)
[20:17:24.956] UDP Failed to set send buffer: requested 1048576, got 262142 (tr-udp.c:88)
[20:17:24.956] UDP Please add the line "net.core.wmem_max = 1048576" to /etc/sysctl.conf (tr-udp.c:93)
[20:17:24.956] DHT Initializing DHT (tr-dht.c:276)
[20:17:24.956] Couldn't read "/var/lib/transmission/dht.dat": No such file or directory (utils.c:445)
[20:17:24.956] DHT Generating new id (tr-dht.c:309)
[20:17:24.956] DHT DHT initialized (tr-dht.c:330)
[20:17:24.956] LPD Initialising Local Peer Discovery (tr-lpd.c:283)
[20:17:24.956] LPD Local Peer Discovery initialised (tr-lpd.c:354)
[20:17:24.956] Using settings from "/var/lib/transmission" (daemon.c:517)
[20:17:24.956] Saved "/var/lib/transmission/settings.json" (bencode.c:1733)
[20:17:24.956] ubuntu-13.04-desktop-amd64.iso Read resume file "/var/lib/transmission/resume/ubuntu-13.04-desktop-amd64.iso.f41989f9797a8850.resume" (resume.c:692)
[20:17:24.956] ubuntu-13.04-desktop-amd64.iso Resume file found 1 files marked for download (resume.c:205)
[20:17:24.956] ubuntu-13.04-desktop-i386.iso Read resume file "/var/lib/transmission/resume/ubuntu-13.04-desktop-i386.iso.daac7008e2e3a6e4.resume" (resume.c:692)
[20:17:24.956] ubuntu-13.04-desktop-i386.iso Resume file found 1 files marked for download (resume.c:205)
[20:17:24.956] Loaded 2 torrents (session.c:1943)
[20:17:24.956] Port Forwarding (NAT-PMP) initnatpmp failed. Natpmp returned -8 (connect() failed); errno is 22 (Invalid argument) (natpmp.c:77)
[20:17:24.956] Port Forwarding (NAT-PMP) sendpublicaddressrequest failed. Natpmp returned -10 (send() failed); errno is 89 (Destination address required) (natpmp.c:77)
[20:17:32.964] Port Forwarding (UPnP) UPNP_GetValidIGD failed (errno 0 - Success) (upnp.c:214)
[20:17:32.964] Port Forwarding (UPnP) If your router supports UPnP, please make sure UPnP is enabled! (upnp.c:217)
[20:17:32.964] Port Forwarding State changed from "Not forwarded" to "???" (port-forwarding.c:93)
[20:17:58.005] DHT Attempting bootstrap from dht.transmissionbt.com (tr-dht.c:247)
[20:18:32.056] ubuntu-13.04-desktop-amd64.iso Scrape error: Could not connect to tracker (announcer.c:1259)
[20:18:32.056] ubuntu-13.04-desktop-amd64.iso Retrying scrape in 319 seconds. (announcer.c:1268)
[20:18:42.066] ubuntu-13.04-desktop-i386.iso Scrape error: Could not connect to tracker (announcer.c:1259)
[20:18:42.066] ubuntu-13.04-desktop-i386.iso Retrying scrape in 310 seconds. (announcer.c:1268)

[20:19:43.163] ubuntu-13.04-desktop-i386.iso Scrape error: Could not connect to tracker (announcer.c:1259)
[20:19:43.163] ubuntu-13.04-desktop-i386.iso Retrying scrape in 305 seconds. (announcer.c:1268)
[20:20:22.204] ubuntu-13.04-desktop-amd64.iso Scrape error: Could not connect to tracker (announcer.c:1259)
[20:20:22.204] ubuntu-13.04-desktop-amd64.iso Retrying scrape in 352 seconds. (announcer.c:1268)
[20:21:29.275] Searching for web interface file "/var/lib/transmission/.local/share/transmission/web/index.html" (platform.c:537)
[20:21:29.275] Searching for web interface file "/usr/share/transmission/web/index.html" (platform.c:537)
[20:21:37.284] ubuntu-13.04-desktop-amd64.iso LPD announce message away (tr-lpd.c:473)
[20:21:38.285] ubuntu-13.04-desktop-amd64.iso Announcing to tracker (announcer.c:1532)
[20:21:38.285] ubuntu-13.04-desktop-amd64.iso Announcing to tracker (announcer.c:1532)
[20:21:38.285] ubuntu-13.04-desktop-i386.iso Announcing to tracker (announcer.c:1532)
[20:21:38.285] ubuntu-13.04-desktop-i386.iso Announcing to tracker (announcer.c:1532)
[20:21:39.286] ubuntu-13.04-desktop-amd64.iso Could not connect to tracker (announcer.c:994)
[20:21:39.286] ubuntu-13.04-desktop-amd64.iso Retrying announce in 910 seconds. (announcer.c:1003)
[20:21:39.286] ubuntu-13.04-desktop-amd64.iso Could not connect to tracker (announcer.c:994)
[20:21:39.286] ubuntu-13.04-desktop-amd64.iso Retrying announce in 944 seconds. (announcer.c:1003)
[20:21:39.286] ubuntu-13.04-desktop-i386.iso Could not connect to tracker (announcer.c:994)
[20:21:39.286] ubuntu-13.04-desktop-i386.iso Retrying announce in 945 seconds. (announcer.c:1003)
[20:21:39.286] ubuntu-13.04-desktop-i386.iso Could not connect to tracker (announcer.c:994)
[20:21:39.286] ubuntu-13.04-desktop-i386.iso Retrying announce in 931 seconds. (announcer.c:1003)
[20:21:42.289] ubuntu-13.04-desktop-i386.iso LPD announce message away (tr-lpd.c:473)
[20:21:51.300] ubuntu-13.04-desktop-i386.iso IPv4 DHT not ready (broken, 1 nodes) (tr-dht.c:590)
[20:21:53.302] ubuntu-13.04-desktop-amd64.iso IPv4 DHT not ready (broken, 1 nodes) (tr-dht.c:590)
Also, I have increased the sysctl.conf sizes as requested but, even after a server reboot the above messages remain the same.

The fact that it worked with no tweeking on a vps with the same OS suggests to me that it must be a ports/firewall issue and yet the required port seems to be open.

Any help to get this thing going would be much appreciated
sabretache
Posts: 21
Joined: Mon Mar 07, 2011 5:07 pm

Re: Another new installation problem

Post by sabretache »

I have had those two ubuntu torrents loaded for nearly 3 days now and still not a byte in or out.

I tried a traceroute to the trackers. That revealed that the probe packets could not exit (or maybe just the replies get back to) the server. Investigation shows that, by default, traceroute uses udp and a default start port of 33434. So I then tried:
traceroute -I and traceroute -T
Both worked fine.

So, althought my vps firewall reports 32768 - 65535 for both TCP and UDP as open for inbound traffic and ALL ports open for outbound, UDP packets do not get back in (or maybe out either!). My conclusion is that my ISP must be blocking them. This in spite of Nmap reporting 51413 as open|filtered for UDP.

My vps ISP says they have a very restrictive ports policy for their enire network. They will not provide details but say that, if particular non-standard (maybe that should be 'official') ports are required to be open for a vps, they must be specifically requested on a spreadsheet-like form which they provide for the purpose.

My revised question therefore is, what inbound ports MUST, as a minumum be opened to inbound traffic, and for which protocls, for both DHT - and tracker communication to work?
Post Reply