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

Logs make it sound like everything is fully running when not #348

Closed
LMWF opened this issue May 26, 2020 · 1 comment · Fixed by #448
Closed

Logs make it sound like everything is fully running when not #348

LMWF opened this issue May 26, 2020 · 1 comment · Fixed by #448
Assignees
Labels
kind/bug Something isn't working

Comments

@LMWF
Copy link
Contributor

LMWF commented May 26, 2020

The dapr runtime will wait for the app to listen on the port given in --app-id. If it does not, this will wait forever:

== DAPR == time="2020-05-24T13:13:57.8317813-06:00" level=info msg="application protocol: http. waiting on port 5000.  This will block until the app is listening on that port." 

However this will print afterwards, making it sound like everything is ok:

⚠  Could not update sidecar metadata for cliPID: PUT http://127.0.0.1:3501/v1.0/metadata/cliPID giving up after 5 attempts
✅  You're up and running! Dapr logs will appear here.

These should be clarified.

From #345.

@LMWF LMWF added the kind/bug Something isn't working label May 26, 2020
@mukundansundar mukundansundar mentioned this issue Aug 21, 2020
3 tasks
@mukundansundar mukundansundar self-assigned this Aug 25, 2020
@ZhangX-Byte
Copy link

I still got error in the dapr version 0.9.2 java SDK when i follow the doc.

my command is:
dapr run --components-path ./components --app-id someservice --app-port 3000 --dapr-http-port 3005 -- java -jar target/dapr-java-server-exec.jar com.dapr.someservice -p 3001

dapr version:
image

error:
image

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

Successfully merging a pull request may close this issue.

3 participants