This message was deleted.
# supports
Slackbot
09/06/2023, 9:41 AMThis message was deleted.
✅ 1
s
Srikanth Chekuri
09/06/2023, 10:42 AMAre there no other logs?
j
Juan Ramino
09/06/2023, 12:26 PMno, how can i increase verbosity of logs?
Juan Ramino
09/06/2023, 12:36 PMSome magic solved it, because after few hours containers stop restarting and finally runs fine.
Thanks @Srikanth Chekuri
Juan Ramino
09/06/2023, 1:51 PMBut... this happen again after an update of the release.
Same situation, container exit with code 2 after displaying that log (without errors).
s
Srikanth Chekuri
09/06/2023, 1:53 PMThe logs are already verbose. What is the environment you see this happen? What does the pod describe show?
j
Juan Ramino
09/06/2023, 2:12 PMwe 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
Srikanth Chekuri
09/06/2023, 2:13 PMCan you confirm is ClickHouse is running?
j
Juan Ramino
09/06/2023, 2:14 PMyes, is running, also the initContainer exit successfully
Juan Ramino
09/06/2023, 2:20 PMafter 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
Prashant Shahi
09/06/2023, 4:13 PMPrashant Shahi
09/06/2023, 6:57 PMResolved by https://github.com/SigNoz/charts/pull/284
j
Juan Ramino
09/07/2023, 7:25 AMgood! thanks
4 Views