Results 1 to 4 of 4

Thread: s3 connection timed out errors

  1. #1

    Question s3 connection timed out errors

    Hi,

    I am in the process of migrating to using wowza with AWS and S3 (both in the same region). Multiple times a day I see the following errors in the log. Does this mean that my wowza server gave up trying to retrieve the video from my s3 bucket? Can I or should I tune any timeout parameters in my application config?

    2015-09-01      19:25:06        UTC     comment server  ERROR   500     -       MediaCacheHTTPByteReader.sendRequest[http://mybucket.s3.amazonaws.com:80/myvideo.mp4] : java.net.SocketException: Connection timed out|at java.net.SocketOutputStream.socketWrite0(Native Method)|at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)|at java.net.SocketOutputStream.write(SocketOutputStream.java:141)|at com.wowza.wms.mediacache.impl.MediaCacheHTTPByteReader.sendRequest(MediaCacheHTTPByteReader.java:807)|at com.wowza.wms.mediacache.impl.MediaCacheHTTPByteReader.sendRequest(MediaCacheHTTPByteReader.java:778)
    Thanks,
    Gavin

  2. #2
    Join Date
    Jun 2011
    Posts
    1,037

    Default

    Hi,
    MediaCache on EC2 is usually a good match up, but the error does indicate a network issue of some sort.
    What instance type are you using? And what is the region?

    You could try increasing the timeout with the httpConnectionTimeout MediaCache source property, detailed on page 22 of the MediaCache user guide.

    Daren

  3. #3

    Default

    Thanks Daren,

    Both the instance and s3 bucket are in EU (Ireland). The instance type is m3.medium and I have not had more than 4 to 5 videos streaming simultaneously so far. Thanks for pointing me to the settings, 6 seconds sounds like a long time already, but maybe increasing to 10 would be worth trying? Is it worth increasing the httpReadRetries too?

    Has anyone else had similar issues which they have resolved or is s3 just prone to these issues?

    Thanks,
    Gavin

  4. #4
    Join Date
    Jun 2011
    Posts
    1,037

    Default

    Hi,
    I would suggest turning on debugHTTPRequests. This property is detailed on the same page, 22, of the MediaCache users guide.. That will allow problematic HTTP sources to be debugged and the cause of the failures can be observed. The information will be written to the WowzaStreamingEngine_access.log, under [install-dir]/logs

    Daren

Similar Threads

  1. Transcoder only wraps up when client is timed out?
    By jHouseman in forum Wowza Transcoder
    Replies: 8
    Last Post: 10-08-2014, 10:03 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •