Hey folks, Did anybody face such an issue. I run s...
# support
s
Hey folks, Did anybody face such an issue. I run signoz in the swarm mode under wsl. And it seems like all domain names are wrongly resolved:
Copy code
2024-11-07 13:52:54 SigNoz version   : v0.56.0
2024-11-07 13:52:54 Commit SHA-1     : b70d50f
2024-11-07 13:52:54 Commit timestamp : 2024-10-10T10:10:41Z
2024-11-07 13:52:54 Branch           : HEAD
2024-11-07 13:52:54 Go version       : go1.22.7
2024-11-07 13:52:54 
2024-11-07 13:52:54 For SigNoz Official Documentation,  visit <https://signoz.io/docs/>
2024-11-07 13:52:54 For SigNoz Community Slack,         visit <http://signoz.io/slack/>
2024-11-07 13:52:54 For archive of discussions about SigNoz,       visit <https://knowledgebase.signoz.io/>
2024-11-07 13:52:54 
2024-11-07 13:52:54 Check SigNoz Github repo for license details.
2024-11-07 13:52:54 Copyright 2024 SigNoz
2024-11-07 13:52:54 
2024-11-07 13:52:54 {"level":"WARN","timestamp":"2024-11-07T13:52:54.926Z","caller":"query-service/main.go:152","msg":"No JWT secret key is specified."}
2024-11-07 13:52:54 {"level":"INFO","timestamp":"2024-11-07T13:52:54.928Z","caller":"query-service/main.go:160","msg":"Migration successful"}
2024-11-07 13:52:55 {"level":"INFO","timestamp":"2024-11-07T13:52:55.108Z","caller":"license/manager.go:126","msg":"No active license found, defaulting to basic plan"}
2024-11-07 13:52:55 {"level":"INFO","timestamp":"2024-11-07T13:52:55.109Z","caller":"app/server.go:149","msg":"Using ClickHouse as datastore ..."}
2024-11-07 13:52:55 {"level":"INFO","timestamp":"2024-11-07T13:52:55.109Z","caller":"clickhouseReader/options.go:108","msg":"Connecting to Clickhouse","at":"clickhouse:9000","MaxIdleConns":50,"MaxOpenConns":100,"DialTimeout":5000}
2024-11-07 13:52:58 {"level":"FATAL","timestamp":"2024-11-07T13:52:58.585Z","caller":"clickhouseReader/reader.go:170","msg":"failed to initialize ClickHouse","error":"error connecting to primary db: dial tcp: lookup clickhouse on 127.0.0.11:53: no such host","stacktrace":"<http://go.signoz.io/signoz/pkg/query-service/app/clickhouseReader.NewReader|go.signoz.io/signoz/pkg/query-service/app/clickhouseReader.NewReader>\n\t/home/runner/work/signoz/signoz/pkg/query-service/app/clickhouseReader/reader.go:170\ngo.signoz.io/signoz/ee/query-service/app/db.NewDataConnector\n\t/home/runner/work/signoz/signoz/ee/query-service/app/db/reader.go:30\ngo.signoz.io/signoz/ee/query-service/app.NewServer\n\t/home/runner/work/signoz/signoz/ee/query-service/app/server.go:150\nmain.main\n\t/home/runner/work/signoz/signoz/ee/query-service/main.go:163\nruntime.main\n\t/home/runner/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.22.7.linux-amd64/src/runtime/proc.go:271"}
What's even more confusing is that if I connect to the running containers, it can resolve domains correctly:
Copy code
# from otel-collector
/ # telnet clickhouse 9000
Connected to clickhouse
And it causes most of the containers to fail.
s
SigNoz on WSL doesn't work correctly. We don't officially support this yet.