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

[BUG] HTTPServer provider reports a failed health check #1925

Closed
1 of 9 tasks
brooksmtownsend opened this issue Apr 17, 2024 · 2 comments
Closed
1 of 9 tasks

[BUG] HTTPServer provider reports a failed health check #1925

brooksmtownsend opened this issue Apr 17, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@brooksmtownsend
Copy link
Member

Affected project(s)

  • documentation
  • examples
  • wasmCloud host
  • wasmCloud CLI (wash)
  • wasmCloud dashboard UI (washboard)
  • capability providers
  • provider bindgen
  • control interface client
  • other / not sure

Describe the bug

The HTTPserver provider reports the following warning log every health check:

2024-04-17T16:17:09.234789Z  WARN wasmcloud_host::wasmbus: failed to request provider health, retrying in 30 seconds

Steps to reproduce

  1. wash up -d
  2. wash start component ghcr.io/wasmcloud/http-server:0.20.0
  3. View logs

Expected behavior

I expect for the health check to work!

Environment

  • OS: [e.g. Linux, MacOS]
  • Shell [e.g. bash, zsh, powershell]
  • wasmcloud Version [e.g. 0.81.0]

Screenshots / Logs / Additional context

No response

@brooksmtownsend brooksmtownsend added the bug Something isn't working label Apr 17, 2024
@yerzham
Copy link
Contributor

yerzham commented Apr 21, 2024

The steps to reproduce should be:

  1. wash up -d
  2. wash start provider ghcr.io/wasmcloud/http-server:0.20.0 http-server-1
  3. View logs or subscribe to wasmbus.evt.default.health_check_passed nats subject

Based on my manual checks on the current main branch, the health check for the HTTP server is passing. I might try to reproduce it some other way.

@brooksmtownsend
Copy link
Member Author

I can't reproduce this in main so I'm going to close this for now as it'll be fixed by the next patch release of wasmCloud, but if this comes back we can re-open this issue. Thanks for checking as well @yerzham !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants