Log error: received DATA after END_STREAM

mdas013 · April 13, 2022, 10:57am

I'm syncing data from S3 storage to a local drive. I use the latest version of Rclone 1.58. I only write errors to the log. The synchronization seems to be fine.

However, the following messages appear in the log:

2022/04/13 05:57:32 protocol error: received DATA after END_STREAM
2022/04/13 05:59:17 protocol error: received DATA after END_STREAM
2022/04/13 06:01:55 protocol error: received DATA after END_STREAM
2022/04/13 06:02:14 protocol error: received DATA after END_STREAM

What does this mean?

Thank you.

ncw · April 13, 2022, 12:34pm

This is an error from Go's HTTP2 transport.

Do you have a proxy between you and the internet?

Its probably harmless, but rclone will retry any errors.

mdas013 · April 13, 2022, 1:55pm

I don't use any proxy server.

Moreover, these errors do not happen regularly. A few days everything was without errors and today in the log these four.

I monitor the occurrence of errors through the size of the error log. When it is 0 bytes - everything is OK. If I keep logging these errors, which mean nothing, automatic monitoring will not work.

ncw · April 13, 2022, 2:29pm

I'm not sure what is causing it.

Here is where the error is from

github.com

golang/net/blob/290c469a71a567d354e4abd335577aba44c4bde4/http2/transport.go#L2537

      
        
            			cc.mu.Unlock()
            
            
			cc.wmu.Lock()
            			cc.fr.WriteWindowUpdate(0, uint32(f.Length))
            			cc.bw.Flush()
            			cc.wmu.Unlock()
            		}
            		return nil
            	}
            	if cs.readClosed {
            		cc.logf("protocol error: received DATA after END_STREAM")
            		rl.endStreamError(cs, StreamError{
            			StreamID: f.StreamID,
            			Code:     ErrCodeProtocol,
            		})
            		return nil
            	}
            	if !cs.firstByte {
            		cc.logf("protocol error: received DATA before a HEADERS frame")
            		rl.endStreamError(cs, StreamError{
            			StreamID: f.StreamID,

If you get it regularly then let me know, otherwise I think it might be some one off thing like AWS switching over their load balancers or something like that.

mdas013 · April 13, 2022, 4:07pm

OK, I'll keep watching. Thanks for now.

system · May 13, 2022, 4:08pm

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.