protocol error: received DATA after END_STREAM · Issue #13942 · prometheus/prometheus · GitHub
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

protocol error: received DATA after END_STREAM #13942

Open
lrainsun opened this issue Apr 17, 2024 · 2 comments
Open

protocol error: received DATA after END_STREAM #13942

lrainsun opened this issue Apr 17, 2024 · 2 comments

Comments

@lrainsun
Copy link

lrainsun commented Apr 17, 2024 •
edited

What did you do?

upgrade prometheus version to v2.51.1

What did you expect to see?

No error log

What did you see instead? Under which circumstances?

We keep receiving error like below in our production environment after we upgrade prometheus version to v2.51.1
2024/04/17 02:48:39 protocol error: received DATA after END_STREAM

We didn't see same error before upgrade in same environment (prometheus version v2.50.0)

System information

Linux 4.18.0-513.11.1.el8_9.x86_64 x86_64

Prometheus version

prometheus, version 2.51.1 (branch: HEAD, revision: 855b5ac4b80956874eb1790a04c92327f2f99e38)
  build user:       root@d3785d7783f2
  build date:       20240328-09:27:30
  go version:       go1.22.1
  platform:         linux/amd64
  tags:             netgo,builtinassets,stringlabels

Prometheus configuration file

No response

Alertmanager version

No response

Alertmanager configuration file

No response

Logs

No response
@bwplotka
Copy link
Member

Thanks for reporting.

This error is visible where? In Prometheus logs?

Is it related to scraping? Remote Write? Remote Read?

Do you see any other problems other than a error log line?

@lrainsun
Copy link
Author

@bwplotka Thanks for reply.
It's in prometheus log, we enabled remote write but not sure if it related.
No other error logs found besides.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bwplotka @lrainsun