alan
04/25/2022, 1:51 PMexec user process caused "exec format error"
by using default image ("signoz/sample-django:latest"), googled and found require to rebuild docker image after adding #!/bin/bash
in dockerfile, and then I got below errors can you help why this issue happen , I used offical dockerfile to build image
/bin/sh: 1: [opentelemetry-instrument,: not found
Prashant Shahi
04/25/2022, 4:21 PMalan
04/25/2022, 8:44 PMroot@uls-tst01-gen1-7b64d94f9c-2zlr8:/# uname -a
Linux uls-tst01-gen1-7b64d94f9c-2zlr8 5.4.0-1025-gkeop #26~18.04.1-Ubuntu SMP Mon Oct 4 03:14:34 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
root@uls-tst01-gen1-7b64d94f9c-2zlr8:/#
/bin/sh: 1: [opentelemetry-instrument,: not found
when creating pod in kuberenetes. so the docker image should be fine.Prashant Shahi
04/26/2022, 4:20 AMalan
04/26/2022, 9:25 AMPrashant Shahi
04/27/2022, 5:19 AMSrikanth Chekuri
04/28/2022, 1:38 AMPrashant Shahi
04/28/2022, 5:53 AMdocker run --env OTEL_METRICS_EXPORTER=none \
--env OTEL_SERVICE_NAME=djangoApp \
--env OTEL_EXPORTER_OTLP_ENDPOINT=http://<IP of SigNoz>:4317 \
--env DJANGO_SETTINGS_MODULE=mysite.settings \
-p 8000:8000 \
-t signoz/sample-django:latest opentelemetry-instrument gunicorn mysite.wsgi -c gunicorn.config.py --workers 2 --threads 2 --reload --bind 0.0.0.0:8000
Meanwhile, I am working on improving the Dockerfile to fix this and reduce the image size.
Also, I believe @Srikanth Chekuri would be the best person who would have more knowledge on the Django sample app.alan
04/28/2022, 7:01 AM/bin/sh: 1: [opentelemetry-instrument,: not found
that's the point, I wonder have you run this in kubernetes ? I am not able to instrument data to SigNoz.Prashant Shahi
04/28/2022, 7:02 AMPrashant Shahi
04/28/2022, 7:06 AMcommand
. Can you include the equipment environment variables and the command from the following in the manifest?
docker run --env OTEL_METRICS_EXPORTER=none \
--env OTEL_SERVICE_NAME=djangoApp \
--env OTEL_EXPORTER_OTLP_ENDPOINT=http://<IP of SigNoz>:4317 \
--env DJANGO_SETTINGS_MODULE=mysite.settings \
-p 8000:8000 \
-t signoz/sample-django:latest opentelemetry-instrument gunicorn mysite.wsgi -c gunicorn.config.py --workers 2 --threads 2 --reload --bind 0.0.0.0:8000
alan
04/28/2022, 7:06 AMPrashant Shahi
04/28/2022, 7:07 AMalan
04/28/2022, 7:08 AM<http://node.kubernetes.io/unreachable:NoExecute|node.kubernetes.io/unreachable:NoExecute> op=Exists for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 2m44s default-scheduler Successfully assigned alantest/sample-django-deployment-799456b8cc-8vtr2 to uls-tst01-gen1-7b64d94f9c-p949m
Normal Pulled 2m43s kubelet Successfully pulled image "<http://artifactory.wdc.com:6560/bdp-eng-docker/sample-django:amd|artifactory.wdc.com:6560/bdp-eng-docker/sample-django:amd>" in 97.653019ms
Normal Pulled 2m42s kubelet Successfully pulled image "<http://artifactory.wdc.com:6560/bdp-eng-docker/sample-django:amd|artifactory.wdc.com:6560/bdp-eng-docker/sample-django:amd>" in 69.621653ms
Normal Pulled 2m27s kubelet Successfully pulled image "<http://artifactory.wdc.com:6560/bdp-eng-docker/sample-django:amd|artifactory.wdc.com:6560/bdp-eng-docker/sample-django:amd>" in 65.713606ms
Normal Created 119s (x4 over 2m43s) kubelet Created container sample-django
Warning Failed 119s (x4 over 2m43s) kubelet Error: failed to create containerd task: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "opentelemetry-instrument gunicorn mysite.wsgi -c gunicorn.config.py --workers 2 --threads 2 --reload --bind 0.0.0.0:8000": executable file not found in $PATH: unknown
Normal Pulled 119s kubelet Successfully pulled image "<http://artifactory.wdc.com:6560/bdp-eng-docker/sample-django:amd|artifactory.wdc.com:6560/bdp-eng-docker/sample-django:amd>" in 65.166385ms
Warning BackOff 84s (x8 over 2m41s) kubelet Back-off restarting failed container
Normal Pulling 73s (x5 over 2m43s) kubelet Pulling image "<http://artifactory.wdc.com:6560/bdp-eng-docker/sample-django:amd|artifactory.wdc.com:6560/bdp-eng-docker/sample-django:amd>"
Prashant Shahi
04/28/2022, 7:49 AMcommand: ["opentelemetry-instrument", "gunicorn", "mysite.wsgi", "-c", "gunicorn.config.py", "--workers", "2", "--threads", "2", "--reload", "--bind", "0.0.0.0:8000"]
alan
04/28/2022, 7:53 AMgunicorn: error: unrecognized arguments: none djangoApp <http://my-release-signoz-otel-collector:4317> mysite.settings
Prashant Shahi
04/28/2022, 7:56 AMargs
?alan
04/28/2022, 7:56 AMPrashant Shahi
04/28/2022, 7:59 AMalan
04/28/2022, 7:59 AMC02XGC2HJG5H:apmtest ah1000259263$ k get svc -n alantest
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
clickhouse-operator-metrics ClusterIP 172.30.240.102 <none> 8888/TCP 14d
jaeger-test-agent ClusterIP 172.30.241.78 <none> 5775/UDP,6831/UDP,6832/UDP,5778/TCP,14271/TCP 10d
jaeger-test-cassandra ClusterIP None <none> 7000/TCP,7001/TCP,7199/TCP,9042/TCP,9160/TCP 10d
jaeger-test-collector ClusterIP 172.30.241.211 <none> 14250/TCP,14268/TCP,14269/TCP 10d
jaeger-test-query ClusterIP 172.30.241.46 <none> 80/TCP,16687/TCP 10d
my-release-clickhouse ClusterIP 172.30.240.62 <none> 8123/TCP,9000/TCP 14d
my-release-signoz-alertmanager ClusterIP 172.30.241.35 <none> 9093/TCP 14d
my-release-signoz-alertmanager-headless ClusterIP None <none> 9093/TCP 14d
my-release-signoz-frontend ClusterIP 172.30.241.173 <none> 3301/TCP 14d
my-release-signoz-otel-collector ClusterIP 172.30.240.254 <none> 4317/TCP,4318/TCP,55680/TCP,55681/TCP,14250/TCP,14268/TCP,9411/TCP,8888/TCP,8889/TCP 14d
my-release-signoz-otel-collector-metrics ClusterIP 172.30.241.20 <none> 4317/TCP,4318/TCP,55680/TCP,55681/TCP,14250/TCP,14268/TCP,9411/TCP,8888/TCP 14d
my-release-signoz-query-service ClusterIP 172.30.240.200 <none> 8080/TCP 14d
my-release-zookeeper ClusterIP 172.30.240.207 <none> 2181/TCP,2888/TCP,3888/TCP 14d
my-release-zookeeper-headless ClusterIP None <none> 2181/TCP,2888/TCP,3888/TCP
- name: OTEL_EXPORTER_OTLP_ENDPOINT
value: "<http://my-release-signoz-otel-collector:4317>"
Prashant Shahi
04/28/2022, 8:11 AMhttp://<IP of SigNoz>:3301
ankitnayan
password: password
alan
04/28/2022, 8:13 AM--bind", "0.0.0.0:8000"]
in yaml, when I create virtual service I got 400
error @Prashant ShahiPrashant Shahi
04/28/2022, 8:44 AM<http://localhost:8000/admin>
<http://localhost:8000/polls/>
alan
04/28/2022, 8:50 AMPrashant Shahi
04/28/2022, 8:52 AMalan
04/28/2022, 8:52 AMPrashant Shahi
04/28/2022, 8:52 AMalan
04/28/2022, 8:53 AMPrashant Shahi
04/28/2022, 8:54 AMkubectl -n platform run troubleshoot --image=signoz/troubleshoot \
--restart='OnFailure' -i --tty --rm --command -- ./troubleshoot checkEndpoint \
--endpoint=my-release-signoz-otel-collector.platform.svc.cluster.local:4317
alan
04/28/2022, 8:57 AMC02XGC2HJG5H:jaeger ah1000259263$ kubectl -n alantest run troubleshoot --image=<http://artifactory.wdc.com:6609/signoz/troubleshoot|artifactory.wdc.com:6609/signoz/troubleshoot> -l e2-criticality=2,e2-environment=DEV,e2-owner=E2.Owner,e2-project=e2-migration,e2-support-contact=E2.Support \
> --restart='OnFailure' -i --tty --rm --command -- ./troubleshoot checkEndpoint \
> --endpoint=my-release-signoz-otel-collector:4317
If you don't see a command prompt, try pressing enter.
Error attaching, falling back to logs: unable to upgrade connection: container troubleshoot not found in pod troubleshoot_alantest
2022-04-28T09:10:37.205Z INFO troubleshoot/main.go:28 STARTING!
2022-04-28T09:10:37.208Z INFO checkEndpoint/checkEndpoint.go:41 checking reachability of SigNoz endpoint
2022-04-28T09:10:37.335Z INFO troubleshoot/main.go:46 Successfully sent sample data to signoz ...
pod "troubleshoot" deleted
troubleshoot/main.go:46 Successfully sent sample data to signoz
Prashant Shahi
04/28/2022, 9:13 AMalan
04/28/2022, 9:15 AM- name: OTEL_EXPORTER_OTLP_ENDPOINT
value: <http://my-release-signoz-otel-collector:4317>
Prashant Shahi
04/28/2022, 9:51 AMalan
04/28/2022, 10:07 AMPrashant Shahi
04/28/2022, 10:10 AMalan
04/28/2022, 10:10 AM