Dahua NVR Reboots during the day

Those with reboot issue, are your NVR plugged directly into the outlet on the wall?

If your NVR is plugged into power protector or UPS, will you be willing to test it plugged directly to outlet to see if it stop your reboot issue? Just make sure there no storm outside while testing this.
 
TechBill said:
Those with reboot issue, are your NVR plugged directly into the outlet on the wall?

If your NVR is plugged into power protector or UPS, will you be willing to test it plugged directly to outlet to see if it stop your reboot issue? Just make sure there no storm outside while testing this.
Click to expand...
Mine is plugged into a ups. If it can't handle a ups then it has NO place in my setup. However I realize some crappy power supplies may flake out when getting anything but mains power. So i have a new power supply rated at over twice the amperage on order to see if that helps.

I suppose this will also be a good time for me to swap the small ups I'm using for my massive one. 70 minutes battery time isn't enough. :)

Sent from my Pixel XL using Tapatalk
 
Mines plugged into a surge protector along with all the other electronics in that room which is then straight into the wall.
 
Just a random thought here, since it seems like IVS events seem to trigger some of the reboots, is it possible the camera firmware could be affecting it somehow?

I copied this from one of mine and all cameras were updated on the same day with this firmware so it should be the same for all of mine...

Device TypeIPC-HDW5231R-Z
Software Version2.460.0000.7.R, Build Date: 2017-03-06
WEB Version3.2.1.427921
ONVIF Version2.42

And I believe that it is the NTSC not PAL.

I'll have to look at my NVR logs tonight and see if they line up with my updated camera firmware....
 
Wouldn't you know it....all of my reboots started after I upgraded the camera's firmware. Here is a time line of my NVR usage....

4/13/2017 got it up and running. Started recording 24/7 and IVS. Two reboots that day, probably on purpose although I don't remember it restarting and in the file it says the 0x00 is a Normal Reboot and the second was 0x01 which is an Abnormal Reboot.

4/14 - 4/21 NO REBOOTS (that I know of or in the log)

4/20 I upgraded the firmware of my cameras.

4/21 I somehow (I forget how) restarted the NVR on accident. Or maybe it just rebooted itself while I was on it and I thought it was something that I did. Either way, that isn't in the records log, I just remember it happening. On this day after that reboot my IVS push notifications mysteriously started working on my phone. I don't think I made any settings changes (see here)

Then on the the 22nd which was 2 days after upgrading my camera's firmware the reboots started for me. Every day since then including once today already.

upload_2017-5-3_18-59-6.png


Anybody else want to check the time line of their reboots vs firmware upgrades?

It could be just a wild coincidence, but it also might explain why not every 5216 NVR owner has reboots...
 
Last edited:
My NVR is at 3.210.002.2; build 2016-07-21.
My 5231 cameras are 2.460.000.5.R, build 2017-01-17.

That definitely could be the reason. Which is pretty sad since firmware on the camera shouldn't cause the NVR to crash. Lol.

Wow, no reboots today! Impressive!
 
I'm running same firmwares on my PoE NVR and zero reboots; IVS enabled on every camera...
 
I initially had the Jan 2017 firmware on most of my cameras (I think the first 3 had the late 2016 firmware), then upgraded all to the recent firmware update. Not a single random reboot before or after any of the firmware upgrades. IVS is enabled. I have the 5216 non-Poe nvr (with 2 Seagate 6Tb Skyhawks HDs. Powered through a Cyberpower 1500 UPS. I just checked the logs, and the only reboots showing were the ones I initiated 8 days ago when adding several more cameras.
 
I've got a Blue Iris evaluation installed on a spare Intel i5 PC. It remains to be seen whether it'll be able to handle all 10 of my cameras, but I understand the "direct to disk" option doesn't work in demo mode, so we'll see.

I'm already MUCH happier with the fact that you CAN do event pre-recording in Blue Iris. Not the, "oh we'll start recording once the event is over" that I'm using to with the Dahua NVR.

I think the Dahua NVR will just be set to record 24/7 and I'll migrate over to BI to record 24/7 and mark events of interest. Having a backup recording device isn't a bad idea anyways I guess.
 
cybermech said:
I initially had the Jan 2017 firmware on most of my cameras (I think the first 3 had the late 2016 firmware), then upgraded all to the recent firmware update. Not a single random reboot before or after any of the firmware upgrades. IVS is enabled. I have the 5216 non-Poe nvr (with 2 Seagate 6Tb Skyhawks HDs. Powered through a Cyberpower 1500 UPS. I just checked the logs, and the only reboots showing were the ones I initiated 8 days ago when adding several more cameras.
Click to expand...

Yeah, I haven't gotten a clear response regarding what could cause this problem. The new power supply for the Dahua comes today. So we'll see if it makes the unit a more reliable backup recording device.
 
Tygunn said:
Yeah, I haven't gotten a clear response regarding what could cause this problem. The new power supply for the Dahua comes today. So we'll see if it makes the unit a more reliable backup recording device.
Click to expand...

Im hoping it does because it would make sense even coupling the firmware card into the mix. along with the reboots people are reporting lags of time and frame rates with IVS triggers. I don't know cameras but i work on a lot of machinery, and Ive seen similar instances with PLC's were there was a problem with poor/sub power supply to a unit coupled with a bad string of code that would make rapid multiple calls to a address. this caused a LAG spike and a heavy draw to the units power supply and would cause weird errors and reboots. Not saying this is anything like what i have delt with but from a point of logical elimination it parallels.

There could be a problem with code/firmware that having a significant enough power supply like those in the POE powered units have, preventing the reboots. or maybe my tinfoil is on too tight. :paranoid:
 
HMS said:
Im hoping it does because it would make sense even coupling the firmware card into the mix. along with the reboots people are reporting lags of time and frame rates with IVS triggers. I don't know cameras but i work on a lot of machinery, and Ive seen similar instances with PLC's were there was a problem with poor/sub power supply to a unit coupled with a bad string of code that would make rapid multiple calls to a address. this caused a LAG spike and a heavy draw to the units power supply and would cause weird errors and reboots. Not saying this is anything like what i have delt with but from a point of logical elimination it parallels.

There could be a problem with code/firmware that having a significant enough power supply like those in the POE powered units have, preventing the reboots. or maybe my tinfoil is on too tight. :paranoid:
Click to expand...

When the unit isn't rebooting, the lost frames are particularly frustrating as well. I had a package delivered the other day and when I played back the video (records 24/7 with IVS event markers), I saw the delivery person walk up, and then the video froze and by the time there were frames available again, the delivery person was gone. NOT useful for surveillance.

I can definitely see bad power being a cause of all sorts of issues though. I'm sure the included power supplies are the cheapest of the cheap junk power supplies out there. Crossing my fingers that I can get more stability out of the NVR.
 
This may seem like a dumb suggestion (I'd try it myself if I had one of these troublesome NVRs) but has anyone logged the serial console or the kernel log to see what log events exist preceding and following the reboot event?
As the reboot is being recorded with a specific cause, there will almost certainly be error / status / informational messages in the logs that may explain whey the kernel feels it can't continue and must reboot.
 
  • Like
Reactions: fenderman
alastairstevenson said:
This may seem like a dumb suggestion (I'd try it myself if I had one of these troublesome NVRs) but has anyone logged the serial console or the kernel log to see what log events exist preceding and following the reboot event?
As the reboot is being recorded with a specific cause, there will almost certainly be error / status / informational messages in the logs that may explain whey the kernel feels it can't continue and must reboot.
Click to expand...

That is a FANTASTIC idea. I'm going to do that and keep a running log of the console.

HAHAH, okay wow. I actually need an RS232 serial cable for the first time in ages. I guess I better order one on Amazon. Looks like I need Female to Female.
 
Tygunn said:
That is a FANTASTIC idea. I'm going to do that and keep a running log of the console.

HAHAH, okay wow. I actually need an RS232 serial cable for the first time in ages. I guess I better order one on Amazon. Looks like I need Female to Female.
Click to expand...

Shame your not close to me (maybe you are) got a stack of them for PLC work..
 
You must log in or register to reply here.
Top Bottom