Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Slow results for every command #3893

Closed
dspstudio opened this issue Oct 7, 2014 · 3 comments
Closed

Slow results for every command #3893

dspstudio opened this issue Oct 7, 2014 · 3 comments

Comments

@dspstudio
Copy link

@dspstudio dspstudio commented Oct 7, 2014

Since today i noticed it takes around 5 minutes to get a result. I tried on other system and it works fine. Using the verbose didn't gave me some useful output.
I tend to think its a network problem but the tracert to youtube is fine. Any ideas how to debug further?

[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['https://www.youtube.com/watch?v=tX6VursfSao', '-g', '--verbose']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2014.10.05.2
[debug] Python version 2.7.2 - Linux-2.6.32-042stab092.2-x86_64-with-redhat-5.11-Final
[debug] Proxy map: {}
https://r7---sn-5hn7snle.googlevideo.com/videoplayback?ip=31.220.42.57&gcr=be&sparams=gcr%2Cid%2Cinitcwndbps%2Cip%2Cipbits%2Citag%2Cmm%2Cms%2Cmv%2Cratebypass%2Crequiressl%2Csource%2Cupn%2Cexpire&itag=18&requiressl=yes&id=o-AGJziARRahA36EUvg54sfIYRHNDvYjItteojzoAxWuZ4&source=youtube&sver=3&key=yt5&upn=Cnp3Nd5tCDw&mm=31&fexp=916941%2C927622%2C927880%2C930666%2C931983%2C932404%2C934030%2C946022%2C947209%2C952302%2C953733%2C953801&mt=1412669220&mv=m&initcwndbps=15083750&ipbits=0&ratebypass=yes&ms=au&signature=270B6CDF53B163926FEDBE3693E9A00A63D29027.EA955687E102A0097E2924C33234B8BB36852750&expire=1412690904

traceroute to youtube.com (173.194.65.190), 30 hops max, 40 byte packets
1 * * *
2 * * *
3 209.85.248.92 (209.85.248.92) 1.923 ms 2.125 ms 2.123 ms
4 209.85.253.247 (209.85.253.247) 2.242 ms 2.228 ms 72.14.238.69 (72.14.238.69) 2.158 ms
5 209.85.255.85 (209.85.255.85) 11.566 ms 209.85.255.75 (209.85.255.75) 10.720 ms 216.239.48.139 (216.239.48.139) 5.699 ms
6 216.239.49.30 (216.239.49.30) 5.353 ms 216.239.49.36 (216.239.49.36) 5.227 ms 5.199 ms
7 ee-in-f190.1e100.net (173.194.65.190) 5.575 ms 8.252 ms 7.733 ms

@phihag
Copy link
Contributor

@phihag phihag commented Oct 7, 2014

Thank you for the report! This may be a connection problem. Can you post the output you get when you run

time curl phihag.de/ip/ ; time curl r.phihag.de/ip/

? You can change the numbers in the actual addresses if you like; this is just to see whether a faulty IPv6 connection may be the problem.

@dspstudio
Copy link
Author

@dspstudio dspstudio commented Oct 7, 2014

[root@myserver tmp]# time curl phihag.de/ip/ ; time curl r.phihag.de/ip/
31.220.42.57
real 0m0.890s
user 0m0.000s
sys 0m0.004s
31.220.42.57

real 1m3.083s
user 0m0.002s
sys 0m0.003s

You are right there is something wrong with IPv6.

@phihag
Copy link
Contributor

@phihag phihag commented Oct 7, 2014

You can contact your provider and give them the more detailed information you get on http://test-ipv6.com/ . Also, --socket-timeout 3 (tune the number in seconds to your liking) may help for youtube-dl. Unfortunately, there is no option yet in youtube-dl to prefer IPv4 or IPv6; we'll use whatever the operating system's resolver prefers.

@phihag phihag closed this Oct 7, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.