https://signoz.io
Join Slack
Menu
Home
Archive
This message was deleted.
# support
s
This message was deleted.
s
What version are trying to upgrade from and which version is giving this error?
p
@Ashna From the above logs, it's likely that you are trying to downgrade SigNoz using OtelCollector config of latest release.
a
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
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.
a
While Trying to upgrade with old volumes its not reflecting in the latest version
p
can you share how are you upgrading?
a
upgrade from 0.7.1 to 0.11.1
p
you would have to incrementally upgrade across the versions with breaking changes and run the migration scripts
a
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
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
Okay
But how will I get the old data?
p
old data can only be retained if you follow the step-by-step upgradation and run migration script
a
By while doing step by step migration I am getting the error that I shared yestrday
p
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.
Copy code
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
Hi,
We are deploying using docker
p
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.
a
Hi
While tring to migrate as per the above docs, getting the below error
Error: unknown flag: --mem-ballast-size-mib 2022/11/11 081456 collector server run finished with error: unknown flag: --mem-ballast-size-mib
p
That flag was removed long back.
I don't think you are migrating properly
You would have to checkout to 
v0.8.0
:
Copy code
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
I was following the same steps that you have mentioned in the document
p
can you please make sure that you do not have any local changes in the otel-collector config or docker-compose YAML?
a
hi
p
Hi @Ashna 👋 How can I help you?
a
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
257 Views
Open in Slack
PreviousNext
Powered by

SigNoz Community

SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.

Powered by