gargoyle doesn't die sometimes when it inherits TCP sockets

[danbornside]

gargoyle doesn't die sometimes when it inherits TCP sockets

[mikereinhart]

I believe I also observed this. I killed https://gitlab.com/obsidian.systems/tezos-bake-monitor using Control+C, but gargoyle-nix-postres was left behind. Attempting to restart Kiln failed due to the left behind gargoyle process. Manually killing gargoyle allowed me to successfully start Kiln

[3noch]

We also saw a bewildering issue where HTTP requests from Kiln timed out until we killed the lingering gargoyle+postgres.

[ryantrinkle]

@danharaj Any thoughts on this?

[ghost]

No, I'd need to regain my bearings on this code in order to diagnose. Does anyone have a way to reliably reproduce this. Do @mikereinhart 's steps always work?

[mikereinhart]

In my experiences they do not always work. The issue is intermittent

[3noch]

@danbornside told me that he has seen this issue when starting gargoyle postgres after binding a port (such that it gets inherited). I have not confirmed that this is a reliable way to reproduce.