Modify

Opened 7 years ago

Closed 7 years ago

Last modified 4 years ago

#8166 closed defect (fixed)

transmission-daemon and uClibc-0.9.31 socket problems

Reported by: Joe Roback (dirtyfreebooter) <openwrt-devel@…> Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: base system Version: Trunk
Keywords: uClibc, transmission, socket, connect Cc:

Description

Installed latest trunk, r23811, after starting transmission-daemon, logs flooded with this

Nov  2 23:49:09 router user.notice "??^Q6Z?ܸ?
Nov  2 23:49:09 router user.notice ??w?!?^m?^U^LDbb
Nov  2 23:49:09 router user.notice Ż?T›??3??ȎO???h^N^\?Z?T\???큞NT??^D%????WN?+ٳ ?9;??^Eg??P4)!?}^O־??u?^[?C^^^U????c?D?(?.ܫ?}Sx??*LWwr3?^H?????J?ݢ
Nov  2 23:49:10 router user.err transmission-daemon[2276]: Couldn't connect socket 13 to 98.237.251.211, port 59360 (errno 0 - Success) (net.c:342)
Nov  2 23:49:10 router user.err transmission-daemon[2276]: Couldn't connect socket 13 to 95.103.25.64, port 45928 (errno 0 - Success) (net.c:342)
Nov  2 23:49:10 router user.err transmission-daemon[2276]: Couldn't connect socket 13 to 193.126.201.126, port 34714 (errno 0 - Success) (net.c:342)
Nov  2 23:49:10 router user.err transmission-daemon[2276]: Couldn't connect socket 13 to 124.149.114.200, port 7448 (errno 0 - Success) (net.c:342)
Nov  2 23:49:10 router user.err transmission-daemon[2276]: Couldn't connect socket 13 to 87.59.103.214, port 10599 (errno 0 - Success) (net.c:342)
Nov  2 23:49:10 router user.err transmission-daemon[2276]: Couldn't connect socket 13 to 166.205.11.254, port 5850 (errno 0 - Success) (net.c:342)
Nov  2 23:49:10 router user.err transmission-daemon[2276]: Couldn't connect socket 13 to 174.25.131.224, port 50559 (errno 0 - Success) (net.c:342)
Nov  2 23:49:10 router user.err transmission-daemon[2276]: Couldn't connect socket 13 to 212.85.88.191, port 49249 (errno 0 - Success) (net.c:342)
Nov  2 23:49:10 router user.err transmission-daemon[2276]: Couldn't connect socket 13 to 84.217.140.46, port 19954 (errno 0 - Success) (net.c:342)
Nov  2 23:49:10 router user.err transmission-daemon[2276]: Couldn't connect socket 13 to 68.198.117.94, port 55156 (errno 0 - Success) (net.c:342)
Nov  2 23:49:10 router user.err transmission-daemon[2276]: Couldn't connect socket 13 to 2001:0:5ef5:79fd:10c1:68a:ab07:6efd, port 50001 (errno 0 - Success) (net.c:342)
Nov  2 23:49:11 router user.err transmission-daemon[2276]: Couldn't connect socket 0 to 78.70.130.163, port 48161 (errno 0 - Success) (net.c:342)
Nov  2 23:49:11 router user.err transmission-daemon[2276]: Couldn't connect socket 0 to 80.186.1.10, port 46259 (errno 0 - Success) (net.c:342)
Nov  2 23:49:11 router user.err transmission-daemon[2276]: Couldn't connect socket 0 to 64.87.57.119, port 57873 (errno 0 - Success) (net.c:342)
Nov  2 23:49:11 router user.err transmission-daemon[2276]: Couldn't connect socket 0 to 188.165.122.61, port 52160 (errno 0 - Success) (net.c:342)
Nov  2 23:49:11 router user.err transmission-daemon[2276]: Couldn't connect socket 0 to 79.166.80.47, port 32458 (errno 0 - Success) (net.c:342)
Nov  2 23:49:11 router user.err transmission-daemon[2276]: Couldn't connect socket 0 to 2002:534:fdc9::534:fdc9, port 56701 (errno 0 - Success) (net.c:342)
Nov  2 23:49:11 router user.err transmission-daemon[2276]: Couldn't connect socket 0 to 134.153.83.180, port 46535 (errno 0 - Success) (net.c:342)
Nov  2 23:49:11 router user.err transmission-daemon[2276]: Couldn't connect socket 0 to 203.214.159.56, port 57374 (errno 0 - Success) (net.c:342)
Nov  2 23:49:11 router user.err transmission-daemon[2276]: Couldn't connect socket 0 to 89.166.223.215, port 56694 (errno 0 - Success) (net.c:342)
Nov  2 23:49:11 router user.err transmission-daemon[2276]: Couldn't connect socket 0 to 85.165.151.46, port 39911 (errno 0 - Success) (net.c:342)
Nov  2 23:49:11 router user.err transmission-daemon[2276]: Couldn't connect socket 0 to 178.40.233.65, port 45927 (errno 0 - Success) (net.c:342)
Nov  2 23:49:12 router user.err transmission-daemon[2276]: Couldn't connect socket 0 to 86.164.106.89, port 65449 (errno 0 - Success) (net.c:342)
Nov  2 23:49:12 router user.err transmission-daemon[2276]: Couldn't connect socket 0 to 24.5.29.157, port 36997 (errno 0 - Success) (net.c:342)
Nov  2 23:49:12 router user.err transmission-daemon[2276]: Couldn't connect socket 0 to 96.246.39.156, port 10000 (errno 0 - Success) (net.c:342)
Nov  2 23:49:12 router user.err transmission-daemon[2276]: Couldn't connect socket 0 to 110.175.55.68, port 27272 (errno 0 - Success) (net.c:342)
Nov  2 23:49:12 router user.err transmission-daemon[2276]: Couldn't connect socket 0 to 80.186.20.198, port 46259 (errno 0 - Success) (net.c:342)
Nov  2 23:49:12 router user.err transmission-daemon[2276]: Couldn't connect socket 0 to 166.194.51.165, port 51413 (errno 0 - Success) (net.c:342)
Nov  2 23:49:12 router user.err transmission-daemon[2276]: Couldn't connect socket 0 to 77.110.3.206, port 51426 (errno 0 - Success) (net.c:342)
Nov  2 23:49:12 router user.err transmission-daemon[2276]: Couldn't connect socket 0 to 84.48.216.199, port 59012 (errno 0 - Success) (net.c:342)
Nov  2 23:49:12 router user.err transmission-daemon[2276]: Couldn't connect socket 0 to 90.201.192.21, port 32462 (errno 0 - Success) (net.c:342)
Nov  2 23:49:12 router user.err transmission-daemon[2276]: Couldn't connect socket 0 to 94.221.230.96, port 11112 (errno 0 - Success) (net.c:342)
Nov  2 23:49:12 router user.err transmission-daemon[2276]: Couldn't connect socket 0 to 213.93.63.14, port 51413 (errno 0 - Success) (net.c:342)
Nov  2 23:49:13 router user.err transmission-daemon[2276]: Couldn't connect socket 0 to 203.219.44.160, port 63363 (errno 0 - Success) (net.c:342)
Nov  2 23:49:13 router user.err transmission-daemon[2276]: Couldn't connect socket 0 to 203.59.93.148, port 39266 (errno 0 - Success) (net.c:342)
Nov  2 23:49:13 router user.err transmission-daemon[2276]: Couldn't connect socket 0 to 84.202.73.67, port 24804 (errno 0 - Success) (net.c:342)
Nov  2 23:49:13 router user.err transmission-daemon[2276]: Couldn't connect socket 0 to 138.67.180.133, port 51413 (errno 0 - Success) (net.c:342)
Nov  2 23:49:13 router user.err transmission-daemon[2276]: Couldn't connect socket 0 to 188.82.169.166, port 13000 (errno 0 - Success) (net.c:342)
Nov  2 23:49:13 router user.err transmission-daemon[2276]: Couldn't connect socket 0 to 69.171.173.136, port 60450 (errno 0 - Success) (net.c:342)

Errno reports success, but still results in failure. Switching back to uClibc 0.9.30.1 and issues went away.

The offending if statement in transmission is at https://trac.transmissionbt.com/browser/tags/2.11/libtransmission/net.c on line 342 ... does this seem like a libc bug or transmission bug?

Attachments (0)

Change History (33)

comment:1 Changed 7 years ago by acoul

can you try to compile from a clean/vanilla svn checkout? you may also use "make distclean".

comment:2 Changed 7 years ago by Joe Roback (dirtyfreebooter) <openwrt-devel@…>

When I saw the libc changes, I immediately distclean'd. I've doubled checked, distclean'd and updated to r23827 this morning and still the same thing.

Nov  3 10:30:12 router user.err transmission-daemon[2276]: Couldn't connect socket 16 to 78.86.128.96, port 22223 (errno 0 - Success) (net.c:342)
Nov  3 10:30:12 router user.err transmission-daemon[2276]: Couldn't connect socket 16 to 72.199.142.164, port 17620 (errno 0 - Success) (net.c:342)
Nov  3 10:30:12 router user.err transmission-daemon[2276]: Couldn't connect socket 16 to 86.3.12.30, port 51965 (errno 0 - Success) (net.c:342)
Nov  3 10:30:12 router user.err transmission-daemon[2276]: Couldn't connect socket 16 to 87.194.231.138, port 59595 (errno 0 - Success) (net.c:342)
Nov  3 10:30:12 router user.err transmission-daemon[2276]: Couldn't connect socket 16 to 213.219.142.215, port 51413 (errno 0 - Success) (net.c:342)
Nov  3 10:30:12 router user.err transmission-daemon[2276]: Couldn't connect socket 16 to 79.166.105.53, port 32458 (errno 0 - Success) (net.c:342)
Nov  3 10:30:13 router user.err transmission-daemon[2276]: Couldn't connect socket 17 to 94.23.208.147, port 51413 (errno 0 - Success) (net.c:342)
Nov  3 10:30:13 router user.err transmission-daemon[2276]: Couldn't connect socket 17 to 70.74.242.171, port 51413 (errno 0 - Success) (net.c:342)
Nov  3 10:30:13 router user.err transmission-daemon[2276]: Couldn't connect socket 17 to 94.221.240.112, port 11112 (errno 0 - Success) (net.c:342)
...

comment:3 Changed 7 years ago by acoul

what gcc are you using, you can try with gcc-4.5.1 perhaps. BTW, the logs you provide are not too informative, you can try to enable some debug options. a tcpdump may also be helpful.

comment:4 Changed 7 years ago by mb

What target architecture is this?

comment:5 Changed 7 years ago by Joe Roback (dirtyfreebooter) <openwrt-devel@…>

architecture is ar71xx... I'll do some more investigating soon, tcpdump and try gcc-4.5.1, but unfortunately I won't be able to get to it until probably tomorrow.

comment:6 Changed 7 years ago by mb

It's probably worth to check what the return value from connect() is.

comment:7 follow-up: Changed 7 years ago by saxin <saxin1@…>

I got the same, "Couldn't connect to socket, latest trunk with minimal package set.
acrchitecture is ar71xx. If more output is needed will supply.

comment:8 in reply to: ↑ 7 ; follow-up: Changed 7 years ago by acoul

Replying to saxin <saxin1@…>:

I got the same, "Couldn't connect to socket, latest trunk with minimal package set.
acrchitecture is ar71xx. If more output is needed will supply.

please do

comment:9 Changed 7 years ago by Joe Roback (dirtyfreebooter) <openwrt-devel@…>

All I had time for last night was trying gcc-4.5.1, but got the same results. This weekend I'll compile a debug version transmission-daemon and see what connect() is actually returning... and hopefully determine whether its uClibc fault or transmission ;-)

comment:10 in reply to: ↑ 8 Changed 7 years ago by saxin <saxin1@…>

Replying to acoul:

Replying to saxin <saxin1@…>:

I got the same, "Couldn't connect to socket, latest trunk with minimal package set.
acrchitecture is ar71xx. If more output is needed will supply.

please do

Please give steps to obtain, I'm not so proficient with linux !

comment:11 Changed 7 years ago by admin@…

same problem on my x86 router with two last snapshots!!!

Nov  6 21:05:12 CS-Internet-App user.err transmission-daemon[1843]: Couldn't create socket: Success (fdlimit.c:659)
Nov  6 21:05:15 CS-Internet-App user.err transmission-daemon[1843]: Couldn't connect socket 17 to 78.56.230.171, port 65486 (errno 0 - Success) (net.c:342)
Nov  6 21:05:16 CS-Internet-App user.err transmission-daemon[1843]: Couldn't connect socket 0 to 78.56.230.171, port 65486 (errno 0 - Success) (net.c:342)
Nov  6 21:05:16 CS-Internet-App user.err transmission-daemon[1843]: Couldn't connect socket 0 to 81.5.127.7, port 15632 (errno 0 - Success) (net.c:342)
Nov  6 21:05:17 CS-Internet-App user.err transmission-daemon[1843]: Couldn't connect socket 0 to 81.5.127.7, port 15632 (errno 0 - Success) (net.c:342)
Nov  6 21:05:20 CS-Internet-App user.err transmission-daemon[1843]: Couldn't connect socket 17 to 92.101.223.33, port 23816 (errno 0 - Success) (net.c:342)
Nov  6 21:05:21 CS-Internet-App user.err transmission-daemon[1843]: Couldn't connect socket 0 to 92.101.223.33, port 23816 (errno 0 - Success) (net.c:342)
Nov  6 21:05:25 CS-Internet-App user.err transmission-daemon[1843]: Couldn't connect socket 17 to 79.165.174.172, port 3286 (errno 0 - Success) (net.c:342)
Nov  6 21:05:26 CS-Internet-App user.err transmission-daemon[1843]: Couldn't connect socket 0 to 79.165.174.172, port 3286 (errno 0 - Success) (net.c:342)
Nov  6 21:05:26 CS-Internet-App user.err transmission-daemon[1843]: Couldn't connect socket 0 to 46.73.205.251, port 1240 (errno 0 - Success) (net.c:342)
Nov  6 21:05:27 CS-Internet-App user.err transmission-daemon[1843]: Couldn't connect socket 0 to 46.73.205.251, port 1240 (errno 0 - Success) (net.c:342)
Nov  6 21:05:30 CS-Internet-App user.err transmission-daemon[1843]: Couldn't connect socket 17 to 91.143.42.1, port 30967 (errno 0 - Success) (net.c:342)
Nov  6 21:05:31 CS-Internet-App user.err transmission-daemon[1843]: Couldn't connect socket 0 to 91.143.42.1, port 30967 (errno 0 - Success) (net.c:342)
Nov  6 21:05:31 CS-Internet-App user.err transmission-daemon[1843]: Couldn't connect socket 0 to 85.30.250.24, port 40973 (errno 0 - Success) (net.c:342)
Nov  6 21:05:32 CS-Internet-App user.err transmission-daemon[1843]: Couldn't connect socket 0 to 178.95.8.62, port 29194 (errno 0 - Success) (net.c:342)
Nov  6 21:05:34 CS-Internet-App user.err transmission-daemon[1843]: Couldn't connect socket 17 to 89.21.86.216, port 31302 (errno 0 - Success) (net.c:342)
Nov  6 21:05:35 CS-Internet-App user.err transmission-daemon[1843]: Couldn't connect socket 0 to 89.21.86.216, port 31302 (errno 0 - Success) (net.c:342)
Nov  6 21:05:45 CS-Internet-App user.err transmission-daemon[1843]: Couldn't connect socket 18 to 95.145.73.24, port 45688 (errno 0 - Success) (net.c:342)
Nov  6 21:05:46 CS-Internet-App user.err transmission-daemon[1843]: Couldn't connect socket 19 to 93.72.204.90, port 25060 (errno 0 - Success) (net.c:342)
Nov  6 21:05:47 CS-Internet-App user.err transmission-daemon[1843]: Couldn't connect socket 0 to 95.145.73.24, port 45688 (errno 0 - Success) (net.c:342)
Nov  6 21:05:51 CS-Internet-App user.err transmission-daemon[1843]: Couldn't connect socket 18 to 195.64.202.67, port 6654 (errno 0 - Success) (net.c:342)
Nov  6 21:05:52 CS-Internet-App user.err transmission-daemon[1843]: Couldn't connect socket 0 to 195.64.202.67, port 6654 (errno 0 - Success) (net.c:342)
Nov  6 21:05:56 CS-Internet-App user.err transmission-daemon[1843]: Couldn't connect socket 20 to 109.205.248.180, port 24084 (errno 0 - Success) (net.c:342)
Nov  6 21:05:57 CS-Internet-App user.err transmission-daemon[1843]: Couldn't connect socket 0 to 109.205.248.180, port 24084 (errno 0 - Success) (net.c:342)
Nov  6 21:06:05 CS-Internet-App user.err transmission-daemon[1843]: Couldn't connect socket 19 to 109.251.34.182, port 62226 (errno 0 - Success) (net.c:342)
Nov  6 21:06:06 CS-Internet-App user.err transmission-daemon[1843]: Couldn't connect socket 0 to 109.251.34.182, port 62226 (errno 0 - Success) (net.c:342)
Nov  6 21:06:07 CS-Internet-App user.err transmission-daemon[1843]: Couldn't connect socket 0 to 95.68.107.190, port 6352 (errno 0 - Success) (net.c:342)
Nov  6 21:06:08 CS-Internet-App user.err transmission-daemon[1843]: Couldn't connect socket 0 to 95.68.107.190, port 6352 (errno 0 - Success) (net.c:342)

comment:12 Changed 7 years ago by admin@…

root@CS-Internet-App:~# opkg update
Downloading http://downloads.openwrt.org/snapshots/trunk/x86/packages/Packages.gz.
Inflating http://downloads.openwrt.org/snapshots/trunk/x86/packages/Packages.gz.
Updated list of available packages in /opt/opkg-lists/snapshots.
root@CS-Internet-App:~# opkg install libc
Package libc (0.9.31-60) installed in root is up to date.
root@CS-Internet-App:~# opkg install libc --force-reinstall
Removing package libc from root...
Installing libc (0.9.31-60) to root...
Downloading http://downloads.openwrt.org/snapshots/trunk/x86/packages/libc_0.9.31-60_x86.ipk.
Collected errors:
 * opkg_download: Failed to download http://downloads.openwrt.org/snapshots/trunk/x86/packages/libc_0.9.31-60_x86.ipk, wget returned 255.
 * opkg_install_pkg: Failed to download libc. Perhaps you need to run 'opkg update'?
 * opkg_install_cmd: Cannot install package libc.
root@CS-Internet-App:~# opkg update
-ash: opkg: not found

after this I see kernel panic messafe after reboot by Reset.

comment:13 Changed 7 years ago by jow

Do *not* upgrade libc with opkg, it will remove the dynamic loader which renders the complete system unusable! If you can, get into failsafe and reset your overlay or reflash the firmware.

comment:14 Changed 7 years ago by jow

  • Resolution set to fixed
  • Status changed from new to closed

I believe this particular issue has been solved with r23905.

comment:15 Changed 7 years ago by admin@…

previusly all work. I make opkg upgrade and opkg upgrade ALL installed components.

now I cannot made opkg upgrade, not start x86 router if COM port disabled.

comment:16 Changed 7 years ago by anonymous

  • Resolution fixed deleted
  • Status changed from closed to reopened

now I use 09 nov build 23918

transmission start and work, but .....

all previously downloaded files when add torrent and Verify Data NOT verifying on 100%. always 95%,96%!!!

comment:17 Changed 7 years ago by admin@…

x86 router

comment:18 follow-up: Changed 7 years ago by Joe Roback (dirtyfreebooter) <openwrt-devel@…>

Yea, I am seeing downloaded pieces constantly failing checksum. It is certainly not usable at this point.

comment:19 Changed 7 years ago by jow

  • Resolution set to invalid
  • Status changed from reopened to closed

I fail to see how this is a "transmission-daemon and uClibc-0.9.31 socket problem". Create a separate ticket please.

comment:20 in reply to: ↑ 18 Changed 7 years ago by saxin <saxin1@…>

Replying to Joe Roback (dirtyfreebooter) <openwrt-devel@…>:

Yea, I am seeing downloaded pieces constantly failing checksum. It is certainly not usable at this point.

Same for me I even dist cleaned, same checksum fail for all parts downloaded.
Maybe worth opening a ticket on transmission TRAC ? What architecture you'r on ?

comment:21 Changed 7 years ago by Joe Roback (dirtyfreebooter) <openwrt-devel@…>

yea, its certainly not a socket problem, but the fix/hack that resolved the socket problem with uClibc 0.9.31 propagated this problem. I'll file a new ticket later. I first want to at least get some background first, that way my ticket can be something better than, *it doesn't work* ;-)

comment:22 Changed 7 years ago by admin@…

  • Resolution invalid deleted
  • Status changed from closed to reopened

I don't understand WHY to create new ticket, if problem appear after problem in uClibc-0.9.31?

before error in uClibc-0.9.31 all work!!! now even after partialy repair problem still exist:

already donwloaded file:
http://i12.fastpic.ru/big/2010/1119/3c/13b8ddb5475410ea3b188040bd47153c.jpg
remove task and added again - verifying:
http://i12.fastpic.ru/big/2010/1119/ef/5bc4f4967c84cec07a40178f950007ef.jpg
stop verifying at 99.2% (for more large files stopping at 97%,96%):
http://i12.fastpic.ru/big/2010/1119/87/66b9f3ba3b6668b20633d9fd7e9f7987.jpg
and downloading again (but what????):
http://i12.fastpic.ru/big/2010/1119/39/877440bcbd7913e7f65017a6312aae39.jpg

why problem in transmission if previously transmission work!!
ctorrent already have problems with verifying!

x86 router last 18 nov build.

comment:23 Changed 7 years ago by acoul

#8281 is dupe of this.

comment:24 Changed 7 years ago by acoul

  • Resolution set to fixed
  • Status changed from reopened to closed

this should be fixed in latest trunk r24248. please always issue "make distclean" when testing stuff in trunk.

comment:25 Changed 7 years ago by admin@…

  • Resolution fixed deleted
  • Status changed from closed to reopened

no? problem stay! even in 24651 it present!

comment:26 Changed 7 years ago by dirtyfreebooter <openwrt-devel@…>

I'm running r24664 and it doesn't happen to me anymore. Try distclean, you're probably using a stale libc.

comment:27 Changed 7 years ago by admin@…

I write new image for my x86 router from 13 Dec trunk for x86 (problem stay)
today upgrade to 24651 trunk, where new lib present libc, libgcc, libpthread - problem stay!

comment:28 Changed 7 years ago by admin@…

in trunk 24843 problem gone (but partically)! now transmission correctly verify allready downloaded files!!!

the torrents that downloaded previously to this problem apear verifying only 99.x%, but if verify again - than verifying normaly.

and it is wonder!!!! gone my problem: /ticket/7689.html

transmission now download and verify files more than 2gb!!!!!

comment:29 Changed 7 years ago by anonymous

problem still exist!!!

now problem like this:

  1. copy file to folder on router
  2. check md5 checksumm (first_checksum)
  3. create new torrent by transmission-create from folder
  4. check md5 checksumm (second_checksum)
  5. post torrent file to tracker and save torrent from tracker
  6. load in transmission web torrent from tracker
  7. transmision Verifying Data (checking hash)
  8. 100% verifying - ready for seeding
  9. check md5 checksumm (third_checksum)

first_checksum and second_checksum are same.

third_checksum is DIFFERENT!!!

same problem with other torrent.
if check md5 checksums downloaded files of any torrent, they differ from checksums that print on torent trackers.

comment:30 Changed 7 years ago by nbd

Please try the latest version, rebuild from scratch

comment:31 Changed 7 years ago by Joe Roback <openwrt-devel@…>

Yes, sorry, I forgot about this one.. I need to find a good way to keep track of tickets I open. The latest trunk builds work great. Thanks nbd!

comment:32 Changed 7 years ago by acoul

  • Resolution set to fixed
  • Status changed from reopened to closed

comment:33 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.