-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
task restart No response #20406
Comments
Service registration provider defaults to |
The following is the configuration of the service template, daprd task restart operation is ok, only when not set provider app task restart no response
|
Hi @chenjpu! Apologies for the delay in responding to this. Let me verify I understand what you're saying here:
Is that right? I would not have expected the workload to run at all with |
|
Hi @chenjpu! I think what I'm not making clear is that if you had jobspecjob "example" {
group "group" {
network {
mode = "bridge"
port "www" {
to = 8001
}
}
service {
name = "httpd-web"
provider = ""
port = "www"
}
task "task" {
driver = "docker"
config {
image = "busybox:1"
command = "httpd"
args = ["-vv", "-f", "-p", "8001", "-h", "/local"]
}
resources {
cpu = 50
memory = 50
}
}
}
} I get a scheduling error like the following:
However, I suspect the We emit the "User requested task to restart" event just before we actually try to restart the task (ref So there might be something that's blocking the shutdown here. Next steps to debug:
|
Hi @tgross |
@chenjpu ok I understand. If this happens again, you can capture the logs of the running client with: |
OK, I am happy to help with this problem |
Doing a little issue cleanup. Going to close this out as unable to reproduce. |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
1.7.6 or main branch
Operating system and Environment details
CentOS Linux release 7.9.2009 (Core)
Docker Engine - 24.0.1
Issue
Multiple attempts to restart the task showed no response
Reproduction steps
Expected Result
Actual Result
Job file (if appropriate)
Nomad Server logs (if appropriate)
Nomad Client logs (if appropriate)
The text was updated successfully, but these errors were encountered: