What's new

Transmission Error

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Mogambo

New Around Here
Hi Folks,
Have been using Merlin for sometime now.
And I have to say I love it.
Have a AC56U and on that have been using transmission.
Recently I have started seeing this error in the sys log.
Couldn't bind port 32767 on ::: Address already in use (Is another copy of Transmission already running?) (net.c:371)
The firewall start script is correct, I tried netstat to see if anything else is hogging teh port.
I tried changing it, (Was on the then default 51413 and only changed it after getting errors).

I even did a complete factory reset and re-installed and reconfigured everything to no avail.

Had read somewhere that Ubuntu torrents may cause a problem and I incidentally had a ubuntu and linux mint torrent in there, removed those from the /opt/etc/transmission-daemon/resume.

Well of these tries and still cant get transmission to work.
I know this is not Merlin specific, but want to put in here:

Thank you in Advance!

Details:

Apr 17 23:48:39 transmission-daemon: Starting transmission-daemon...
Apr 17 23:48:40 transmission-daemon[6330]: Transmission 2.82 (14160) started (session.c:738)
Apr 17 23:48:40 transmission-daemon[6330]: RPC Server Adding address to whitelist: *.*.*.* (rpc-server.c:828)
Apr 17 23:48:40 transmission-daemon[6330]: RPC Server Serving RPC and Web requests on port 127.0.0.1:1521/transmission/ (rpc-server.c:1035)
Apr 17 23:48:40 transmission-daemon[6330]: RPC Server Whitelist enabled (rpc-server.c:1039)
Apr 17 23:48:40 transmission-daemon[6330]: RPC Server Password required (rpc-server.c:1042)
Apr 17 23:48:40 transmission-daemon[6330]: Couldn't bind port 32767 on ::: Address already in use (Is another copy of Transmission already running?) (net.c:371)
Apr 17 23:48:40 transmission-daemon[6330]: UDP Failed to set receive buffer: requested 4194304, got 245760 (tr-udp.c:78)
Apr 17 23:48:40 transmission-daemon[6330]: UDP Please add the line "net.core.rmem_max = 4194304" to /etc/sysctl.conf (tr-udp.c:83)
Apr 17 23:48:40 transmission-daemon[6330]: UDP Failed to set send buffer: requested 1048576, got 245760 (tr-udp.c:89)
Apr 17 23:48:40 transmission-daemon[6330]: UDP Please add the line "net.core.wmem_max = 1048576" to /etc/sysctl.conf (tr-udp.c:94)
Apr 17 23:48:40 transmission-daemon[6330]: DHT Reusing old id (tr-dht.c:306)
Apr 17 23:48:40 transmission-daemon[6330]: DHT Bootstrapping from 44 IPv4 nodes (tr-dht.c:154)
Apr 17 23:48:40 transmission-daemon[6330]: Using settings from "/opt/etc/transmission-daemon" (daemon.c:526)
Apr 17 23:48:40 transmission-daemon[6330]: Saved "/tmp/mnt/sdb1/asusware.arm/etc/transmission-daemon/settings.json" (variant.c:1217)
Apr 17 23:48:40 transmission-daemon[6330]: Saved pidfile "/var/run/transmission-daemon.pid" (daemon.c:538)
Apr 17 23:48:40 transmission-daemon[6330]: transmission-daemon requiring authentication (daemon.c:546)
Apr 17 23:48:40 transmission-daemon[6330]: Watching "/mnt/YD128GBSSD/torrents/watchdir" for new .torrent files (daemon.c:564)
Apr 17 23:48:40 transmission-daemon[6330]: Using readdir to watch directory "/mnt/YD128GBSSD/torrents/watchdir" (watch.c:163)
Apr 17 23:48:40 transmission-daemon[6330]: Loaded 4 torrents (session.c:1994)
Apr 17 23:48:40 transmission-daemon[6330]: Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:73)
Apr 17 23:48:40 transmission-daemon[6330]: Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:73)
Apr 17 23:51:19 dnsmasq-dhcp[653]: DHCPREQUEST(br0) 192.168.1.235 18:97:ff:f0:32:20
Apr 17 23:51:19 dnsmasq-dhcp[653]: DHCPACK(br0) 192.168.1.235 18:97:ff:f0:32:20 android-6b9c7eb5d495fd29
admin@RT-AC56U-BFB0:/tmp/mnt/sdb1/asusware.arm/etc/init.d# netstat -a | grep 32767
admin@RT-AC56U-BFB0:/tmp/mnt/sdb1/asusware.arm/etc/init.d# iptables --list-rules | grep 32767
-A INPUT -p udp -m udp --dport 32767 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 32767 -j ACCEPT
admin@RT-AC56U-BFB0:/tmp/mnt/sdb1/asusware.arm/etc/init.d# cat /var/run/transmission-daemon.pid
6330admin@RT-AC56U-BFB0:/tmp/mnt/sdb1/asusware.arm/etc/init.d# ps | grep 6330
6564 admin 1376 S grep 6330
admin@RT-AC56U-BFB0:/tmp/mnt/sdb1/asusware.arm/etc/init.d#
 
Did you check the System Log -> Connections to see what other devices might be using that port?
 
Was not aware of that tab, but just checked, the output of that tab doenst contain 32767.
And I have tried changing the port to have multiple different numbers.
And updated the firewall start script accordingly and I have always been getting this error
 
Odd, you could try updating Transmission to 2.84. Assuming you're using Entware you can update all the installed packages using the following set of commands:

opkg update
opkg upgrade
 
I have setup it up using optware (before entware was supported on arm devices.
Let me try to update it through optware to see if it helps
 
Seems I am on the latest version:

admin@RT-AC56U-BFB0:/# ipkg list_installed | grep -i transmission
transmission - 2.82-1 - Lightweight BitTorrent client and daemon, with web interface bundled.
admin@RT-AC56U-BFB0:/# ipkg update; ipkg upgrade
Downloading http://ipkg.nslu2-linux.org/feeds/optware/mbwe-bluering/cross/stable/Packages.gz
Inflating http://ipkg.nslu2-linux.org/feeds/optware/mbwe-bluering/cross/stable/Packages.gz
Updated list of available packages in /opt/lib/ipkg/lists/optware.mbwe-bluering
Downloading http://nw-dlcdnet.asus.com/asusware/arm/stable/Packages.gz
Inflating http://nw-dlcdnet.asus.com/asusware/arm/stable/Packages.gz
Updated list of available packages in /opt/lib/ipkg/lists/optware.asus
Successfully terminated.
Nothing to be done
Successfully terminated.
admin@RT-AC56U-BFB0:/#

Any more pointers?
 
I suspect that Outware isn't being maintained as 2.84 of Transmission is available under Entware. If you're not tied to Outwore you might want to switch over to Entware and see if that resolves the issues.
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top