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

A GET on /sys/pprof/profile causes a read timeout #18851

Closed
ludovicianul opened this issue Jan 26, 2023 · 3 comments
Closed

A GET on /sys/pprof/profile causes a read timeout #18851

ludovicianul opened this issue Jan 26, 2023 · 3 comments
Labels
bug Used to indicate a potential bug core/telemetry performance

Comments

@ludovicianul
Copy link

Describe the bug
Doing a GET on /sys/pprof/profile causes a read timeout.

To Reproduce
Steps to reproduce the behavior:

curl  -X GET \
      -H "Accept: application/json" -H "Content-Type: application/json" -H "X-Vault-Token: $token" \
      http://localhost:8200/v1/sys/pprof/profile

Expected behavior
A meaningful HTTP response.

Environment:

  • Vault Server Version (retrieve with vault status): 1.12.2
  • Vault CLI Version (retrieve with vault version): v1.12.2
  • Server Operating System/Architecture: macOS Ventura 13.0.1
@hsimon-hashicorp hsimon-hashicorp added core/telemetry performance bug Used to indicate a potential bug labels Jan 26, 2023
@ryowright
Copy link
Contributor

I'd like to take a look at this issue if no one is currently working on it.

@ryowright
Copy link
Contributor

I tried out the reproduction of the behavior, and I actually did end up receiving data back after 30 seconds as specified on the documentation. I just had to output the data to a file because cURL read it as binary data and did not want to output it to the terminal. Although, there was no HTTP response message or confirmation.

Could the default time parameter be a reason you might be experiencing a read timeout?

image

@ludovicianul
Copy link
Author

You are correct, @ryowright. Missed that from the documentation. This can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Used to indicate a potential bug core/telemetry performance
Projects
None yet
Development

No branches or pull requests

3 participants