https://signoz.io logo
Powered by
#support
Title
# support
n

Nicolai Birkmose Oksen

10/31/2023, 4:23 PM
Hey 🙂 I'm trying to spin up a Signoz instance on Azure - Using an external Clickhouse instance. I'm getting the following error in the signozschemamigrator:
Copy code
{
  "level": "fatal",
  "timestamp": "2023-10-31T16:03:57.316Z",
  "caller": "signozschemamigrator/migrate.go:79",
  "msg": "Failed to create migration manager",
  "component": "migrate cli",
  "error": "failed to parse dsn: parse \"tcp://<redacted>.aws.clickhouse.cloud:%!s(float64=9000)?username=default&password=<redacted>\": invalid port \":%!s(float64=9000)\" after host",
  "stacktrace": "main.main\n\t/home/runner/work/signoz-otel-collector/signoz-otel-collector/cmd/signozschemamigrator/migrate.go:79\nruntime.main\n\t/opt/hostedtoolcache/go/1.20.10/x64/src/runtime/proc.go:250"
}
I've set the port in the Helm Chart values to 9000.
I figured it out - Port had to be a string. New issue - it fails to ping the clickhouse instance. I'm using Clickhouse Cloud - any suggestions?
n

Nočnica Mellifera

10/31/2023, 7:25 PM
I felt so smart noticing 
(float64=9000)
but it looks like you figured out that bit, does a test ping to your clickhouse cloud instance succeed?
n

Nicolai Birkmose Oksen

10/31/2023, 7:26 PM
Do you mean a simple ping from the command line on my pc?
n

Nočnica Mellifera

10/31/2023, 7:27 PM
yeah, like, is the instance available at :9000 ?
m

Mayur B

11/09/2023, 2:55 PM
@Nočnica Mellifera 8123 is being automatically appended in the Init Containers despite giving 9000 in the port. Also if i remove the Ports from the endpoint, the init container connects successfully to the db but the main pod gives missing port error
@Prashant Shahi
Copy code
{
  "level": "fatal",
  "timestamp": "2023-11-09T14:59:48.372Z",
  "caller": "signozschemamigrator/migrate.go:104",
  "msg": "Failed to create migration manager",
  "component": "migrate cli",
  "error": "failed to parse dsn: parse \"<tcp://clickhouse-microk8s>:%!s(float64=9000)?username=xxx&password=xxx\": invalid port \":%!s(float64=9000)\" after host",
  "stacktrace": "main.main\n\t/home/runner/work/signoz-otel-collector/signoz-otel-collector/cmd/signozschemamigrator/migrate.go:104\nruntime.main\n\t/opt/hostedtoolcache/go/1.20.10/x64/src/runtime/proc.go:250"
}
This is what happens if i remove the port. This is the schema-migrator-pod. And this is the init container when the port is removed
where is the value for .clickhouse.httpUrl being fetched from in the repo?
Temporarily resolved it by disabling
Copy code
schemaMigrator:
  enabled: false
Copy code
TCPHandler: Code: 81. DB::Exception: Database signoz_metrics doesn't exist
This is the error i get when i disable migrator
signoz_metrics db is not getting created when deploying clickhouse helm chart
Powered by