This message was deleted.
# troubleshootings
Slackbot
05/09/2023, 3:33 AMThis message was deleted.
a
Abhishek Agarwal
05/09/2023, 5:21 AMit likely means that overlord shutdown the task. you should check the overlord logs to see why it shut down that task
u
Udit Sharma
05/09/2023, 5:39 AMThanks @Abhishek Agarwal !!
Udit Sharma
05/09/2023, 7:55 AMchecked that, overlord failed to check the status of task and decided to shut it down.
Udit Sharma
05/09/2023, 7:58 AMBut interesting part was why the task was failing to respond. something happened on the gcp node where the mm was running. i see some GCP node logs like this. Any one familiar with this ? @Abhishek Agarwal Have you seen something like this ?
Copy code
task jbd2/sdb-8:1565 blocked for more than 327 secondsa
Abhishek Agarwal
05/09/2023, 8:28 AMno idea
Abhishek Agarwal
05/09/2023, 8:31 AMwe should probably change that message from "Triggering JVM shutdown" to "Triggering JVM shutdown. Check overlord logs to see why the task was shutdown"
s
Sergio Ferragut
05/09/2023, 5:00 PMDoes the overlord log have more detail on why it couldn't communicate with the task? Was it just unable to connect or did it timeout waiting for the communication?
u
Udit Sharma
05/10/2023, 9:42 AMrequest were timed out, something went wrong on the node, that is all i could figure out, as moving to different resolved the issue.
Udit Sharma
05/10/2023, 9:42 AMtask/status api failed to respond.
3 Views