PC looses entire internet connection while streaming every ~~ 3 hrs

Tinteex

New Member
Hello.

Im running a 2 PC setup and send over the Video, Audio & Microphone to the Streaming PC over NDI.

Both PC are connected via a LAN-SWITCH (1gbit) .

When i am streaming, around every 3 hrs OBS will lose the total lan & internet connection & even "mouse without borders" or "remote desktop" will stop working.

if i use another port on the lan switch, the internet is back instantly and obs manages to reconnect until it happens again a few hours later.

i attached the logs here :

 

R1CH

Forum Admin
Developer
Sounds like an issue with your router or switch if all other applications also lose network access. Check event viewer logs for anything around the time it happens.
 

Tinteex

New Member
The weird thing is, it only affects the Streaming pc. all other devices do not have any problems, nor do they slow down (phones, tablets, other pcs, homeserver)

this pc new new installed with windows 10, the windows 10 license is not activated yet. could this contribute to the issue?
 

Xsoulsin

Member
It does sound like possible Modem/Router or Switch that might be using. You could try different cable, Ethernet Port on Modem/Router. I would make sure that Network Drivers are up to date. Also under Network Properties to make sure no power management is checked just incase. I would advise if you using any form VPN that could be dropping connection or if you have any Security Software. Sounds like more of a settings on computer side than OBS. With not been activated that should not affect it, as only for certain features and watermark. Just few things wanted to toss just incase you not checked into that. Outside of that I am not sure.
 

dmemphis

Member
I don't think its OBS and I don't think its your PC.
I used to experience something like uploading files to imgur.
If I cued a bunch of files up, that action would "lock up" the internet connection pretty
surely. Sometimes internet in general would just stop.
I discovered that if I cycled the power on my 4 port switch ahead of my wireless router,
it would start going again.
It has occurred to me responding to this that I have not had that little router
"lock up" since I moved, and I have it on a different brand wifi router and am on
Comcast in NJ rather that Penn Tele Data in Pennsylvania.
Definitely try other network gear before you spend a lot of time looking into the PC.
The fact your PC's connection locking up vs your other device could be the streaming protocol whacking something. That's unique to your PC's network use. Might also be the uniquely
heavl uploading.
 

Lawrence_SoCal

Active Member
Unfortunately. dmemphis's description of a solution was more than likely a coincidence than an understanding of how compute networking functions. In this case 'locked up' simply meant overwhelmed/bottlenecking. Simple network traffic monitoring (on the router, the switch, or the streaming PC) would most likely have shown that. rebooting switch was most likely unnecessary/overkill (akin to using a hand grenade instead of a fly-swatter). All that needed to be done is stop overwhelming the upload bandwidth. rebooting the switch interrupted the upload from the streaming PC. One could accomplish the same by unplugging Ethernet (or Airplane mode if WiFi connected, which of course should NOT be done when live-streaming). Either that or it was a cheap, defective Ethernet switch (something like TP-link or similar)

When you switch ports you are forcing everything on your PC to stop sending. That clearly is resolving whatever the issue is temporarily (effectively forcing a network re-connection/reset including at App level). I notice you have the StreamElements plug-in, and I can't even count how many trouble systems also run that. That plug-in pukes all over the OBS log, which indicates a lack of professionalism and quality on the part of the StreamElements and their programmers [yes, a professional opinion]. So... my first recommendation is remove/disable that PoS and see if that helps. Looking at the log shows lots of stream_elements errors, some of which could be config issues on your end?

My thinking is that with all of the errors in the log for stream_elements, especially with network communication could, in theory, flood OS network stack and mess up other apps on same PC.

Then, at a higher level, is doing the equivalent of not driving while blind. I have monitoring enabled on your router as well as streaming PC (so you can see bandwidth levels, re-transmissions, etc)
 

Tinteex

New Member
Unfortunately. dmemphis's description of a solution was more than likely a coincidence than an understanding of how compute networking functions. In this case 'locked up' simply meant overwhelmed/bottlenecking. Simple network traffic monitoring (on the router, the switch, or the streaming PC) would most likely have shown that. rebooting switch was most likely unnecessary/overkill (akin to using a hand grenade instead of a fly-swatter). All that needed to be done is stop overwhelming the upload bandwidth. rebooting the switch interrupted the upload from the streaming PC. One could accomplish the same by unplugging Ethernet (or Airplane mode if WiFi connected, which of course should NOT be done when live-streaming). Either that or it was a cheap, defective Ethernet switch (something like TP-link or similar)

When you switch ports you are forcing everything on your PC to stop sending. That clearly is resolving whatever the issue is temporarily (effectively forcing a network re-connection/reset including at App level). I notice you have the StreamElements plug-in, and I can't even count how many trouble systems also run that. That plug-in pukes all over the OBS log, which indicates a lack of professionalism and quality on the part of the StreamElements and their programmers [yes, a professional opinion]. So... my first recommendation is remove/disable that PoS and see if that helps. Looking at the log shows lots of stream_elements errors, some of which could be config issues on your end?

My thinking is that with all of the errors in the log for stream_elements, especially with network communication could, in theory, flood OS network stack and mess up other apps on same PC.

Then, at a higher level, is doing the equivalent of not driving while blind. I have monitoring enabled on your router as well as streaming PC (so you can see bandwidth levels, re-transmissions, etc)
I will check that, and in fact i have a tp-link switch
"
TP-Link TL-SG105E 5-Ports
"

Is it bad? Can you reccomend a better one? i will try deleting the streamelements plugin
 

Lawrence_SoCal

Active Member
Start with the most likely culprit - that plugin... only proceed to next step if the prior action doesn't result in desired outcome. change too many things at once and you'll never know what real root cause was
 

Tinteex

New Member
Screenshot 2021-10-28 21.02.11.png



Whats really weird...... i tried this tool on the stream pc, i get good upload but the quality is 0.

my gaming pc gets 10k+ and 100 quality .... any ideas?

therefore it cant be the streamelements plugin.

i thought its the switch... bot both pcs connect to the switch.
 

rockbottom

Active Member
It's not OBS, probably the switch.

Easy fix, uncomplicate your set-up & your life, ditch NDI & PC2. You clearly do not need it with a 5950x & a GTX-1050 TI.
 

rockbottom

Active Member
I already gave you the answer & where did I say get rid of it?

Sometimes simpler is not only easier but a better solution.
 

Lawrence_SoCal

Active Member
Whats really weird...... i tried this tool on the stream pc, i get good upload but the quality is 0.
my gaming pc gets 10k+ and 100 quality .... any ideas?

Could be lots of things, none of which has anything to do with OBS or streaming. So you are into general PC troubleshooting
- OS config/operation
- physical NIC on that PC
- cable on that PC
- switch port plugged into
 

Tinteex

New Member
i reinstalled all drivers again, then adjusted MTU, now i only loose obs connection, internet & lan stay. i get this new error message now
the reconnect was almost instant now and i didnt need to plug any cables in or out. if my chat wouldnt have told me, i wouldnt even have noticed

23:19:51.768: socket_thread_windows: Received FD_CLOSE, 18811 ms since last send (buffer: 1063687 / 1064960)
23:19:51.768: socket_thread_windows: Aborting due to FD_CLOSE, error 10053
23:19:51.768: [rtmp stream: 'adv_stream'] Disconnected from rtmp://ams03.contribute.live-video.net/app
23:19:51.768: Output 'adv_stream': stopping
23:19:51.768: Output 'adv_stream': Total frames output: 1059450 (1060507 attempted)
23:19:51.768: Output 'adv_stream': Total drawn frames: 1060695 (1060705 attempted)
23:19:51.768: Output 'adv_stream': Number of lagged frames due to rendering lag/stalls: 10 (0.0%)
23:19:51.768: Output 'adv_stream': Number of dropped frames due to insufficient bandwidth/connection stalls: 1057 (0.1%)
23:19:51.769: Output 'adv_stream': Reconnecting in 10 seconds..
23:19:51.769: [rtmp stream: 'adv_stream'] Freeing 842 remaining packets
23:19:51.769: Video stopped, number of skipped frames due to encoding lag: 12/1060601 (0.0%)
23:19:51.827: warning: 2 frames left in the queue on closing
23:20:01.769: ---------------------------------
23:20:01.769: [x264 encoder: 'streaming_h264'] preset: slower
23:20:01.769: [x264 encoder: 'streaming_h264'] profile: high
23:20:01.769: [x264 encoder: 'streaming_h264'] settings:
23:20:01.769: rate_control: CBR
23:20:01.769: bitrate: 8000
23:20:01.769: buffer size: 6000
23:20:01.769: crf: 23
23:20:01.769: fps_num: 60
23:20:01.769: fps_den: 1
23:20:01.769: width: 1536
23:20:01.769: height: 864
23:20:01.769: keyint: 120
23:20:01.769:
23:20:01.769: [x264 encoder: 'streaming_h264'] custom settings:
23:20:01.769: scenecut = 0
23:20:01.772: ---------------------------------
23:20:01.772: [FFmpeg aac encoder: 'adv_stream_aac'] bitrate: 320, channels: 2, channel_layout: 3
23:20:01.772:
23:20:01.774: [rtmp stream: 'adv_stream'] Connecting to RTMP URL rtmp://ams03.contribute.live-video.net/app...
23:20:01.794: [rtmp stream: 'adv_stream'] Interface: Realtek Gaming 2.5GbE Family Controller (ethernet, 1000 mbps)
23:20:02.789: [rtmp stream: 'adv_stream'] Connection to rtmp://ams03.contribute.live-video.net/app successful
23:20:02.789: [rtmp stream: 'adv_stream'] New socket loop enabled by user
23:47:16.139: adding 42 milliseconds of audio buffering, total audio buffering is now 64 milliseconds (source: NDI Wave 3)

FD_CLOSE is a new error anyone knows what it means?
 

R1CH

Forum Admin
Developer
Something is preventing you from sending data and the connection died after stalling for 18 seconds.

Some other things to try in order: in your network adapter properties, disable flow control, disable green / energy efficient ethernet, disable large send offload.
 

Tinteex

New Member
Something is preventing you from sending data and the connection died after stalling for 18 seconds.

Some other things to try in order: in your network adapter properties, disable flow control, disable green / energy efficient ethernet, disable large send offload.
i changed all these Settings, sadly it happened again today After 4 hrs 14 min of streaming. anyone got another idea?


tried a fresh obs install without streamelements, still no change
 

Tinteex

New Member
- replaced the switch problem appeared after a few minutes again

19:30:41.914: Max audio buffering reached!
19:30:41.914: adding 917 milliseconds of audio buffering, total audio buffering is now 960 milliseconds (source: NDI SCREENCAP)
19:30:41.914:
19:31:52.242: User switched to scene 'Browsing'
19:45:33.099: [rtmp stream: 'adv_stream'] bitrate decreased to: 7900
19:45:50.664: socket_thread_windows: Received FD_CLOSE, 18806 ms since last send (buffer: 1062910 / 1064960)
19:45:50.664: socket_thread_windows: Aborting due to FD_CLOSE, error 10053
19:45:50.664: [rtmp stream: 'adv_stream'] Disconnected from rtmp://fra02.contribute.live-video.net/app
19:45:50.666: Output 'adv_stream': stopping
19:45:50.666: Output 'adv_stream': Total frames output: 98240
19:45:50.666: Output 'adv_stream': Total drawn frames: 98457
19:45:50.666: Output 'adv_stream': Reconnecting in 10 seconds..
19:45:50.666: [rtmp stream: 'adv_stream'] Freeing 1902 remaining packets
19:45:50.860: warning: 2 frames left in the queue on closing
19:46:00.667: ---------------------------------
19:46:00.667: [x264 encoder: 'streaming_h264'] preset: slower
19:46:00.667: [x264 encoder: 'streaming_h264'] profile: high
19:46:00.667: [x264 encoder: 'streaming_h264'] settings:
19:46:00.667: rate_control: CBR
19:46:00.667: bitrate: 8000
19:46:00.667: buffer size: 6000
19:46:00.667: crf: 23
19:46:00.667: fps_num: 60
19:46:00.667: fps_den: 1
19:46:00.667: width: 1536
19:46:00.667: height: 864
19:46:00.667: keyint: 120
19:46:00.667:
19:46:00.667: [x264 encoder: 'streaming_h264'] custom settings:
19:46:00.667: scenecut = 0
19:46:00.669: ---------------------------------
19:46:00.669: [FFmpeg aac encoder: 'adv_stream_aac'] bitrate: 320, channels: 2, channel_layout: 3
19:46:00.669:
19:46:00.680: [rtmp stream: 'adv_stream'] Dynamic bitrate enabled. Dropped frames begone!
19:46:00.680: [rtmp stream: 'adv_stream'] Connecting to RTMP URL rtmp://fra02.contribute.live-video.net/app...
19:46:00.700: [rtmp stream: 'adv_stream'] Interface: Realtek Gaming 2.5GbE Family Controller (ethernet, 1000 mbps)
19:46:02.009: [rtmp stream: 'adv_stream'] Connection to rtmp://fra02.contribute.live-video.net/app successful
19:46:02.009: [rtmp stream: 'adv_stream'] New socket loop enabled by user
19:46:05.682: [rtmp stream: 'adv_stream'] bitrate decreased to: 7300
19:46:09.276: Source NDI SCREENCAP audio is lagging (over by 8650.68 ms) at max audio buffering. Restarting source audio.
19:46:35.699: [rtmp stream: 'adv_stream'] bitrate increased to: 8000, done
 
Top