#general

Resolving Sample Application Installation and Tracing Generation Issue

TLDR Eugene faced issues installing a sample application and generating tracing data. Prashant troubleshooted the problem and ultimately guided Eugene to switch to the 'develop' branch and update the locust tag, which resolved the issue.

4mo

Join the chat

Jul 10, 2023 (5 months ago)

Photo of md5-0ca37054c6c9042aa04fcfb92cc7d99c

Eugene

02:04 PM

Hello,
I am trying to install sample-application and generate tracing data
https://signoz.io/docs/install/kubernetes/others/#optional-install-a-sample-application-and-generate-tracing-data

But pods cannot start:

Normal   Pulling    6s (x3 over 48s)   kubelet            Pulling image "signoz/locust:0.8.1-py3.6"                                                                                                                   ││   Warning  Failed     5s (x3 over 47s)   kubelet            Failed to pull image "signoz/locust:0.8.1-py3.6": rpc error: code = NotFound desc = failed to pull and unpack image "":  ││ failed to resolve reference "": : not found                                                                                                       ││   Warning  Failed     5s (x3 over 47s)   kubelet            Error: ErrImagePull

Image 1 for Hello,
I am trying to install sample-application and generate tracing data
<https://signoz.io/docs/install/kubernetes/others/#optional-install-a-sample-application-and-generate-tracing-data>

But pods cannot start:
```Normal Pulling 6s (x3 over 48s) kubelet Pulling image "signoz/locust:0.8.1-py3.6" ││ Warning Failed 5s (x3 over 47s) kubelet Failed to pull image "signoz/locust:0.8.1-py3.6": rpc error: code = NotFound desc = failed to pull and unpack image "<http://docker.io/signoz/locust:0.8.1-py3.6|docker.io/signoz/locust:0.8.1-py3.6>": ││ failed to resolve reference "<http://docker.io/signoz/locust:0.8.1-py3.6|docker.io/signoz/locust:0.8.1-py3.6>": <http://docker.io/signoz/locust:0.8.1-py3.6|docker.io/signoz/locust:0.8.1-py3.6>: not found ││ Warning Failed 5s (x3 over 47s) kubelet Error: ErrImagePull ```

Jul 11, 2023 (5 months ago)

Photo of md5-1899629483c7ab1dccfbee6cc2f637b9

Prashant

05:32 AM

Hello Eugene 👋

This issue has been addressed in this PR: https://github.com/SigNoz/signoz/pull/3096

Eugene

06:46 PM

now image can be download and pods start but they crush with the following logs:

Prashant

06:51 PM

we have updated the Hotrod manifest as well as updated docs.

can you delete the sample-application namespace and retry the Hotrod sample-app installation?

06:54

Prashant

06:54 PM

https://signoz.io/docs/install/kubernetes/others/#optional-install-a-sample-application-and-generate-tracing-data

Jul 12, 2023 (5 months ago)

Eugene

01:50 PM

I tried to deploy sample-application from the scratch. uninstall it completely and install again. it did not help. the result and the logs are still the same.

Prashant

03:03 PM

Fix was merged 4 hours back: https://github.com/SigNoz/signoz/pull/3112

03:04

Prashant

03:04 PM

Did you retry recently?

Eugene

03:05 PM

let me try once more…

Prashant

03:05 PM

yes please.

03:05

Prashant

03:05 PM

do let us know if this works

Eugene

03:28 PM

the problem with image pulling returned

03:28

Eugene

03:28 PM

docker pull signoz/locust:0.8.1-py3.6

Error response from daemon: manifest for signoz/locust:0.8.1-py3.6 not found: manifest unknown: manifest unknown

03:29

Eugene

03:29 PM

Warning  Failed     3s    kubelet            Failed to pull image "signoz/locust:0.8.1-py3.6": rpc error: code = NotFound desc = failed to pull and unpack image "": failed to res │
│ olve reference "": : not found                                                                                                                    │
│   Warning  Failed     3s    kubelet            Error: ErrImagePull

Prashant

03:30 PM

did you cleanup old sample application namespace?

03:30

Prashant

03:30 PM

also, why is it pointing to 0.8.1, it should be using 1.2.3

Eugene

03:34 PM

yes. i cleaned up old sample namespace. actually the removal script does it itself.

Delete HotROD sample app namespace sample-application
namespace "sample-application" deleted
✅ Successfully deleted HotROD sample application

but I double checked, there is no such namespace any more

Prashant

03:35 PM

can you share the command that you used to install?

03:36

Prashant

03:36 PM

Yesterday, docs was updated as welll: https://signoz.io/docs/install/kubernetes/others/#optional-install-a-sample-application-and-generate-tracing-data

Eugene

03:36 PM

i use the following command from the guide located on the Signoz site:

curl -sL  \   | HELM_RELEASE=signoz-demo SIGNOZ_NAMESPACE=signoz bash

with my env vars.
I downloaded the hotrod-install.sh from the specified url. it contains:

# Locust's docker image
if [[ -z $LOCUST_IMAGE ]]; then
    LOCUST_REPO="${LOCUST_REPO:-signoz/locust}"
    LOCUST_TAG="${LOCUST_TAG:-0.8.1-py3.6}"
    LOCUST_IMAGE="${LOCUST_REPO}:${LOCUST_TAG}"
fi

Prashant

03:36 PM

use develop instead of main

Eugene

03:37 PM

got it. let me try.

Prashant

03:37 PM

also, LOCUST_TAG should default to 1.2.3

Eugene

03:39 PM

03:39

Eugene

03:39 PM

Prashant

03:42 PM

why HttpLocust is being used there.
It is likely using old version from main branch instead.

Did you try the latest commands from docs?

03:42

Prashant

03:42 PM

I just tested it from docs again. It works without any problem.

Eugene

03:44 PM

03:47

Eugene

03:47 PM

at the same time hotrod works fine

03:53

Eugene

03:53 PM

tried once again. the result is the same.

Prashant

06:36 PM

it looks like it is still creating locust-slave instead of locust-worker

06:42

Prashant

06:42 PM

can you confirm the content of the install script.

wget

^ it should match with the GitHub remote: https://raw.githubusercontent.com/SigNoz/signoz/develop/sample-apps/hotrod/hotrod-install.sh

After that you can execute the local script:

cat hotrod-install.sh | HELM_RELEASE=signoz-demo SIGNOZ_NAMESPACE=signoz bash

Jul 13, 2023 (4 months ago)

Eugene

05:54 AM

the files are the same. it is working now. thank you.

Prashant

06:34 AM

glad to know it works now 🙂

SigNoz Community

Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI

Indexed 1023 threads (61% resolved)

Join Our Community

Similar Threads

SigNoz Production Feedback and Improvement Suggestions

Users shared their SigNoz experiences and feedback. Issues mentioned include memory consumption, UI/UX improvements, connection difficulties, and automation limitations.

9mo

Deploying SigNoz in AKS Production Cluster with Sample Application

Koushik asks about using SigNoz in an AKS production cluster and wants a sample app. Prashant provides instructions for setting up SigNoz in AKS and suggests HotROD and other sample applications for testing.

6mo

SigNoz Install Script Errors

Nishant encountered errors with the install.sh script. Prashant suggested using `bash install.sh` or `./install.sh` instead of `sh`.

7mo

Extracting Custom Fields as Attributes from Log in SigNoz

Harald wants to have custom fields from their body parsed as attributes in the SigNoz logger. They have tried implementing suggestions from nitya-signoz and Prashant, but the issue remains unsolved due to a potential race condition encountered while executing the code. They have provided a full example using Kind for further assistance.

209

5mo

Issues with SigNoz Setup and Data Persistence in AKS

Vaibhavi experienced issues setting up SigNoz in AKS, and faced data persistence issues after installation. Srikanth provided guidance on ClickHouse version compatibility and resource requirements, helping Vaibhavi troubleshoot and resolve the issue.

8mo