Question / Help Explain some logs

Red_Orchestra

New Member
Hello. Can someone explain log's part 4 me?

I have some random disconnects from servers and try to understand why

12:37:15: RTMPPublisher::SocketLoop: Received FD_CLOSE, 5854 ms since last send (buffer: 269777 / 272384)
12:37:15: RTMPPublisher::SocketLoop: Aborting due to FD_CLOSE, error 0
12:37:15: FlushBufferedVideo: Flushing 24 packets over 767 ms
12:37:16: Total frames encoded: 15774, total frames duplicated: 19 (0.12%)
12:37:16: Total frames rendered: 15765, number of late frames: 2 (0.01%) (it's okay for some frames to be late)
12:37:16: ~RTMPPublisher: Packet flush completed in 129 ms
12:37:16: ~RTMPPublisher: Send thread terminated in 3 ms
12:37:16: ~RTMPPublisher: Socket thread terminated in 0 ms
12:37:16: Average send payload: 5651 bytes, average send interval: 21 ms
12:37:16: Number of times waited to send: 2, Waited for a total of 8208 bytes
12:37:16: Number of b-frames dropped: 0 (0%), Number of p-frames dropped: 0 (0%), Total 0 (0%)
12:37:16: Number of bytes sent: 137970895
12:37:16: Encoder closed
12:37:16: NVENC deinitialized
 

dping

Active Member
Hello. Can someone explain log's part 4 me?

I have some random disconnects from servers and try to understand why

12:37:15: RTMPPublisher::SocketLoop: Received FD_CLOSE, 5854 ms since last send (buffer: 269777 / 272384)
12:37:15: RTMPPublisher::SocketLoop: Aborting due to FD_CLOSE, error 0
12:37:15: FlushBufferedVideo: Flushing 24 packets over 767 ms
12:37:16: Total frames encoded: 15774, total frames duplicated: 19 (0.12%)
12:37:16: Total frames rendered: 15765, number of late frames: 2 (0.01%) (it's okay for some frames to be late)
12:37:16: ~RTMPPublisher: Packet flush completed in 129 ms
12:37:16: ~RTMPPublisher: Send thread terminated in 3 ms
12:37:16: ~RTMPPublisher: Socket thread terminated in 0 ms
12:37:16: Average send payload: 5651 bytes, average send interval: 21 ms
12:37:16: Number of times waited to send: 2, Waited for a total of 8208 bytes
12:37:16: Number of b-frames dropped: 0 (0%), Number of p-frames dropped: 0 (0%), Total 0 (0%)
12:37:16: Number of bytes sent: 137970895
12:37:16: Encoder closed
12:37:16: NVENC deinitialized
FD_CLOSE is a winsocket error basically saying the connection closed. usually error 0 is something when you suddently press the stop button or the connection is lost.

I've seen it to where a 3rd party firewall or antimalware program will close the OBS connection as it sees a lot of data going out. This is more of a false positive for the firewall but it happens. Most of the time this is shown as an FD_CLOSE error 10053

please post a link to your full log like this:
giphy.gif
 

Red_Orchestra

New Member
FD_CLOSE is a winsocket error basically saying the connection closed. usually error 0 is something when you suddently press the stop button or the connection is lost.

I've seen it to where a 3rd party firewall or antimalware program will close the OBS connection as it sees a lot of data going out. This is more of a false positive for the firewall but it happens. Most of the time this is shown as an FD_CLOSE error 10053

please post a link to your full log like this:
giphy.gif
Thank you for reply. Here's log https://gist.github.com/a672eba89ac36b7a1837

What may cause this kind of problem? Is it a provider problem, or my own?
 
Top