https://signoz.io logo
Join Slack
Powered by
Hello, I have a problem with the helm installatio...
# support
j
Hello, I have a problem with the helm installation, query-service won't start. It just prints this log and then exit with code 2. Container image used is query-service:0.28.0. Do you have any tips? Thanks
Copy code
2023-09-06T09:39:47.396Z	INFO	version/version.go:43	

SigNoz version   : v0.28.0
Commit SHA-1     : b2a9437
Commit timestamp : 2023-09-01T10:42:25Z
Branch           : HEAD
Go version       : go1.21.0

For SigNoz Official Documentation,  visit <https://signoz.io/docs>
For SigNoz Community Slack,         visit <http://signoz.io/slack>
For discussions about SigNoz,       visit <https://community.signoz.io>

Check SigNoz Github repo for license details.
Copyright 2022 SigNoz


2023-09-06T09:39:47.396Z	WARN	query-service/main.go:130	No JWT secret key is specified.
s
Are there no other logs?
j
no, how can i increase verbosity of logs?
Some magic solved it, because after few hours containers stop restarting and finally runs fine. Thanks @Srikanth Chekuri
But... this happen again after an update of the release. Same situation, container exit with code 2 after displaying that log (without errors).
s
The logs are already verbose. What is the environment you see this happen? What does the pod describe show?
j
we are running signoz inside a k8s cluster version at v1.26.6 Describe just show that liveness and readiness are failing for a connection refused error.
s
Can you confirm is ClickHouse is running?
j
yes, is running, also the initContainer exit successfully
after removing liveness and readiness probes the container start and stay up printing more logs. It seems probes are too quick and doesn't let it starts correctly
p
j
good! thanks
2 Views
Open in Slack
PreviousNext
Powered by