fly.toml kill_signal and kill_timeout

Questions / Help
1

Hi! I’ve set

kill_signal = ‘SIGTERM’
kill_timeout = 30

in Fly.toml – in my logs I’m seeing

  • [info] INFO Sending signal SIGINT to main child process w/ PID 323
    …30 seconds
  • [info] INFO Sending signal SIGTERM to main child process w/ PID 323
  • [warn] Virtual machine exited abruptly

(I am trapping SIGTERM in my execution script and I guess that the actions there have not had enough time to land)

The behaviour I would have expected is

  • no SIGNT
  • SIGTERM
  • 30 seconds
  • SIGKILL

am i missing something?

2 Likes
Fly.toml configuration does not set kill_signal
2

I also have this issue. I need to send out a signal to my orchestration cluster before I shut down the node, i.e. on SIGTERM, but this does not seem to work as documented/intended.

3

To maybe help me narrow down what could be happening here, are you both using the proxy to auto stop the machines? Or are you using the CLI/API directly to stop them?

4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.