Hey folks - Docker standalone is failing due to an issue encountered with the ClickHouse Docker container. When attempting to run the ClickHouse Docker container on Oracle Linux 8 with Docker version 24.0.7 and ClickHouse server version 24.1.2-alpine, the following error is encountered:

Processing configuration file '/etc/clickhouse-server/config.xml'.

Poco::Exception. Code: 1000, e.code() = 13, Access to file denied: /etc/clickhouse-server/config.xml

Full log dump: https://gitlab.com/-/snippets/3690972 I attempted to resolve the issue by creating the path /etc/clickhouse-server/ with full permissions . Despite trying to bring up the Docker Compose setup using the root user, the ClickHouse Docker container running on Oracle Linux 8 with Docker version 24.0.7 and ClickHouse server version 24.1.2-alpine still encounters the following error: No luck This issue seems to be related to file permission or access control within the Docker container environment. Any insights or suggestions on how to resolve this issue would be greatly appreciated. Please let me know if further information is required.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

Hi Team, I've done a fresh setup of SigNoz with clickhouse on EKS with 2 shards and 2 replicas (https://signoz.io/docs/operate/clickhouse/distributed-clickhouse/#kubernetes-installation), Now, whenever I do a helm upgrade, the signoz-schema-migrator-sync job runs and fails few times due to table not found errors then automatically succeeds.

Error: code: 60, message: There was an error on [chi-signoz-clickhouse-cluster-1-1:9000]: Code: 60. DB::Exception: Could not find table: time_series_v4. (UNKNOWN_TABLE) (version 24.1.2.5 (official build))

In clickhouse logs as well I see missing table errors. error logs of chi-signoz-clickhouse-cluster-0-0-0:

"message":"Code: 60. DB::Exception: Received from chi-signoz-clickhouse-cluster-1-1:9000. DB::Exception: Table signoz_metrics.samples_v4 does not exist.

"message":"Code: 60. DB::Exception: Received from chi-signoz-clickhouse-cluster-1-1:9000. DB::Exception: Table signoz_metrics.samples_v2 does not exist.

Then while setting the retention on UI, it just gets stuck and in the logs of the query service I see it is not able to do GetTTL from clickhouse:

"msg":"http: panic serving 10.10.249.136:55804: runtime error: invalid memory address or nil pointer dereference\ngoroutine 684 [running]:\nnet/http.(*conn).serve.func1()\n\t/home/runner/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.22.7.linux-amd64/src/net/http/server.go:1903 +0xbe\npanic({0x22593a0?, 0x4155d20?})\n\t/home/runner/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.22.7.linux-amd64/src/runtime/panic.go:770 +0x132\<http://ngo.signoz.io/signoz/pkg/query-service/app/clickhouseReader.(*ClickHouseReader).GetTTL(0xc00011f688|ngo.signoz.io/signoz/pkg/query-service/app/clickhouseReader.(*ClickHouseReader).GetTTL(0xc00011f688>, {0x2f132b8, 0xc000d074a0}

I cleared the SQLite db table as well, but it is still stuck. (https://signoz.io/docs/faqs/troubleshooting/#i-am-trying-to-change-the-retention-period-of-traces-but-the-process-gets-stuck-everytime) Am I missing something wrt to the db schemas? Is anyone able to make it work with the latest helm chart appVersion=0.73.0?

Hello All, In my organization, we use Grafana Alloy, and Otel-contrib as agents and collectors. I want to forward syslogs to SigNoz, which is running as self-hosted for a POC. In this scenario, should I send the data to ports 4317 & 4318 ("SigNoz OTEL Collector") or directly to port 9000? Thanks in advanced.

I'm trying to evaluate Signoz locally, but I can't get it to start. I'm using Docker Desktop on Windows 11.

docker compose -f docker/clickhouse-setup/docker-compose.yaml up -d

[+] Running 11/11
 ✔ Network clickhouse-setup_default  Created                                                                       0.1s
 ✔ Container load-hotrod             Started                                                                       3.2s
 ✔ Container signoz-zookeeper-1      Started                                                                       3.6s
 ✔ Container hotrod                  Started                                                                       3.2s
 ✔ Container signoz-clickhouse       Healthy                                                                      34.5s
 ✘ Container otel-migrator           service "otel-collector-migrator" didn't complet...                          34.3s
 ✔ Container signoz-query-service    Created                                                                       0.2s
 ✔ Container signoz-alertmanager     Created                                                                       0.2s
 ✔ Container signoz-otel-collector   Created                                                                       0.2s
 ✔ Container signoz-logspout         Created                                                                       0.2s
 ✔ Container signoz-frontend         Created                                                                       0.2s

2024-06-07 18:12:40 {"level":"info","timestamp":"2024-06-07T23:12:40.900Z","caller":"signozschemamigrator/migrate.go:89","msg":"Setting env var SIGNOZ_CLUSTER","component":"migrate cli","cluster-name":"cluster"}
2024-06-07 18:12:40 {"level":"info","timestamp":"2024-06-07T23:12:40.900Z","caller":"signozschemamigrator/migrate.go:106","msg":"Successfully set env var SIGNOZ_CLUSTER ","component":"migrate cli","cluster-name":"cluster"}
2024-06-07 18:12:40 {"level":"info","timestamp":"2024-06-07T23:12:40.900Z","caller":"signozschemamigrator/migrate.go:111","msg":"Setting env var SIGNOZ_REPLICATED","component":"migrate cli","replication":false}
2024-06-07 18:12:40 {"level":"info","timestamp":"2024-06-07T23:12:40.906Z","caller":"migrationmanager/manager.go:76","msg":"Running migrations for all migrators","component":"migrationmanager"}
2024-06-07 18:12:40 {"level":"info","timestamp":"2024-06-07T23:12:40.906Z","caller":"migrationmanager/manager.go:78","msg":"Running migrations for logs","component":"migrationmanager","migrator":"logs"}
2024-06-07 18:12:41 {"level":"error","timestamp":"2024-06-07T23:12:41.058Z","caller":"migrationmanager/manager.go:81","msg":"Failed to run migrations for migrator","component":"migrationmanager","migrator":"logs","error":"clickhouse migrate failed to run, error: code: 1001, message: std::__1::__fs::filesystem::filesystem_error: filesystem error: in rename: Permission denied [\"/var/lib/clickhouse/store/b1a/b1a5f878-85cf-44da-bb9f-5e75e6fe6278/tmp_insert_all_1_1_0/\"] [\"/var/lib/clickhouse/store/b1a/b1a5f878-85cf-44da-bb9f-5e75e6fe6278/all_1_1_0/\"] in line 0: INSERT INTO schema_migrations (version, dirty, sequence) VALUES (1, 1, 1717801960995297780)","stacktrace":"github.com/SigNoz/signoz-otel-collector/migrationmanager.(*MigrationManager).Migrate\n\t/home/runner/work/signoz-otel-collector/signoz-otel-collector/migrationmanager/manager.go:81\nmain.main\n\t/home/runner/work/signoz-otel-collector/signoz-otel-collector/cmd/signozschemamigrator/migrate.go:126\nruntime.main\n\t/opt/hostedtoolcache/go/1.21.10/x64/src/runtime/proc.go:267"}
2024-06-07 18:12:41 {"level":"fatal","timestamp":"2024-06-07T23:12:41.058Z","caller":"signozschemamigrator/migrate.go:128","msg":"Failed to run migrations","component":"migrate cli","error":"clickhouse migrate failed to run, error: code: 1001, message: std::__1::__fs::filesystem::filesystem_error: filesystem error: in rename: Permission denied [\"/var/lib/clickhouse/store/b1a/b1a5f878-85cf-44da-bb9f-5e75e6fe6278/tmp_insert_all_1_1_0/\"] [\"/var/lib/clickhouse/store/b1a/b1a5f878-85cf-44da-bb9f-5e75e6fe6278/all_1_1_0/\"] in line 0: INSERT INTO schema_migrations (version, dirty, sequence) VALUES (1, 1, 1717801960995297780)","stacktrace":"main.main\n\t/home/runner/work/signoz-otel-collector/signoz-otel-collector/cmd/signozschemamigrator/migrate.go:128\nruntime.main\n\t/opt/hostedtoolcache/go/1.21.10/x64/src/runtime/proc.go:267"}

in the signoz k8s chart, how do i run the

job/signoz-schema-migrator-upgrade

again? it seems it didnt run properly and

kubectl create job signoz-schema-migrator-upgrade-lolol --from=job/signoz-schema-migrator-upgrade

is not working, giving

error: unknown object type *v1.Job

This message was deleted.