Anyone ever seen Blue Iris cause massive ping spikes?

singularity42

singularity42

Young grasshopper
Jan 21, 2020
46
15
MN
Woke up this morning, tried to log into the html viewer for BI, its extremely slow and intermittent.
I start a ping test to my BI server and see:
Code: 
Reply from 192.168.1.100: bytes=32 time=983ms TTL=128
Reply from 192.168.1.100: bytes=32 time=960ms TTL=128
Reply from 192.168.1.100: bytes=32 time=19ms TTL=128
Reply from 192.168.1.100: bytes=32 time=69ms TTL=128
Reply from 192.168.1.100: bytes=32 time=917ms TTL=128
Reply from 192.168.1.100: bytes=32 time=904ms TTL=128
Reply from 192.168.1.100: bytes=32 time=901ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time=879ms TTL=128
Reply from 192.168.1.100: bytes=32 time=870ms TTL=128
Reply from 192.168.1.100: bytes=32 time=831ms TTL=128
Reply from 192.168.1.100: bytes=32 time=818ms TTL=128
Reply from 192.168.1.100: bytes=32 time=296ms TTL=128

So I immediately start looking all over my network. Is this a broadcast storm, issue with routing, duplicate ips?
Couldnt find anything. I then decide to go restart BI. As soon as I do:
Code: 
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
Poof. Issue gone. One thing I noticed that was different is one of my cameras had lost its connecting to BI. When I restarted BI that camera came right back as well.
Anyone seen this oddity before?
 
I wonder if there is any correlation between my one camera going off line at random times and bi losing connection to the server?
 
They did seem to go hand in hand. Not entirely sure what happened and not sure I want to dig through all my network logs.
 
My Blue Iris is causing latency spikes across my entire system. Anyone else? I get spikes pinging google DNS... As high as 700ms. Then League of Legends will have 5000ms spikes...

Closing Blue Iris resolves the issue, but I'd prefer to resolve the issue in settings if possible.
 
Cheese said:
My Blue Iris is causing latency spikes across my entire system. Anyone else? I get spikes pinging google DNS... As high as 700ms. Then League of Legends will have 5000ms spikes...

Closing Blue Iris resolves the issue, but I'd prefer to resolve the issue in settings if possible.
Click to expand...
what are your ping times to google with BI shut down
 
I absolutely got this when I had a camera go offline. BI has a setting somewhere (sorry, forget where) about finding lost cameras?
I think it's meant to help find a camera that changes IP because of poorly configured DHCP, maybe? It pings every IP in the subnet fairly often looking for the offline camera(s).
Anyway it absolutely killed my network when I had two cameras offline. Solution was to disable or delete the offline cameras, though I think there's also a setting to turn that behavior off.
 
You must log in or register to reply here.
Top Bottom