Open ngreve opened 5 months ago
Commit: cdc7893481aa10d51070d965ae9fc6eebfe91ac2
When starting a build node with, it can does not fully get closed when issuing Ctrl-C in the terminal.
Ctrl-C
Start a build node and try to cancel the execution using Ctrl-C:
./flesnet -n 15 -t zeromq -I shm://127.0.0.1/0 -o 0 -O shm:/fles_out_shared_memory/0 --processor-instances 1 -e "./tsclient -i shm:%s -o file:timeslice_archive.tsa" [11:40:41] INFO: this is output 0 (of 1) [11:40:41] INFO: timeslice buffer 0: fles_out_shared_memory {bd603892-8d48-4d22-a6f0-e95d40efe499}, size: 1 * (128 MiB + 16 MiB) = 144 MiB [11:40:41] INFO: [c0] |____________________|__________| [11:40:41] INFO: worker connected: TimesliceAutoSource at PID 33222 (s1/o0/p0/g0) ^C[11:40:44] ERROR: ZMQ: Interrupted system call [11:40:44] INFO: total timeslices processed: 0 [11:40:44] INFO: worker disconnected: TimesliceAutoSource at PID 33222 (s1/o0/p0/g0) [11:40:44] INFO: exiting [11:40:44] INFO: [c0] |____________________|__________|
The output shows [11:40:44] INFO: exiting but the process does not get killed and is stuck there. You have to use htop or pkill to kill the process.
[11:40:44] INFO: exiting
htop
pkill
The process should get killed.
Commit: cdc7893481aa10d51070d965ae9fc6eebfe91ac2
Problem Description
When starting a build node with, it can does not fully get closed when issuing
Ctrl-C
in the terminal.Steps to Reproduce
Start a build node and try to cancel the execution using
Ctrl-C
:The output shows
[11:40:44] INFO: exiting
but the process does not get killed and is stuck there. You have to usehtop
orpkill
to kill the process.Expected Behavior
The process should get killed.