Main child exited normally with code: 0

Questions / Help
1

Does anyone know how to fix this? I have a Dockerfile that starts a websocket client on the last CMD.

2

Hmm, this is a bit vague. Is there more information and/or logs you can provide? Off the top of my head, maybe the WebSocket client occasionally raises an exception, causing an exit? Do you have any error handling built in to handle exceptions and reconnections if necessary?

3

Here is more of the log. I really don’t understand why it’s sig terming. I assume it’s because I have no endpoint for health check (not an HTTP server), so I thought it might be my fly.toml config.



2023-10-17T07:58:59.004 app[e286009c7d3e86] nrt [info] INFO Main child exited normally with code: 0

2023-10-17T07:58:59.005 app[e286009c7d3e86] nrt [info] INFO Starting clean up.

2023-10-17T07:58:59.005 app[e286009c7d3e86] nrt [info] WARN hallpass exited, pid: 315, status: signal: 15 (SIGTERM)

Here’s my config based on some other relevant posts and solutions in the forum:

I am sure I made a mistake somewhere. I just can’t figure out what’s causing it.

[build]

[[services]]
  internal_port = 8080
  protocol = "tcp"
  auto_stop_machines = true
  auto_start_machines = true
  min_machines_running = 1
4

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