Wowza Streaming Engine 4.7.5 MediaCache/amazons3 Read Timeout

Hello,

First, I am new to Wowza and media streaming in general.

I’m using live streaming and playing vod content (S3). Now once a week wowza server stops responding, doesn’t take any requests, not even ping is working. There is no other service working on the server. Please see below the last error logged in wowza before it stopped responding.

Wowza Streaming Engine : version 4.7.5 | @Amazon Linux 1 : 8 Core : 32 GB RAM

ERROR server comment 2020-09-08 12:34:46 - - - - - 496890.084 - - - - - - - - MediaCacheHTTPByteReader.sendRequest[http://s3.amazonaws.com:80/bucket/file.mp4] : java.net.SocketTimeoutException: Read timed out|at java.net.SocketInputStream.socketRead0(Native Method)|at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)|at java.net.SocketInputStream.read(SocketInputStream.java:170)|at java.net.SocketInputStream.read(SocketInputStream.java:141)|at com.wowza.wms.mediacache.impl.MediaCacheHTTPByteReader.sendRequest(MediaCacheHTTPByteReader.java:1109)|
WARN server comment 2020-09-08 12:34:46 - - - - - 496890.091 - - - - - - - - MediaCacheItemHTTPImpl.read[amazons3]: Read failure: req:3407872/262144 url:http://s3.amazonaws.com:80/bucket/file.mp4

WARN server comment 2020-09-08 12:35:28 - - - - - 496932.238 - - - - - - - - MediaCacheItemHTTPImpl.getItemInfo[http://s3.amazonaws.com:80/bucket/file.mp4]: HTTP response: 500

WARN server comment 2020-09-08 12:35:28 - - - - - 496932.238 - - - - - - - - MediaCacheItemBase.init: Item does not exist: amazons3/bucket/file.mp4
WARN server comment 2020-09-08 12:35:28 - - - - - 496932.238 - - - - - - - - MediaCacheItemHTTPImpl.getItemInfo[s3.amazonaws.com:80/bucket/file.mp4]: HTTP response: 404
WARN server comment 2020-09-08 12:35:28 - - - - - 496932.238 - - - - - - - - MediaCacheItemBase.init: Item does not exist: amazons3/bucket/file.mp4
WARN server comment 2020-09-08 12:35:28 - - - - - 496932.244 - - - - - - - - MediaCacheItemHTTPImpl.getItemInfo[s3.amazonaws.com:80/bucket/file.mp4]: HTTP response: 404
WARN server comment 2020-09-08 12:35:28 - - - - - 496932.244 - - - - - - - - MediaCacheItemBase.init: Item does not exist: amazons3/s3.amazonaws.com:80/bucket/file.mp4
WARN server comment 2020-09-08 12:35:28 - - - - - 496932.244 - - - - - - - amazons3/bucket/file.mp4 MediaReaderH264.open[1]: java.io.IOException: MediaCacheRandomAccessReader.open: Item not in cache: amazons3/bucket/file.mp4: java.io.IOException: MediaCacheRandomAccessReader.open: Item not in cache: amazons3/bucket/file.mp4|at com.wowza.wms.mediacache.impl.MediaCacheRandomAccessReader.open(MediaCacheRandomAccessReader.java:75)|at com.wowza.wms.mediacache.impl.MediaCacheRandomAccessReaderFilter.open(MediaCacheRandomAccessReaderFilter.java:75)|at com.wowza.wms.mediareader.h264.MediaReaderH264.open(MediaReaderH264.java:267)|at com.wowza.wms.stream.publish.PublishingProviderMediaReader.a(PublishingProviderMediaReader.java:239)|at com.wowza.wms.stream.publish.PublishingProviderMediaReader.(PublishingProviderMediaReader.java:97)|
ERROR server comment 2020-09-08 12:35:33 - - - - - 496937.059 - - - - - - - - MediaCacheHTTPByteReader.sendRequest[http://s3.amazonaws.com:80/bucket/file.mp4] : java.net.SocketTimeoutException: Read timed out|at java.net.SocketInputStream.socketRead0(Native Method)|at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)|at java.net.SocketInputStream.read(SocketInputStream.java:170)|at java.net.SocketInputStream.read(SocketInputStream.java:141)|at com.wowza.wms.mediacache.impl.MediaCacheHTTPByteReader.sendRequest(MediaCacheHTTPByteReader.java:1109)|
WARN server comment 2020-09-08 12:35:57 - - - - - 496961.004 - - - - - - - amazons3/bucket/file.mp4 MediaReaderH264.open: Error parsing file format [MP4]
ERROR server comment 2020-09-08 12:36:03 - - - - - 496967.115 - - - - - -

I have tried to play content which is not in media cache and S3, but still unable to reproduce the issue.

Welcome to the forums @Chandan_Upendra1!
Yes, those types of messages suggest that the connection from your Wowza instance to the S3 bucket failed. As far as why, that will require a review of your logs and configuration. It can range from a hardware issue to network lag to an error in your playback url.

I see you submitted a support ticket and will follow the conversation once it’s assigned to an engineer. They will be able to run some tests and determine where the issue is. Sorry, you’re having an issue.