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

Multi App Run - Stop processing and exit when there is error in daprd startup #1257

Open
pravinpushkar opened this issue Mar 9, 2023 · 5 comments
Labels
kind/bug Something isn't working pinned
Milestone

Comments

@pravinpushkar
Copy link
Contributor

Expected Behavior

It should provide details of the error, stop processing further apps and exit the process.

Actual Behavior

When there is error in daprd startup, for example loading of components etc then there is no error logs on the console and it console logs gives indication of all successful steps.

⚠  This is a preview feature and subject to change in future releases.
ℹ️  Validating config and starting app "addapp"
ℹ️  Started Dapr with app id "addapp". HTTP Port: 3503. gRPC Port: 61181
ℹ️  Writing log files to directory : /Users/pravin/work/quickstarts/tutorials/distributed-calculator/go/.dapr/logs
ℹ️  Validating config and starting app "subtractapp"
Listening on port 4000!
ℹ️  Started Dapr with app id "subtractapp". HTTP Port: 3502. gRPC Port: 61215
ℹ️  Writing log files to directory : /Users/pravin/work/quickstarts/tutorials/distributed-calculator/node/.dapr/logs
ℹ️  Validating config and starting app "multiplyapp"

This does take extra time because behind the scene below is happening (actual daprd logs in log file)-

time="2023-03-09T15:11:17.224749+05:30" level=fatal msg="process component pubsub error: [INIT_COMPONENT_FAILURE]: initialization error occurred for pubsub (pubsub.kafka/v1): kafka error: missing 'brokers' attribute" app_id=addapp instance=Pravins-MacBook-Pro.local scope=dapr.runtime type=log ver=1.10.2
The daprd process exited with error code: exit status 1
Could not update sidecar metadata for cliPID: PUT http://127.0.0.1:3503/v1.0/metadata/cliPID giving up after 5 attempt(s): Put "http://127.0.0.1:3503/v1.0/metadata/cliPID": dial tcp 127.0.0.1:3503: connect: connection refused
Could not update sidecar metadata for runFile: PUT http://127.0.0.1:3503/v1.0/metadata/runTemplatePath giving up after 5 attempt(s): Put "http://127.0.0.1:3503/v1.0/metadata/runTemplatePath": dial tcp 127.0.0.1:3503: connect: connection refused
Updating metadata for app command: go run app.go
Could not update sidecar metadata for appCommand: PUT http://127.0.0.1:3503/v1.0/metadata/appCommand giving up after 5 attempt(s): Put "http://127.0.0.1:3503/v1.0/metadata/appCommand": dial tcp 127.0.0.1:3503: connect: connection refused
Updating metadata for appPID: 46924
Could not update sidecar metadata for appPID: PUT http://127.0.0.1:3503/v1.0/metadata/appPID giving up after 5 attempt(s): Put "http://127.0.0.1:3503/v1.0/metadata/appPID": dial tcp 127.0.0.1:3503: connect: connection refused
You're up and running! Dapr logs will appear here.

Steps to Reproduce the Problem

Release Note

RELEASE NOTE: FIX Improve console logs of daprd in error scenarios for Multi App Run

@pravinpushkar pravinpushkar added the kind/bug Something isn't working label Mar 9, 2023
@mukundansundar mukundansundar added this to the v1.11 milestone Mar 14, 2023
@dapr-bot
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

@dapr-bot dapr-bot added the stale label Apr 13, 2023
@dapr-bot
Copy link
Collaborator

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.

@dapr-bot
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

@dapr-bot dapr-bot added the stale label May 21, 2023
@mukundansundar mukundansundar modified the milestones: v1.11, v1.12 May 23, 2023
@dapr-bot
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

@dapr-bot dapr-bot added the stale label Jun 22, 2023
@dapr-bot
Copy link
Collaborator

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.

@mukundansundar mukundansundar modified the milestones: v1.12, v1.13 Sep 22, 2023
@mukundansundar mukundansundar modified the milestones: v1.13, v1.14 Feb 8, 2024
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 pinned
Projects
None yet
Development

No branches or pull requests

3 participants