With the new update, whenever a Streamer disconnects their client it sends the ingest into a spiral of logging, and does not allow the Streamer to reconnect under the same channel ID. I did not try another channel ID.
Here are the logs from an Ingest when a Streamer disconnects:
Feb 09 12:28:45 do-nyc3-ingest1.kjfk.live.glimesh.tv janus[689693]: [2021-02-09 12:28:45.761] [warning] Unknown ingest command: DISCONNECT
Feb 09 12:28:45 do-nyc3-ingest1.kjfk.live.glimesh.tv janus[689693]: [2021-02-09 12:28:45.767] [info] Unpublishing channel 3 / stream 264 from Orchestrator
Feb 09 12:28:45 do-nyc3-ingest1.kjfk.live.glimesh.tv janus[689693]: [2021-02-09 12:28:45.767] [info] Stopping relay for channel 3 / stream 264 -> do-nyc3-edge3.kjfk.live.glimesh.tv...
[...]
# Then this same message repeated thousands of times a second, very fast!
Feb 09 12:23:07 do-nyc3-ingest1.kjfk.live.glimesh.tv janus[689327]: [2021-02-09 12:23:07.168] [info] Stopping relay for channel 3 / stream 263 -> do-nyc3-edge3.kjfk.live.glimesh.tv...
With the new update, whenever a Streamer disconnects their client it sends the ingest into a spiral of logging, and does not allow the Streamer to reconnect under the same channel ID. I did not try another channel ID.
Here are the logs from an Ingest when a Streamer disconnects: