You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While chaos-monkey-testing captive-core in the remote http configuration I killed the core child process to simulate a crash.
Instead of respawning the core process, the captive core http server:
Panicked due to the channel double-close (See backlog at the end of the description)
Got stuck, which is more worrisome. Instead of dying, the captive core server process lingered, not giving an opportunity to the supervisor (Kubernetes in this case) to re-spawn it:
root@horizon-with-remote-core-6bddf785b9-r9vlg:/# killall stellar-core
root@horizon-with-remote-core-6bddf785b9-r9vlg:/# ps aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 20.5 1.5 1539976 32040 ? Ssl 18:13 12:26 /captivecore --port=8080
root 7161 0.0 0.1 18504 3372 pts/0 Ss 19:11 0:00 bash
root 7220 0.0 0.1 34400 2792 pts/0 R+ 19:14 0:00 ps aux
root@horizon-with-remote-core-6bddf785b9-r9vlg:/# ps aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 18.6 1.3 1539976 28016 ? Ssl 18:13 12:27 /captivecore --port=8080
root 7161 0.0 0.1 18504 3372 pts/0 Ss 19:11 0:00 bash
root 7221 0.0 0.1 34400 2748 pts/0 R+ 19:20 0:00 ps aux
root@horizon-with-remote-core-6bddf785b9-r9vlg:/#
While chaos-monkey-testing captive-core in the remote http configuration I killed the core child process to simulate a crash.
Instead of respawning the core process, the captive core http server:
Panic log:
The text was updated successfully, but these errors were encountered: