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

Cannot start agent and collector on the same machine (OpenTelemetry distribution) #2566

Closed
jpkrohling opened this issue Oct 15, 2020 · 3 comments

Comments

@jpkrohling
Copy link
Contributor

jpkrohling commented Oct 15, 2020

When trying to start both the collector and the agent on the same machine, the second component to start hangs without failing:

$ SPAN_STORAGE_TYPE=memory go run ./cmd/collector 

In another terminal:

$ go run ./cmd/agent --reporter.grpc.host-port=localhost:14250
2020-10-15T14:11:40.555+0200	INFO	service/service.go:396	Starting Jaeger OpenTelemetry Agent...	{"Version": "", "GitHash": "", "NumCPU": 12}
2020-10-15T14:11:40.556+0200	INFO	service/service.go:240	Setting up own telemetry...
2020-10-15T14:11:40.569+0200	INFO	service/telemetry.go:110	Serving Prometheus metrics	{"address": "localhost:8888", "legacy_metrics": false, "new_metrics": true, "level": 0, "service.instance.id": "63dde494-2c17-4752-ae8c-ecd42caf7eb1"}
2020-10-15T14:11:40.601+0200	INFO	service/service.go:277	Loading configuration...
2020-10-15T14:11:40.612+0200	INFO	service/service.go:288	Applying configuration...
2020-10-15T14:11:40.612+0200	INFO	service/service.go:309	Starting extensions...
2020-10-15T14:11:40.612+0200	INFO	builder/extensions_builder.go:53	Extension is starting...	{"component_kind": "extension", "component_type": "health_check", "component_name": "health_check"}
2020-10-15T14:11:40.612+0200	INFO	healthcheckextension/healthcheckextension.go:40	Starting health_check extension	{"component_kind": "extension", "component_type": "health_check", "component_name": "health_check", "config": {"TypeVal":"health_check","NameVal":"health_check","Port":13133}}
^Csignal: interrupt

Once #2563 is addressed, this won't be such a big problem, as the port can then be overridden.

@yurishkuro
Copy link
Member

the second component to start hangs without failing

odd, since when port is in use you normally get an error and the binary should exit with it

@jpkrohling
Copy link
Contributor Author

That'd be my expectation too.

@pavolloffay
Copy link
Member

closing, OTEL distribution has been removed

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

No branches or pull requests

3 participants