https://signoz.io logo
Join Slack
Channels
contributing
contributing-frontend
general
github-activities
incidents
k8s_operator_helm
reactjs-config
signoz-alert-testing
support
testsupport
watercooler
webhook-dev
write-for-signoz
Powered by Linen
Title
a

Ashna

11/02/2022, 11:14 AM
2022/11/02 10:21:24 collector server run finished with error: failed to get config: cannot unmarshal the configuration: unknown exporters type "clickhouselogsexporter" for "clickhouselogsexporter" (valid values: [awsemf clickhouse honeycomb newrelic opencensus prometheusremotewrite skywalking sumologic alibabacloud_logservice file splunk_hec awsprometheusremotewrite awsxray f5cloud jaeger logging prometheus signalfx awskinesis elasticsearch googlecloud kafka logzio sapm zipkin carbon humio loki stackdriver tencentcloud_logservice azuremonitor clickhousemetricswrite datadog dynatrace elastic jaeger_thrift loadbalancing otlp otlphttp parquet influxdb sentry tanzuobservability])
s

Srikanth Chekuri

11/02/2022, 11:31 AM
What version are trying to upgrade from and which version is giving this error?
p

Prashant Shahi

11/02/2022, 11:40 AM
@Ashna From the above logs, it's likely that you are trying to downgrade SigNoz using OtelCollector config of latest release.
a

Ashna

11/02/2022, 12:04 PM
Hi,Please find the below versions I am using signoz/frontend:0.9.0 signoz/query-service:0.9.0 signoz/otelcontribcol:0.43.0-0.1 clickhouse/clickhouse-server:22.4-alpine
p

Prashant Shahi

11/02/2022, 12:06 PM
If you are using older version, you should use older Chart version (or git checkout to release tag/branch) as well.
You are using older version of OtelCollector, while the configuration is pointed to the latest changes.
Compare your 
values.yaml
with the one here: https://github.com/SigNoz/charts/blob/main/charts/signoz/values.yaml
a

Ashna

11/02/2022, 12:09 PM
While Trying to upgrade with old volumes its not reflecting in the latest version
p

Prashant Shahi

11/02/2022, 12:14 PM
can you share how are you upgrading?
a

Ashna

11/02/2022, 12:24 PM
upgrade from 0.7.1 to 0.11.1
p

Prashant Shahi

11/02/2022, 12:52 PM
you would have to incrementally upgrade across the versions with breaking changes and run the migration scripts
https://signoz.io/docs/operate/migration
a

Ashna

11/02/2022, 1:24 PM
Hi , I tried to upgrade to 0.8.0 from 0.7.2 and changed to these below values Alertmanager 0.23.0-0.1, OtelCollector 0.43.0-0.1
Still I am getting the same error
p

Prashant Shahi

11/02/2022, 3:39 PM
The Helm chart and the OtelCollector configuration you are using is for v0.11.x while you are using SigNoz version v0.9.x
you would have to incrementally point to specific chart versions with signoz versions and run the migration scripts.
It would be much easier to clean up existing signoz cluster and install latest one.
a

Ashna

11/03/2022, 6:21 AM
Okay
But how will I get the old data?
p

Prashant Shahi

11/03/2022, 6:29 AM
old data can only be retained if you follow the step-by-step upgradation and run migration script
a

Ashna

11/03/2022, 7:24 AM
By while doing step by step migration I am getting the error that I shared yestrday
p

Prashant Shahi

11/03/2022, 7:27 AM
I don't think you are pointing 
helm
to correct chart versions.
Run the following to get list of various chart versions and note the signoz version next to it. 
helm search repo signoz --versions
you will need to pass 
--version
flag to set specific chart version for each breaking change release for your 
helm upgrade
commands.
a

Ashna

11/03/2022, 10:09 AM
Hi,
We are deploying using docker
p

Prashant Shahi

11/04/2022, 2:55 AM
Oh, I see. That means you would have to 
git checkout
to release branch or tag of each breaking changes incrementally and also run the migration scripts.
Migration scripts: https://signoz.io/docs/operate/migration Upgrade guide: https://signoz.io/docs/operate/docker-standalone/#upgrade
a

Ashna

11/11/2022, 8:24 AM
Hi
While tring to migrate as per the above docs, getting the below error
Error: unknown flag: --mem-ballast-size-mib 2022/11/11 08:14:56 collector server run finished with error: unknown flag: --mem-ballast-size-mib
p

Prashant Shahi

11/11/2022, 11:36 AM
That flag was removed long back.
I don't think you are migrating properly
You would have to checkout to 
v0.8.0
: 
git checkout v0.8.0
And follow the migration guide here: https://signoz.io/docs/operate/migration/upgrade-0.8.0/ Similarly, you would have to checkout to: • 
0.8.1
and follow migration scrips here: https://signoz.io/docs/operate/migration/upgrade-0.8.1/ • 
0.9.0
and follow migration scrips here: https://signoz.io/docs/operate/migration/upgrade-0.9/ • 
0.10.0
and follow migration scrips here: https://signoz.io/docs/operate/migration/upgrade-0.10/
a

Ashna

11/11/2022, 12:05 PM
I was following the same steps that you have mentioned in the document
p

Prashant Shahi

11/11/2022, 12:12 PM
can you please make sure that you do not have any local changes in the otel-collector config or docker-compose YAML?
a

Ashna

03/23/2023, 8:32 AM
hi
p

Prashant Shahi

03/23/2023, 8:35 AM
Hi @Ashna 👋 How can I help you?
a

Ashna

03/23/2023, 8:57 AM
While connecting to grpc using nginx we are getting the below error. Please have a check. [error] 30#30: *1 upstream rejected request with error 1 while reading response header from upstream, client: , server: , request: "GET /favicon.ico HTTP/1.1", u
View count: 37
Back to #supportJoin thread in Slack