question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Issue with installation

See original GitHub issue

Hello,

I’m not sure this is a bug or something I’m doing wrong. I’m having some issues installing tracetest and getting it to work. I’d appreciate it if you could point me in the right direction.

Describe the bug I tried installing using the setup script. Installation seems to be successful(no error log seen)

Log I tried the port forwarding as instructed after the installation but I get this error:

○ → kubectl port-forward --namespace my-test-namespace svc/tracetest 8080:8080
Forwarding from 127.0.0.1:8080 -> 8080
Forwarding from [::1]:8080 -> 8080
Handling connection for 8080
Handling connection for 8080
E0811 17:42:18.939952   50154 portforward.go:406] an error occurred forwarding 8080 -> 8080: error forwarding port 8080 to pod 5800e8116a0baed5cf9fa336ae06ba13febe37dfa2dd6b6b7bddd8b63bf593a9, uid : exit status 1: 2022/08/11 16:42:18 socat[64005] E connect(5, AF=2 127.0.0.1:8080, 16): Connection refused
E0811 17:42:18.940455   50154 portforward.go:234] lost connection to pod
Handling connection for 8080
E0811 17:42:18.941192   50154 portforward.go:346] error creating error stream for port 8080 -> 8080: EOF

Upon inspecting tracetest pod log, it’s in CrashLoopBackOff state:

○ → k get pods --namespace my-test-namespace
NAME                         READY   STATUS             RESTARTS       AGE
jaeger-748ccdcff7-xwkbm      1/1     Running            0              36m
tracetest-5648f7bff7-lwjnz   0/1     CrashLoopBackOff   12 (74s ago)   37m
tracetest-postgresql-0       1/1     Running            0              37m

So the tracetest pod is having trouble here, looking at the pod log, I see.

○ → kubectl logs --namespace my-test-namespace -f svc/tracetest
2022/08/11 16:52:44 could not get trace provider: could not create exporter: could not create gRPC connection to collector: context deadline exceeded

otel collector pod seemed ok:

○ → k get pods
NAME                              READY   STATUS    RESTARTS   AGE
otel-collector-5d475cfc6b-snznq   1/1     Running   0          61m

But the log says it’s not:

○ → k logs otel-collector-5d475cfc6b-snznq
...
2022-08-11T16:16:24.531Z	info	pipelines/pipelines.go:106	Exporter started.	{"kind": "receiver", "name": "otlp", "pipeline": "traces"}
2022-08-11T16:16:24.531Z	info	service/collector.go:220	Starting otelcol...	{"Version": "0.54.0", "NumCPU": 4}
2022-08-11T16:16:24.531Z	info	service/collector.go:128	Everything is ready. Begin running and processing data.
2022-08-11T16:16:24.532Z	warn	zapgrpc/zapgrpc.go:191	[core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {
  "Addr": "jaeger-collector.tracetest.svc.cluster.local:14250",
  "ServerName": "jaeger-collector.tracetest.svc.cluster.local:14250",
  "Attributes": null,
  "BalancerAttributes": null,
  "Type": 0,
  "Metadata": null
}. Err: connection error: desc = "transport: Error while dialing dial tcp: lookup jaeger-collector.tracetest.svc.cluster.local on 10.96.0.10:53: no such host"	{"grpc_log": true}
2022-08-11T16:16:25.530Z	info	jaegerexporter@v0.54.0/exporter.go:186	State of the connection with the Jaeger Collector backend	{"kind": "exporter", "data_type": "traces", "name": "jaeger", "state": "TRANSIENT_FAILURE"}
2022-08-11T16:16:26.531Z	info	jaegerexporter@v0.54.0/exporter.go:186	State of the connection with the Jaeger Collector backend	{"kind": "exporter", "data_type": "traces", "name": "jaeger", "state": "IDLE"}

To Reproduce Steps to reproduce the behavior: Run setup script as instructed. curl -L https://raw.githubusercontent.com/kubeshop/tracetest/main/setup.sh | bash -s -- --namespace my-test-namespace

Issue Analytics

  • State:open
  • Created a year ago
  • Reactions:1
  • Comments:16

github_iconTop GitHub Comments

2reactions
ljo327commented, Aug 12, 2022

I’ve got it working, thank you very much for your help. I was hoping to see more calling relationships in the Graph view but I’m only seeing 1 service so I will investigate a bit further.

In the meantime, I think it’d be super powerful to have some e2e framework integrated, such as Cypress(which Testkube has), and have trace id collected during the UI interaction. Maybe some time in the future 🙂

1reaction
kdhamriccommented, Aug 15, 2022

@ljo-jones Glad to see you got Tracetest installed successfully. Ping me (KenHamric) over on Discord - would like to hear how you are using Tracetest & get more thoughts from you on how you would like to see it integrated with Cypress. Also wanted to send you some swag!!

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to troubleshoot Windows Installer errors - Microsoft Support
Describes how to troubleshoot problems that occur when you install, uninstall, or upgrade a program on a Windows-based computer by using Windows Installer....
Read more >
How to Fix the Most Common Windows 10 Installation Problems
How to fix the most common Windows 10 installation problems · Run the Windows Update troubleshooter · Low disk space · ISO image...
Read more >
Installation issues and solutions - IBM
Review common problem scenarios, recovery methods, and ways to get help if you encounter a problem during software installation. You can diagnose problems...
Read more >
12 irritating Windows 10 installation issues, and how to fix them
Having trouble installing and setting up Windows 10? You aren't alone. Here are a dozen-plus of the most common problems, along with a...
Read more >
4 Solutions to Fix Windows 10/11 Installation Has Failed
Boot Manager Corruption: Any errors or issues found in your boot manager could cause this Windows error to occur. Note that the Boot...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found