Troubleshooting SigNoz Local Setup on M1 Mac

TLDR Sindhu had issues with their local SigNoz installation using Docker on an M1 Mac. Srikanth helped diagnose the problem. It was resolved by manually starting the ClickHouse container and then starting SigNoz via Docker Compose in the terminal.

Photo of Sindhu
Sindhu
Fri, 17 Mar 2023 18:35:15 UTC

hi, I have installed signoz locally via Docker compose on m1 mac. All services are up and running. Able to access the frontend, however XHR call on /signup is pending, I don't see it in the Logs of the frontend docker also. How can I fix this?

Photo of Sindhu
Sindhu
Fri, 17 Mar 2023 18:48:12 UTC

`2023-03-18 00:11:39 172.18.0.1 - - [17/Mar/2023:18:41:39 +0000] "POST /api/v1/register HTTP/1.1" 499 0 "" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36" "-"` I see this in the Docker frontend logs

Photo of Srikanth
Srikanth
Sat, 18 Mar 2023 02:27:56 UTC

This is unexpected, are you sure all the services are running?

Photo of Sindhu
Sindhu
Sat, 18 Mar 2023 05:24:28 UTC

```🟡 Starting the SigNoz containers. It may take a few minutes ... [+] Running 9/9 ⠿ Container load-hotrod Running 0.0s ⠿ Container hotrod Running 0.0s ⠿ Container zookeeper-1 Running 0.0s ⠿ Container clickhouse Healthy 0.6s ⠿ Container query-service Healthy 1.2s ⠿ Container clickhouse-setup-otel-collector-metrics-1 Running 0.0s ⠿ Container clickhouse-setup-alertmanager-1 Running 0.0s ⠿ Container frontend Running 0.0s ⠿ Container clickhouse-setup-otel-collector-1 Running 0.0s```

Photo of Sindhu
Sindhu
Sat, 18 Mar 2023 05:24:48 UTC

```(base) ➜ deploy git:(main) docker-compose -f docker/clickhouse-setup/docker-compose.yaml up -d [+] Running 9/9 ⠿ Container hotrod Running 0.0s ⠿ Container zookeeper-1 Running 0.0s ⠿ Container load-hotrod Running 0.0s ⠿ Container clickhouse Healthy 0.6s ⠿ Container clickhouse-setup-otel-collector-metrics-1 Running 0.0s ⠿ Container query-service Healthy 1.1s ⠿ Container clickhouse-setup-otel-collector-1 Running 0.0s ⠿ Container clickhouse-setup-alertmanager-1 Running 0.0s ⠿ Container frontend Running 0.0s (base) ➜ deploy git:(main) ```

Photo of Sindhu
Sindhu
Sat, 18 Mar 2023 05:24:57 UTC

Looks like everything is up and running fine

Photo of Srikanth
Srikanth
Sat, 18 Mar 2023 07:44:06 UTC

What do query-service logs show?

Photo of Sindhu
Sindhu
Sat, 18 Mar 2023 11:53:19 UTC

Looks like there is some kind of panic runtime error. I feel like there is some configuration conflict with my existing clickhouse containers. Not sure about this.

Photo of Srikanth
Srikanth
Sat, 18 Mar 2023 12:34:08 UTC

It’s unable to connect to ClickHouse. Please make sure it’s running available for connections.

Photo of Sindhu
Sindhu
Sat, 18 Mar 2023 14:26:55 UTC

There are two `clickhouse-*` which of these is it trying to connect to?

Photo of Sindhu
Sindhu
Sat, 18 Mar 2023 14:27:23 UTC

also what port does clickhouse need to be running on?

Photo of Srikanth
Srikanth
Sat, 18 Mar 2023 14:28:30 UTC

Those `clickhouse-setup-*` are not ClickHouse instances, they are collector instances. Clickhouse runs on 9000/8123 for native/http interface.

Photo of Sindhu
Sindhu
Thu, 23 Mar 2023 16:19:10 UTC

Thanks, I manually started clickhouse container and then all other containers were able to run. Pressing :arrow_forward: button against the existing signoz docker container in Docker Desktop app starts containers hapazhardly I think? Starting Signoz via docker-compose command in terminal, starts up all containers in the order they need to be I guess?

Photo of Srikanth
Srikanth
Thu, 23 Mar 2023 18:10:53 UTC

Yes