Question / Help OBS disconnects randomly, then reconnects 15s later. Is this on my end? (Logs provided)

K

Kylix

Member
Hello! I stream on Mixer and sometimes my stream will randomly go offline and come right back on about 15s later with no discernible triggers. (OBS shows a disconnected/reconnecting notification in Windows)

When this happens, I lose any hosts I might have, it splits my VODs in half and makes a huge mess of things in general. Very frustrating. I'm trying to figure out if this is a Mixer (FTL) issue or something on my end.

I've been using roughly the same settings for years and this issue just started becoming frequent in the last month or two. It's happened about 3 times in the last month specifically.

I will provide the part of the log here that I believe is relevant (though I'm not sure) and then the full log below from the last time it happened. Thanks for any insight you can provide. I've tried a lot of fixes and nothing seems to help, which makes me think this is a Mixer server issue.

Code: 
    21:19:34.008: Avg packet send per second 370.3, total nack requests 11
    21:19:34.008: avg transmit delay 0ms (min: 0, max: 4), avg rtt 33ms (min: 32, max: 45)
    21:19:39.025: Avg packet send per second 370.3, total nack requests 11
    21:19:39.025: avg transmit delay 0ms (min: 0, max: 1), avg rtt 33ms (min: 32, max: 60)
    21:19:44.025: Avg packet send per second 370.3, total nack requests 11
    21:19:44.025: avg transmit delay 0ms (min: 0, max: 1), avg rtt 33ms (min: 32, max: 63)
    21:19:45.733: [ftl stream: 'adv_stream'] ftl_stream_stop
    21:19:45.737: [ftl stream: 'adv_stream'] Stream shutdown timeout reached (0 second(s))
    21:19:45.737: [ftl stream: 'adv_stream'] User stopped the stream
    21:19:45.737: Output 'adv_stream': stopping
    21:19:45.737: Output 'adv_stream': Total frames output: 1782835 (1782837 attempted)
    21:19:45.737: Output 'adv_stream': Total drawn frames: 1782412 (1782949 attempted)
    21:19:45.737: Output 'adv_stream': Number of lagged frames due to rendering lag/stalls: 537 (0.0%)
    21:19:45.737: Output 'adv_stream': Number of dropped frames due to insufficient bandwidth/connection stalls: 2 (0.0%)
    21:19:45.737: [ftl stream: 'adv_stream'] ingest disconnect
    21:19:45.738: [3] Exited Ping Thread
    21:19:45.738:
    21:19:45.738: Video stopped, number of skipped frames due to encoding lag: 549/1782860 (0.0%)
    21:19:45.739: [3] Exited Send Thread
    21:19:45.739:
    21:19:45.739: [3] Exited Audio Send Thread
    21:19:45.739:
    21:19:45.766: [3] Exited Recv Thread
    21:19:45.766:
    21:19:45.767: [3] Exited control_keepalive_thread
    21:19:45.767:
    21:19:45.768: [3] Exited connection_status_thread
    21:19:45.768: [3] light-saber disconnect
    21:19:45.768:
    21:19:45.768: [ftl stream: 'adv_stream'] Freeing 2 remaining packets21:19:45.768:
    [ftl stream: 'adv_stream'] Disconnected from ingest with reason: ftl ingest disconnect api was called
    21:19:45.773: warning: 1 frames left in the queue on closing

Full log (with some repeating data omitted due to Pastebin space restrictions)
pastebin.com

OBS Log - Pastebin.com

pastebin.com pastebin.com
 
K

Kylix

Member
R1CH said:
Turn off your output timers (tools menu)
Click to expand...

I checked out the setting you mentioned and nothing there is checked and everything says 0. I guess I should also mention that I've literally never touched this tool before in my 3 year history of using OBS Studio and that these stream disconnects have happened 1h 42m into me streaming, another time was 1h 7m into my stream and I can't remember the 3rd time, but it's always different. And when it happens, they have been several streams apart. Like, I've been able to complete full 8-10h streams with no issues, so an output timer that's never been touched being the culprit doesn't really make sense.

Also, when the stream successfully reconnects after 10s, I am able to continue streaming for several more hours with no additional disconnects. For example, the last stream DC'd after 1h 42m, reconnected and then I went on for the next 8 hours with no issues without me laying a finger on OBS that entire time.

Here's a screen capture of my output timer settings for reference: https://i.imgur.com/K48g4ga.png
 
R

R1CH

Forum Admin
Developer
My mistake, I thought that was the output timer but it's something else. OBS usually logs when a stream is stopped, in this case

21:19:45.737: [ftl stream: 'adv_stream'] User stopped the stream

Seems to imply you are stopping the stream manually as no other reason is logged. Perhaps try using RTMP as maybe the FTL output code has a bug.
 
K

Kylix

Member
R1CH said:
My mistake, I thought that was the output timer but it's something else. OBS usually logs when a stream is stopped, in this case

21:19:45.737: [ftl stream: 'adv_stream'] User stopped the stream

Seems to imply you are stopping the stream manually as no other reason is logged. Perhaps try using RTMP as maybe the FTL output code has a bug.
Click to expand...

I'm trying at all costs to avoid the RTMP service because my stream/content hinges on the sub-second delay that FTL provides for how my interactions and StreamLoots stuff works. (That's why I opted to use Mixer over Twitch actually.)

Let me reiterate that I might have inserted the wrong part of the log there which is why I included the full version at the bottom. I'm not very well versed in where to look for the errors.

So does this extra context help maybe? When the DC happens, OBS never seems to stop. By that, I mean when I look over at OBS during the disconnection, the "LIVE" timer at the bottom keeps rolling as if the stream never stopped broadcasting. So once the stream is truly over, I obviously end it manually at that point, which might be showing up in my log there? Idk. Is there somewhere else in the log to look for a disconnection/re-connection event?

I'm just trying to understand if this is an OBS issue, a Mixer server issue, or maybe even an ISP issue. (I have AT&T 1000/1000 speed with good hardware, so I doubt that's it, but who knows.)

Thanks for all the help and sorry for all the trouble.
 
You must log in or register to reply here.
Top