Forum

Post a new question

Categories:

Tags:

Failed to recieve buffer

George 2015-06-21 14:21:58 UTC in Nimble Streamer

Okay, so I had everything I wanted working. Streams going, and then pulling to all my other servers. But now I receive this error as soon as I start my origin streams up and the streams do not play:

[2015-06-21 07:19:21 P6632-T3808] [rtmp] E: failed to recv buffer from client: 1260

please advise.

Yury Udovichenko 2015-06-21 23:28:59 UTC

Hi George,

Looks like our support team has already contacted you and the issue is resolved.
Let us know if you have further questions.

Charlie 2017-10-14 23:38:12 UTC

What is the answer to this log issue? I have this a lot in my log, like every 1 minute and I can't find the answer anywhere

[2017-10-14 19:36:18 P7752-T7652] [rtmp_sender4] E: failed to recv buffer from client: 3148

Alex Pokotilo 2017-10-15 14:39:06 UTC

Hi Charlie,
this means that client closed the socket and server failed to receive buffer from it. You can ignore these messages as it's always possible that some client disconnects from your stream for many reasons

Charlie 2017-10-16 00:00:58 UTC

Do you think if it is a bug or performance issue of nimble? Cause in my situation I only have 3 clients who are publishing 120 streams to nimble. The nimble server is used as an origin server so it is not serving to end users. The problem I have is 1 client has few FMLE encoders that drop millions of packets. Not all but a few encoders only. And there is not much to tune up in nimble performance so I am not sure why there is such problem

Alex Pokotilo 2017-10-16 00:42:12 UTC

You logs clearly states that this issue is in rtmp_sender thread. This means some server/viewer reset connection during receiving stream from nimble.
if you'd have stream receiving issue you would see [rtmp] tag in error log.

If you have a client with sending issue we recommend to use SRT as specified here http://wmspanel.com/nimble/srt
This way you client setup Nimble to his local network and publish from FMLE to local Nimble and then this local NImble publish to you CDN via SRT. SRT is UDP-based but with retransmission support. Many clients reported improvements in publishing with SRT. So consider to test it.

Post a reply



This website or its third-party tools use cookies, which are necessary to its functioning and required to achieve the purposes illustrated in the Privacy Policy. If you want to know more or withdraw your consent to all or some of the cookies, please refer to the Privacy Policy.
By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies.