Blue Iris no longer recording after crash

foundbobby

n3wb
Oct 31, 2017
5
0
Bay Area, California
Blue Iris crashed on me earlier today (around 2:40PM) all cameras stopped recording so I rebooted the machine and now Blue Iris doesn't record when cameras are triggered.

When I logged in to the machine here was the crashed state:
Screen%20Shot%202018-06-18%20at%207.04.06%20PM.png


After rebooting the machine I repaired the database and even manually deleted some recorded files
Screen%20Shot%202018-06-18%20at%208.03.19%20PM.png


I manually triggered a few cameras (and I saw some movement that triggered them normally but I have no recordings after the crash even though camera borders light up red:
Screen%20Shot%202018-06-18%20at%208.07.08%20PM.png


Any advice or thoughts on how I can fix this? Logs below if they're helpful, if only to show the cameras are indeed getting triggered.

Logs from the crash time:
3 6/18/2018 2:37:28 PM PowerPolePatio MOTION
0 6/18/2018 2:37:58 PM New Move: 2 files 60.7M [21/168 hrs, 20.0G/20.0G, 59.8G free]
3 6/18/2018 2:37:58 PM PowerPoleDown MOTION
0 6/18/2018 2:37:59 PM Stored Delete: 14 files 30.2M [239/3360 hrs, 150.0G/150.0G, 59.8G free]
0 6/18/2018 2:37:59 PM Aux 1 Delete: nothing to do [358/672 hrs, 199.9G/200.0G, 59.8G free]
3 6/18/2018 2:38:41 PM PowerPolePatio MOTION
3 6/18/2018 2:38:59 PM PowerPolePatio MOTION
3 6/18/2018 2:39:22 PM PowerPoleDown MOTION
1 6/18/2018 2:40:30 PM Office Signal: network retry
1 6/18/2018 2:40:30 PM ServerCloset Signal: network retry
1 6/18/2018 2:40:30 PM PowerPolePatio Signal: network retry
1 6/18/2018 2:40:31 PM SideGateAlert Signal: network retry
1 6/18/2018 2:40:31 PM GarageAlert Signal: network retry
1 6/18/2018 2:40:35 PM SideGate1 Signal: network retry
1 6/18/2018 2:41:00 PM PowerPolePatio Signal: network retry
1 6/18/2018 2:41:00 PM ServerCloset Signal: network retry
1 6/18/2018 2:41:00 PM Office Signal: network retry
1 6/18/2018 2:41:01 PM SideGateAlert Signal: network retry
1 6/18/2018 2:41:01 PM GarageAlert Signal: network retry
1 6/18/2018 2:41:05 PM SideGate1 Signal: network retry
1 6/18/2018 2:41:30 PM PowerPolePatio Signal: network retry
1 6/18/2018 2:41:30 PM ServerCloset Signal: network retry
1 6/18/2018 2:41:30 PM Office Signal: network retry

(they continue with network errors for hours)

Logs from manual trigger now:
3 6/18/2018 8:06:57 PM TreeFrontDoor EXTERNAL
3 6/18/2018 8:07:05 PM SideGate GROUP
3 6/18/2018 8:07:05 PM FrontBark EXTERNAL
3 6/18/2018 8:07:05 PM Garage GROUP
3 6/18/2018 8:07:05 PM GarageEve GROUP
0 6/18/2018 8:07:16 PM FrontBark Email: <email redacted> with 2 attachment/s
0 6/18/2018 8:07:16 PM FrontBark Email: <email redacted> with 2 attachment/s
0 6/18/2018 8:07:16 PM FrontBark Email: <email redacted> with 2 attachment/s
0 6/18/2018 8:07:16 PM FrontBark Email: <email redacted> with 2 attachment/s
 
Blue Iris crashed on me earlier today (around 2:40PM) all cameras stopped recording so I rebooted the machine and now Blue Iris doesn't record when cameras are triggered.

When I logged in to the machine here was the crashed state:
Screen%20Shot%202018-06-18%20at%207.04.06%20PM.png


After rebooting the machine I repaired the database and even manually deleted some recorded files
Screen%20Shot%202018-06-18%20at%208.03.19%20PM.png


I manually triggered a few cameras (and I saw some movement that triggered them normally but I have no recordings after the crash even though camera borders light up red:
Screen%20Shot%202018-06-18%20at%208.07.08%20PM.png


Any advice or thoughts on how I can fix this? Logs below if they're helpful, if only to show the cameras are indeed getting triggered.

Logs from the crash time:
3 6/18/2018 2:37:28 PM PowerPolePatio MOTION
0 6/18/2018 2:37:58 PM New Move: 2 files 60.7M [21/168 hrs, 20.0G/20.0G, 59.8G free]
3 6/18/2018 2:37:58 PM PowerPoleDown MOTION
0 6/18/2018 2:37:59 PM Stored Delete: 14 files 30.2M [239/3360 hrs, 150.0G/150.0G, 59.8G free]
0 6/18/2018 2:37:59 PM Aux 1 Delete: nothing to do [358/672 hrs, 199.9G/200.0G, 59.8G free]
3 6/18/2018 2:38:41 PM PowerPolePatio MOTION
3 6/18/2018 2:38:59 PM PowerPolePatio MOTION
3 6/18/2018 2:39:22 PM PowerPoleDown MOTION
1 6/18/2018 2:40:30 PM Office Signal: network retry
1 6/18/2018 2:40:30 PM ServerCloset Signal: network retry
1 6/18/2018 2:40:30 PM PowerPolePatio Signal: network retry
1 6/18/2018 2:40:31 PM SideGateAlert Signal: network retry
1 6/18/2018 2:40:31 PM GarageAlert Signal: network retry
1 6/18/2018 2:40:35 PM SideGate1 Signal: network retry
1 6/18/2018 2:41:00 PM PowerPolePatio Signal: network retry
1 6/18/2018 2:41:00 PM ServerCloset Signal: network retry
1 6/18/2018 2:41:00 PM Office Signal: network retry
1 6/18/2018 2:41:01 PM SideGateAlert Signal: network retry
1 6/18/2018 2:41:01 PM GarageAlert Signal: network retry
1 6/18/2018 2:41:05 PM SideGate1 Signal: network retry
1 6/18/2018 2:41:30 PM PowerPolePatio Signal: network retry
1 6/18/2018 2:41:30 PM ServerCloset Signal: network retry
1 6/18/2018 2:41:30 PM Office Signal: network retry

(they continue with network errors for hours)

Logs from manual trigger now:
3 6/18/2018 8:06:57 PM TreeFrontDoor EXTERNAL
3 6/18/2018 8:07:05 PM SideGate GROUP
3 6/18/2018 8:07:05 PM FrontBark EXTERNAL
3 6/18/2018 8:07:05 PM Garage GROUP
3 6/18/2018 8:07:05 PM GarageEve GROUP
0 6/18/2018 8:07:16 PM FrontBark Email: <email redacted> with 2 attachment/s
0 6/18/2018 8:07:16 PM FrontBark Email: <email redacted> with 2 attachment/s
0 6/18/2018 8:07:16 PM FrontBark Email: <email redacted> with 2 attachment/s
0 6/18/2018 8:07:16 PM FrontBark Email: <email redacted> with 2 attachment/s
you updated to the latest release which is buggy, see threads with instructions on reverting back.
 
  • Like
Reactions: foundbobby