This message was deleted.
# troubleshootings
Slackbot
09/21/2022, 2:54 PMThis message was deleted.
t
Thomas
09/21/2022, 2:55 PMI’d like to take some time to fix it before rolling back to 0.23.0
g
Gian Merlino
09/21/2022, 2:59 PMHmm, those logs aren't super interesting, they just mean that we found your ZK servers (assuming they are correctly at
zk-eu-4zk-eu-6t
Thomas
09/21/2022, 3:00 PMYup…
g
Gian Merlino
09/21/2022, 3:00 PMboth 23 and 24 have the same ZK client version (3.5.9) and curator (4.3.0)
t
Thomas
09/21/2022, 3:00 PMIt bothers me, i have no clues what is happening
Thomas
09/21/2022, 3:00 PMWas working fine on 0.23.0
g
Gian Merlino
09/21/2022, 3:01 PMI guess it appears to be stuck now?
👍 1
Gian Merlino
09/21/2022, 3:01 PMCould you share some additional logs? I'm wondering what it was doing before it got stuck
Gian Merlino
09/21/2022, 3:01 PMIt would also be interesting to see a thread dump:
jstack -l <overlord pid>Gian Merlino
09/21/2022, 3:02 PMThose are generally interesting anytime something seems stuck
t
Thomas
09/21/2022, 3:15 PMhere are the starting logs
Thomas
09/21/2022, 3:20 PMAlso switched log level to DEBUG and didn’t see useful logs 😞
Thomas
09/21/2022, 4:34 PMIt was related to the log
Thomas
09/21/2022, 4:39 PMI had a custom log4j configuration
Thomas
09/21/2022, 4:39 PMAnd the overlord (only the overlord, other processes were fine) complained about it. Once I’ve switched to https://raw.githubusercontent.com/FrankChen021/druid/7fe19499dce9b0e5cfe34de71620b1a9fd5bdeb7/examples/conf/druid/cluster/_common/log4j2.xml, Overlord started and is running fine
g
Gian Merlino
09/22/2022, 1:47 AMah, okay, good to know!
t
Thomas
09/22/2022, 12:41 PMThanks for helping me Gian 🙃
🙌 1