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

TraceCollector in constant CrashLoopBackOff state #95

Open
DesAWSume opened this issue Sep 20, 2024 · 1 comment
Open

TraceCollector in constant CrashLoopBackOff state #95

DesAWSume opened this issue Sep 20, 2024 · 1 comment

Comments

@DesAWSume
Copy link

I first deployed metricsCollector and then TraceCollector via Helm to my EKS cluster

helm -n <namespace> upgrade kube-otel-stack lightstep/kube-otel-stack \
  --set metricsCollector.clusterName=<ClusterName> \
  --set metricsCollector.replicas=1 \
  --set metricsCollector.targetallocator.replicas=1 \
  --set tracesCollector.clusterName=<ClusterName>  \
  --set tracesCollector.enabled=true \

However, TraceCollector stuck at CrashLoopBackOff state

Logs show below:
Error: at least one Provider must be supplied 2024/09/20 04:43:30 collector server run finished with error: at least one Provider must be supplied

Described it like below

image

Do anyone know what is the issue for this?

@DesAWSume
Copy link
Author

Did the same on otel-cloud-stack lightstep/otel-cloud-stack

image

logs show below
Error: at least one Provider must be supplied 2024/09/20 05:03:12 collector server run finished with error: at least one Provider must be supplied

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

1 participant