Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Hotrod api/traces displaying connecting refused #4355

Closed
prasad-shirodkar opened this issue Mar 30, 2023 · 0 comments
Closed

Hotrod api/traces displaying connecting refused #4355

prasad-shirodkar opened this issue Mar 30, 2023 · 0 comments

Comments

@prasad-shirodkar
Copy link

What happened?

I am trying to deploy hotrod 1.42.0 following the instructions at https://github.com/jaegertracing/jaeger/tree/v1.42.0/examples/hotrod.

Steps to reproduce

  1. Run Jaeger backend
  2. Run HotROD from source
git clone [email protected]:jaegertracing/jaeger.git jaeger
git checkout v.1.42.0
cd jaeger
go run ./examples/hotrod/main.go all

2023-03-30T18:22:07.301Z	INFO	[email protected]/command.go:946	Using expvar as metrics backend
2023-03-30T18:22:07.301Z	INFO	[email protected]/command.go:916	Starting all services
2023-03-30T18:22:07.301Z	INFO	tracing/init.go:54	using jaeger trace exporter	{"service": "frontend"}
2023-03-30T18:22:07.301Z	INFO	tracing/init.go:54	using jaeger trace exporter	{"service": "customer"}
2023-03-30T18:22:07.301Z	INFO	tracing/init.go:54	using jaeger trace exporter	{"service": "driver"}
2023-03-30T18:22:07.301Z	INFO	tracing/init.go:67	created OTEL->OT brige	{"service": "frontend", "service-name": "frontend"}
2023-03-30T18:22:07.301Z	INFO	tracing/init.go:67	created OTEL->OT brige	{"service": "customer", "service-name": "customer"}
2023-03-30T18:22:07.301Z	INFO	tracing/init.go:67	created OTEL->OT brige	{"service": "driver", "service-name": "driver"}
2023-03-30T18:22:07.301Z	INFO	tracing/init.go:54	using jaeger trace exporter	{"service": "customer"}
2023-03-30T18:22:07.301Z	INFO	tracing/init.go:54	using jaeger trace exporter	{"service": "driver"}
2023-03-30T18:22:07.301Z	INFO	tracing/init.go:54	using jaeger trace exporter	{"service": "route"}
2023-03-30T18:22:07.302Z	INFO	tracing/init.go:67	created OTEL->OT brige	{"service": "driver", "service-name": "redis"}
2023-03-30T18:22:07.301Z	INFO	tracing/init.go:67	created OTEL->OT brige	{"service": "customer", "service-name": "mysql"}
2023-03-30T18:22:07.302Z	INFO	customer/server.go:55	Starting	{"service": "customer", "address": "http://0.0.0.0:8081"}
2023-03-30T18:22:07.302Z	INFO	frontend/server.go:74	Starting	{"service": "frontend", "address": "http://0.0.0.0:8080"}
2023-03-30T18:22:07.302Z	INFO	tracing/init.go:67	created OTEL->OT brige	{"service": "route", "service-name": "route"}
2023-03-30T18:22:07.302Z	INFO	route/server.go:57	Starting	{"service": "route", "address": "http://0.0.0.0:8083"}
2023/03/30 18:22:27 Post "http://localhost:14268/api/traces": dial tcp 127.0.0.1:14268: connect: connection refused

More connection refused message show up on clicking the examples in hotrod UI http://localhost:8080/

Expected behavior

No errors when using hotrod.

Relevant log output

No response

Screenshot

No response

Additional context

Similar issue has been logged as opensearch-project/data-prepper#2273

Jaeger backend version

No response

SDK

No response

Pipeline

No response

Stogage backend

No response

Operating system

Oracle Linux 7

Deployment model

No response

Deployment configs

No response

@yurishkuro yurishkuro changed the title [Bug]: Hotrod api/traces displaying connecting refused Hotrod api/traces displaying connecting refused Mar 31, 2023
@yurishkuro yurishkuro removed the bug label Mar 31, 2023
@jaegertracing jaegertracing locked and limited conversation to collaborators Mar 31, 2023
@yurishkuro yurishkuro converted this issue into discussion #4356 Mar 31, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants