Has anyone encountered the same issue when deployi...
# support
a
Has anyone encountered the same issue when deploying the latest version on signoz I am getting below issue while clicking on traces in the Traces. for reference, I attached a screenshot too.
Copy code
{
  "level": "ERROR",
  "timestamp": "2025-02-06T10:39:39.558Z",
  "caller": "clickhouseReader/reader.go:4517",
  "msg": "error while reading time series result",
  "error": "code: 179, message: Multiple expressions __table1.trace_id and __table2.traceID for alias traceID. In scope SELECT __table2.serviceName AS `subQuery.serviceName`, __table2.name AS `subQuery.name`, count() AS span_count, __table2.durationNano AS `subQuery.durationNano`, __table2.traceID AS traceID FROM signoz_traces.signoz_index_v3 AS __table1 ALL INNER JOIN (SELECT __table3.traceID AS traceID, __table3.durationNano AS durationNano, __table3.serviceName AS serviceName, __table3.name AS name FROM (SELECT __table4.trace_id AS traceID, __table4.duration_nano AS durationNano, __table4.`resource_string_service$$name` AS serviceName, __table4.name AS name FROM signoz_traces.signoz_index_v3 AS __table4 WHERE ((__table4.parent_span_id AS parentSpanID) = '') AND ((__table4.timestamp >= '1738751816000000000') AND (__table4.timestamp <= '1738838216000000000')) AND ((__table4.ts_bucket_start >= 1738750016) AND (__table4.ts_bucket_start <= 1738838216)) ORDER BY durationNano DESC LIMIT _CAST(1, 'UInt64') BY traceID) AS __table3) AS __table2 ON (__table1.trace_id AS traceID) = __table2.traceID WHERE ((__table1.timestamp >= '1738751816000000000') AND (__table1.timestamp <= '1738838216000000000')) AND ((__table1.ts_bucket_start >= 1738750016) AND (__table1.ts_bucket_start <= 1738838216)) GROUP BY __table2.traceID, __table2.durationNano, __table2.name, __table2.serviceName ORDER BY __table2.durationNano DESC LIMIT _CAST(1, 'UInt64') BY __table2.traceID LIMIT _CAST(10, 'UInt64')",
  "stacktrace": "<http://go.signoz.io/signoz/pkg/query-service/app/clickhouseReader.(*ClickHouseReader).GetListResultV3|go.signoz.io/signoz/pkg/query-service/app/clickhouseReader.(*ClickHouseReader).GetListResultV3>\n\t/home/runner/work/signoz/signoz/pkg/query-service/app/clickhouseReader/reader.go:4517\ngo.signoz.io/signoz/pkg/query-service/app/querier.(*querier).runBuilderListQueries.func1\n\t/home/runner/work/signoz/signoz/pkg/query-service/app/querier/querier.go:489"
}
v
@Ekansh Gupta can you please help here
a
@Ekansh Gupta, @nitya-signoz please help me to resolve this issue
@nitya-signoz if I modify query like below then issue will resolved. please check it once SELECT __table2.serviceName AS
subQuery.serviceName
, __table2.name AS
subQuery.name
, *count*() AS _span_count_, __table2.durationNano AS
subQuery.durationNano
, __table2.traceID AS _trace_id_ FROM signoz_traces.signoz_index_v3 AS __table1 ALL INNER JOIN (SELECT __table3.traceID AS traceID, __table3.durationNano AS durationNano, __table3.serviceName AS serviceName, __table3.name AS name FROM (SELECT __table4.trace_id AS traceID, __table4.duration_nano AS durationNano, __table4.
resource_string_service$$name
AS serviceName, __table4.name AS name FROM signoz_traces.signoz_index_v3 AS __table4 WHERE ((__table4.parent_span_id AS parentSpanID) = '') AND ((__table4.timestamp >= '1738751816000000000') AND (__table4.timestamp <= '1738838216000000000')) AND ((__table4.ts_bucket_start >= 1738750016) AND (__table4.ts_bucket_start <= 1738838216)) ORDER BY durationNano DESC LIMIT _CAST(1, 'UInt64') BY traceID) AS __table3) AS __table2 ON (__table1.trace_id AS traceID) = __table2.traceID WHERE ((__table1.timestamp >= '1738751816000000000') AND (__table1.timestamp <= '1738838216000000000')) AND ((__table1.ts_bucket_start >= 1738750016) AND (__table1.ts_bucket_start <= 1738838216)) GROUP BY __table2.traceID, __table2.durationNano, __table2.name, __table2.serviceName ORDER BY __table2.durationNano DESC LIMIT _CAST(1, 'UInt64') BY __table2.traceID LIMIT _CAST(10, 'UInt64')
e
Ack
a
@Ekansh Gupta once it is fixed, please share the hotfix or provide the tag version so i will deploy the same.
e
@Alok Singh What is the tag that you're using currently?
a
@Ekansh Gupta I am using the latest one v0.72.0
e
Although I understand the problem in the query due to which you're getting the error, but I dont understand why this query is conflicting. I have tried to replicate this as well. Can you share me a video, if possible,
a
Sure, I’ll create a video and share it with you
@Ekansh Gupta please watch in following order: 1. signoz_dashboard 2. query-service_logs 3. dbeaver clickhouse-client
e
If you see the second log line, thats the query we are using for the particular tab. Lets set up a call if possible for me to understand why the issue is coming. You can help me replicate this issue as well.
a
Any tentative time so I will schedule a call with you
m
I still have this exact problem in the latest version, 0.79.1
e
Hi @Ming Fang we had concluded this issue by highlighting the fact that while upgrading you also need to run the sync and async migration scripts. I would request you to check the same and get back to me
m
I'm seeing this issue on a completely fresh install and after sync and async migrations are run to completion.