Hi Eduardo,
Thanks for that. After checking my /etc.init.d/liquidsoap to see what user
I have LS running as, I created a .curlrc in that user's home folder and
added:
--max-time 120
--trace /home/myuser/curl_trace.txt
The second parameter was just to make sure the curl binary was reading the
.curlrc. I then did the request push and again after seconds, but the
result was the same and the log output was exactly the same, still showing
the 18 or 19 second timeout. In the log I again saw:
2017/11/21 18:14:39 [protocol.process:3] Failed to execute curl -sL "
http://domain.com/bigfile.mp3"; -o "/tmp/liq-process5a0666.mp3":
("timeout","18.9830081463")
The thing that gets me is, I set up a: watch 'ls -l /tmp' and even after LS
timed out the request after 20 seconds, curl continued to download the rest
of the file to temp for another 40 seconds until it was complete! (It's
only a 75mb file) And now there was a 315 mb trace file in my $HOME
folder. So I ended up with a successful curl download and a complete trace
file - it's just that LS is still deciding to timeout the request after 20
seconds.
s
On Tue, Nov 21, 2017 at 4:58 PM, Eduardo Martinez <[email protected]>
wrote:
> Hi Stephan,
>
> Liquidsoap uses the system defaults for curl
> , so you can increase in max-time in local .curlrc file. Other settings
> like the user agent can also be adjusted here.
>
> On Tue, Nov 21, 2017, 5:49 AM Stephan Hoppe <[email protected]>
> wrote:
>
>> Hi again,
>>
>> FYI log output is as follows:
>>
>> 2017/11/21 14:36:45 [procol.external:4] Running curl -sLI -X HEAD "
>> http://domain.com/BigFile.mp3"; | grep -i '^content-type' | tail -n 1 |
>> cut -d':' -f 2 | cut -d';' -f 1
>> 2017/11/21 14:36:45 [lang.run_process:4] Starting process
>> 2017/11/21 14:36:45 [lang.run_process:4] Closing process's stdin
>> 2017/11/21 14:36:45 [lang.run_process:4] Process exited
>> 2017/11/21 14:36:45 [lang.run_process:4] Cleaning up process
>> 2017/11/21 14:36:45 [protocol.process:4] Processing mp3,curl -sL
>> "http$(colon)//domain.com/BigFile.mp3" -o $(output)
>> 2017/11/21 14:36:45 [protocol.process:4] Executing curl -sL "
>> http://domain.com/BigFile.mp3"; -o "/tmp/liq-process0d51cb.mp3"
>> 2017/11/21 14:36:45 [lang.run_process:4] Starting process
>> 2017/11/21 14:36:45 [lang.run_process:4] Closing process's stdin
>> 2017/11/21 14:37:05 [protocol.process:3] Failed to execute curl -sL "
>> http://domain.com/BigFile.mp3"; -o "/tmp/liq-process0d51cb.mp3":
>> ("timeout","19.0799219608")
>> 2017/11/21 14:37:05 [request:4] Failed to resolve "process:mp3,curl -sL
>> \"http$(colon)//domain.com/BigFile.mp3\
>> <http://domain.com/BigFile.mp3%5C>" -o $(output)"! For more info, see
>> server command 'trace 14'.
>> 2017/11/21 14:37:05 [lang.run_process:4] Cleaning up process
>>
>> The timeout value of "19.0799219608" is always in the neighbourhood of
>> 18, or 19 seconds.
>>
>> On Thu, Nov 16, 2017 at 5:06 PM, Stephan Hoppe <[email protected]>
>> wrote:
>>
>>> Hi,
>>>
>>> Just as the subject says, On 1.3.3, I'm using the request.push feature
>>> of the telnet server to grab remote .mp3s and queue them up for play,
>>> however I notice that the curl function times out after 20 seconds of
>>> downloading to /tmp before the download is complete.
>>>
>>> Is there a way to extend the timeout so that these downloads can
>>> complete or make LS sense that the download hasn't finished yet?
>>>
>>> thx.
>>> s
>>>
>>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot______
>> _________________________________________
>> Savonet-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/savonet-users
>>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Savonet-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/savonet-users
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users
