https://signoz.io logo
Join Slack
Powered by
This message was deleted.
# support
s
This message was deleted.
s
What is the earlier version and what version are you upgrading to? What is your environment, the more detail you share the better it is to help debugging.
m
k8s, helm version 0.14.1 to 0.14.2 is what I am upgrading to
Thank you @Srikanth Chekuri for getting back
And eks is the kube environment
is there a version that accepts 36 arguments for tracing that I can roll back to?
f its any help its trying to write to the index table
Could not write a batch of spans to index table
s
No, there was no change from 
0.14.1
to 
0.14.2
. What is your collector version?
m
one se
one sec
'0.66.6'
s
How did you upgrade? It shouldn’t be 
0.66.6
m
here is the helm install output helm upgrade -n signoz signoz signoz/signoz 
coalesce.go:175: warning: skipped value for zookeeper.initContainers: Not a table.
Release "signoz" has been upgraded. Happy Helming!
NAME: signoz
LAST DEPLOYED: Fri Apr 28 09:01:09 2023
NAMESPACE: signoz
STATUS: deployed
REVISION: 36
NOTES:
1. You have just deployed SigNoz cluster:
- frontend version: '0.17.0'
- query-service version: '0.17.0'
- alertmanager version: '0.23.0-0.2'
- otel-collector version: '0.66.6'
- otel-collector-metrics version: '0.66.6'
2. Get the application URL by running these commands:
export POD_NAME=$(kubectl get pods --namespace signoz -l "<http://app.kubernetes.io/name=signoz,app.kubernetes.io/instance=signoz,app.kubernetes.io/component=frontend|app.kubernetes.io/name=signoz,app.kubernetes.io/instance=signoz,app.kubernetes.io/component=frontend>" -o jsonpath="{.items[0].metadata.name}")
echo "Visit <http://127.0.0.1:3301> to use your application"
kubectl --namespace signoz port-forward $POD_NAME 3301:3301
If you have any ideas, questions, or any feedback, please share on our Github Discussions:
<https://github.com/SigNoz/signoz/discussions/713>
s
This is signoz charts 
0.12.1
version, but you mentioned you are upgrading from 
0.14.1
to 
0.14.2
.
m
my bad, I assumed it will automatically upgrade to the latest version. Should I helm install 0.14.2 ? There is a change my previous version was way down that supported 35 arguments, I remember using -reuse-values while changing the logging level of clickhouse from information to warning
Apologies for how vaguely I am describing things here
very new to the whole ecosystem, including k8s and helm
s
pull the new releases and then upgrade
m
Sure thanks a mil
will report back
even after pulling and installing the collector version is still '0.66.6'
one more issue on the side note is that one of the clickhouse cluster init containers keep giving this error out and never lets the cluster to start /bin/sh: curl: not found /bin/sh: curl: not found /bin/sh: curl: not found
this can be fixed by getting rid of the damanged init container from the stateful set, fyi
Im facing the same error again Could not write a batch of spans {"kind": "exporter", "data_type": "traces", "name": "clickhousetraces", "error": "clickhouse [Append]: clickhouse: expected 36 arguments, got 35"}
What version of otel collector is supposed to come with chart version 0.14.2 ?
s
What version of otel collector is supposed to come with chart version 0.14.2 ?
0.66.7
m
Thank you
12 Views
Open in Slack
PreviousNext
Powered by