-
Notifications
You must be signed in to change notification settings - Fork 91
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
The "go-auto" container of example app "rolldice" crashes #265
Comments
If I understand correctly, this happens for you on the latest main branch ? |
@RonFed
|
Here is the error message when running this "rolldice" in my test machine with latest image:
I can successfully run this example app with My test machine:
|
@liurui-1 Can you please try this branch on your setup ? |
hi @RonFed , I tried
Then I revised "docker-compose.yaml" file to replace:
with
Then I saw the
|
Did you ran |
Hi @RonFed , I forgot to run " While I tested with following 2 commands in the
Now the problem is similar. The "rolldice-rolldice" container exits. Following are log messages of
|
@liurui-1 The error in the log you attached means the environment variable OTEL_GO_AUTO_TARGET_EXE is not defined. |
@RonFed
|
@liurui-1 |
@liurui-1 This is again the env var problem. If the yaml file is not changed this should not happen. |
Hi @RonFed ,
Here is the error messages:
Here is the container info:
|
I want to apologize that I forgot that I tested with a changed |
Describe the bug
I am running the example name "rolldice" in this "opentelemetry-go-instrumentation". I can successfully run "docker compose up" . When I ran command "curl localhost:8080/rolldice", I can see the good responses in docker logs:
rolldice-rolldice-1 | 2023-08-23T11:27:41.658Z INFO app/main.go:41 rolldice called {"dice": 5}
rolldice-rolldice-1 | 2023-08-23T11:27:42.389Z INFO app/main.go:41 rolldice called {"dice": 4}
rolldice-rolldice-1 | 2023-08-23T11:27:43.053Z INFO app/main.go:41 rolldice called {"dice": 4}
rolldice-rolldice-1 | 2023-08-23T11:27:43.678Z INFO app/main.go:41 rolldice called {"dice": 4}
But when I visit Jaeger at http://ip:16686/ , I can only see one service named "jaeger-query". It seems the spans from rolldice are not sent to Jaeger.
After checking the configuration, I found the "go-auto" container of this example failed. Here is the error message:
I got some comments from Jamie Danielson to change the "docker-compose.yaml" file. Change the "go-auto" to use image directly.
Here is the new configuration:
When I run run "docker compose up" again, I can see the problem is fixed.
Environment
To Reproduce
Steps to reproduce the behavior:
Simply Run following commands in above environment:
Expected behavior
The "go-auto" container does not crash.
The text was updated successfully, but these errors were encountered: