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

Need guidance on starting daprd built for component checking (OOM error) #3553

Open
alg opened this issue Sep 23, 2024 · 2 comments
Open

Need guidance on starting daprd built for component checking (OOM error) #3553

alg opened this issue Sep 23, 2024 · 2 comments

Comments

@alg
Copy link

alg commented Sep 23, 2024

I have dapr 1.14.1 installed into the system via nix. I've been working on the feature to support TAG type to the Redis State Query and was going to test how it works in the test app. So I followed the tutorial of building the custom daprd, replacing the version in the ~/.dapr/bin etc. When I start, it immediately exists with the killed error. The exit code is 137 (OOM error).

I compared what old version displays when started:

→ ./daprd.bak help
INFO[0000] Starting Dapr Runtime -- version 1.14.1 -- commit 81cb1f5c4709535b03799e7e1826fbab0315b90b  instance=MacBook-Pro.local scope=dapr.runtime type=log ver=1.14.1
...

And the new one:

→ ./daprd help
zsh: killed     ./daprd helpecho $?
137

File type looks correct:

→ file daprd
daprd: Mach-O 64-bit executable arm64

Clearly something is wrong here. Can anyone suggest where to look next?

I'm on M1 so I took the dist binary from dist/darwin_arm64/debug obviously. There was no any other.

@yaron2
Copy link
Member

yaron2 commented Sep 23, 2024

Did you replace an earlier binary? If so, you must remove/delete the existing binary before copying over the new one

@alg
Copy link
Author

alg commented Sep 24, 2024

You mean step 6 here? https://github.com/alg/components-contrib/blob/main/docs/developing-component.md

Yes, I've done that. After trying dapr run ... and seeing it reporting accidental kill of daprd on start I started looking into problem. Got to the point where I just ran daprd manually (notice "d") as described in the original message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants