| View previous topic :: View next topic |
| Author |
Message |
tld
Veteran
Joined: 09 Dec 2003
Posts: 1816
|
 Posted: Tue Apr 24, 2007 1:06 pm Post subject: curl timing out in audacious-plugins [SOLVED] |
 |
|
I'm posting this as solved, as it may prevent someone from going nuts figuring it out as I did this morning.
Today I was unable to listent to any internet radio with audacious. I kept getting this:
| Code: | Open http://wnycfm.streamguys.com with curl => 0x81ea380
Got curl error 28: a timeout was reached
failed!
Open http://wnycfm.streamguys.com with curl => 0x8196470
Got curl error 28: a timeout was reached
failed!
failed!
Close 0x8196470
Open http://wnycfm.streamguys.com with curl => 0x81963e0
Got curl error 28: a timeout was reached
failed!
MADPlug-Message: vfs_fread failed @1 http://wnycfm.streamguys.com
Close 0x81963e0
Open http://wnycfm.streamguys.com with curl => 0x8196470
Got curl error 28: a timeout was reached
failed!
Close 0x8196470
Open http://wnycfm.streamguys.com with curl => 0x81963e0
Got curl error 28: a timeout was reached
failed!
Close 0x81963e0
Open http://wnycfm.streamguys.com with curl => 0x8196470
Got curl error 28: a timeout was reached |
Until it timed out, it couldn't even be killed except with -9.
It turns out that it was related to slow DNS. I use the DNS servers at opendns.com, which appear to having some issues. DNS was lagging seriously, but worked in other apps. Apparently the DNS timeout in audacious-plugins must be extremely short. Once I switched to DNS servers that were working ok, everything was fine.
Tom |
|
| Back to top |
|
 |
nenolod
Apprentice
Joined: 03 Mar 2006
Posts: 199
Location: Tulsa, OK
|
| Posted: Tue Apr 24, 2007 1:49 pm Post subject: Re: curl timing out in audacious-plugins [SOLVED] |
|
|
| tld wrote: | I'm posting this as solved, as it may prevent someone from going nuts figuring it out as I did this morning.
Today I was unable to listent to any internet radio with audacious. I kept getting this:
| Code: | Open http://wnycfm.streamguys.com with curl => 0x81ea380
Got curl error 28: a timeout was reached
failed!
Open http://wnycfm.streamguys.com with curl => 0x8196470
Got curl error 28: a timeout was reached
failed!
failed!
Close 0x8196470
Open http://wnycfm.streamguys.com with curl => 0x81963e0
Got curl error 28: a timeout was reached
failed!
MADPlug-Message: vfs_fread failed @1 http://wnycfm.streamguys.com
Close 0x81963e0
Open http://wnycfm.streamguys.com with curl => 0x8196470
Got curl error 28: a timeout was reached
failed!
Close 0x8196470
Open http://wnycfm.streamguys.com with curl => 0x81963e0
Got curl error 28: a timeout was reached
failed!
Close 0x81963e0
Open http://wnycfm.streamguys.com with curl => 0x8196470
Got curl error 28: a timeout was reached |
Until it timed out, it couldn't even be killed except with -9.
It turns out that it was related to slow DNS. I use the DNS servers at opendns.com, which appear to having some issues. DNS was lagging seriously, but worked in other apps. Apparently the DNS timeout in audacious-plugins must be extremely short. Once I switched to DNS servers that were working ok, everything was fine.
Tom |
We're experimenting with adjusting the timeout to 10 seconds.
_________________
Portage --ignore-blocked-dependencies patch |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Multimedia
