Rebooting IP Camera Statistics And Practices

By: IPVM Team, Published on Aug 10, 2017

Dahua cameras automatically reboot weekly, by default.

Is this an innovation by the Chinese mega-manufacturer or a sign of a problems?

125 integrators told IPVM what they do about rebooting cameras, either never, on a schedule or for certain specific reasons.

Statistics Summary

Overall, only about 1 in 8 integrators reboot cameras on a schedule:

*****

**** *********** ** *** reboot ******* ** * regular *****. **** **** confused ** *** **** idea:

"********* ** *** *** adage.... '** ** ***'* broke... ***'* *** **.'"
"** ** *******, ******* on ******** *** ****** for ********."
"** ***'*, *** ***** we ****** * ****** thats ******* ****?"
"*****, ** **** *** set ** ********* ** shouldn't ** *********."
"*'* ******** * *** surprised ** *** **** that ********** ******* *** a ********* **** *** anyone."
"***** ****** ** **** an ***** **** ******** , ** ***'* **** customers ** **** **** in *****."
"*** **** *** *** would **** ** ******* a ******** ***** ******* and/or ****** ******** **** to ** ******** ** a ********. **** ***** never *** *** *** customers ** *** ******/******* would **** *********."
"********** ** *** ****** them ** * ********, do * **** **?"

Top *******

*** **** ****** ******* given *** ********* * camera ****:

***************
******** *******
************* *** *****

**** *********** **** ** that ******* ****** ****** require ********* **** ***** than ******, *** ** one ***** *** ******* out **** ***** **** others.

***** * ******** ** integrators ** ******** ******* reboots, ***** *** ** consensus ** *** *********, with ******* ******* **** ***** to ********. **** *********** that ** *** ********* schedule ******* ********* ** interest ** ***** **.

Integrators ***** ****** ******* **** ********* ** *****

*** ***** **** ** troubleshooting ********* ** ****** *** camera. **** '****** ****' allows ***** ** *****, settings ** ***********, *** connections ** ** ************. Integrators **** ** **** this ** *** **** common ****** *** ********* cameras, *** ********** ** not ****** *** ****** unless ********* ** *****.

"** ***** ** ******** due ** ****** *******. It's *** ***** **** in *************** **** * camera *** ***** *** is *******."
"** **** ** * remote ****** ** *** to ******* ****** ****** in **** ** ******* a *****."
"********* **** ** * reboot ** ** **** that ********* ** **** 'off' **** *** ******."
"******* *** ********, ** there ** ** ***** with *** ****** *.* artifacts, ***** ** ********** issues, ***** ******. ********* reboot ** ****."
"****** ** **** ** we ****** *** ******* unless ***** ** ******* shooting **** * ****** or *** ****** *********** in *****."
"****** **** *** ***************. We ***'* ********* **** scheduled *******. ** * camera *** **** ************* often ** ****** *******, then ** ***** ********* reboot *** *** ** that ******** *** *****."
"** ***** ** ******** due ** ****** *******. It's *** ***** **** in *************** **** * camera *** ***** *** is *******."
"********* ** *** ** the ******* *************** ******* for **** **********. ** a ******** ***** **** a ***** **** *****, we *** ** ******** reboot *****. ** ** cannot ****** *** ******* or ******* ******, ** will *** *** ******** to "**** ******". ** is *** ******** ** common ****** ** ******* a ********* ******, *** that **** ******* ** the ************ ** *** camera."
"*** **** **** ** reboot ******* ** ****** troubleshooting ** * ***** step. ** *****'* **** a **** ** ****** on * ********."
"** *****'* ** ***** with * ****** ** will ***** ***** ***** the **** ** *** switch ** *** ** the ******* ******** ******. If ** *** * firmware ****** ** ****** power ***** ***** *** update **** ** *** camera *****'* ***** *** power *****. ***** **** that ** ***'* *** have *** ********* ** power *****."
"*** ******* ** *** up ********* *** ****** always ** * ****** of ********* ***** ***** (usually ******** ****** *********** and ******* **, ** RTSP ******* ******). ** do *** **** *** cameras *** ** ****** on * ******** ** a ******* ********** (*** only **** ** ****** on * ******** ** if ** **** *** determined *** ***** ** RTSP ********, ** ** have **** ****** ** a ******** ** ******** the ****** ** **** dropping ****** ** **** a ********* ***)."

Integrators ****** *** ****** **** ******** ********

******** ******* ***** ******* a ****** ** **** affect.

"**** ** ********/******** *******."
"**** ** ***** ** an ***** ** ** are ********* *** ********."
"**** ****** - ******* only **** ** ** firmware ******** ** ******* to ********."
"**** **** ***** ** an *****, ** **** upgrading ********."
"********* **** ****** ******** updates."
"**** **'* **** *** a ******** ******, **** the ****** **** ********."
"*** ***** ** ********, for ******* *** *************/******** update."

Integrators ****** *** ****** ****** *************

********* *** ****** ****** configuration ******* ** **** place.

"**** * ****** ***** on ****** & ****** to *** ***, ***** that *********** *****."
"**** ** ***-******** ************* setup."
"***** *** ****** *** make *** ******* ** IP *** ******** *** power ****. ** ******* to *** **** *** power ** ***** *** do *** **** ***** specific ********* ********."
"** ****** ****** *****."
"* ****** *** ******* only ***** ********."
"***** *** ****** *** make *** ******* ** IP *** ******** *** power ****. ** ******* to *** **** *** power ** ***** *** do *** **** ***** specific ********* ********."

Integrators ***** **** **** ****** ******* **** ******* **** ******

**** ** ****** ****** by bad ***********:

"******* ***** *-* ******* cameras **** ****** ******** that ******* *******."
"**** *** ******* *** probably *** *** ** reboot **** ***** ** clear ** ******."
"******* ** *** ************... Axis & **** ******* rarely *** **** **** they **** ****** **. Other ****** ** **** tried ****** ** **** up **** **** *****, so ** ****** ******* anything *** **** *******."
"** **** * *** clients **** **** ** occasional ****** (**** ***** month ** **), **** there's ***** ****--** ** Axis ****** ** ****."
"*******, ***** *******, *** Sony **** ** **** that **** ****** *** need ** ** ******** the ****."
"**************, ********* ** *** manufacturer."
"********* *** ******* ** not ******* * ******. We ***** ****** **** do."

Reboot ********* ** ***********

*******, ***** *** ** consensus ** *** ***** cameras ****** ** ********. Dahua, *** *******, ******** a ****** ** **** a ****.

"**** * ***, ********** and **********"
"**** * ****."
"** * ******** , because **** ** ******* tend ** **** **** left ******* *** **** duration."
"**** ** ******. ***** Digital ******* *** ******* really ***** ****. ****** that * **** *******, we **** ******* ** install ****** *** ******** which **** ***** "** Alive *****" *******. ******* of ******** ********* ** entire ******, ***. ** now **** *** ****** automatically ***** ***** ** ports **** **** ** self **** *****."
"**** **** ** ** rebooted ******* ** **. We *** ********* ******* at ******* ** * schedule, *** ** *** growing ********* ** ********* needed."
"** ****** ******* *** every *** ***** ** a ********, **** ** refresh *** **** *** provide *** ****** **** any ******* ** *** need."
"** * ********, ** the ****** *** * routine *********** *********. *********, on ******* ***** ***** it ***** *********."
"** ******* ****** ************* defaults. ** **** ******* to ********* ****** (*****), we ******** ***** **** setting *****, ******** *** manufacturer *** * **** reason *** *** *******. Otherwise, ** ** *** add * ****** ****** to *** ***** ******."
"** ***** ******* ***** storms, ** **** * quarter. ********* **** ***'* work ** ***, ** the ***** *** * haze **** **."
"** * ********** *********** schedule. ** ***** ****** cache."
"** **** ***** ** will ******** * ****** reboot ** * ******** requires ** ** ** there ** ******** ***** a ******* ******* ** continue ******* ******* ****."
"********* - ****** ** the ********."
"********* *** **** * week. ******* ************ **************."
"**** ****** *** ****** maintenance."

Some *********** *** ******** ** ********** *******

"***** ** ******* ** reboot ** * **** of ********** ***********. **** to ** **** ******** on ****."
"**** ****** ******** ** customer ************: *** ************** is ** ****** **** at ***** ******* *** check *** ******** ******* during **** ****, ******* we ** *** ********* perform ********** *** *********** of *** *********' *********, and ** *** **** provide *********** ** *** they ** ** **********. We **** ***** *********** in ***** ** ****** continued ********, ****** *** security, *** ********* **** no ******* **** **** the ******** **** **** their *********."
"*** ** *** ******** has ***** ***** *******, installed ** ******** ***** all ** ***** ********. We **** ** ****** about ** ******* * week *** ******* ** cannot *******. **** **** back ** **% ** the ****. ****'* **** a *** **** ***** we **** ***** *** switch **** ********. ******** will *** ***** ** scheduled *******."
"** *** ***** ***** that ** ** *** finding *** **** ** start ********* ******* **** often *** **** ******. We *** ****** **** lock ** **** ** used **."
"***'* ** * ******** though ** **** ****** sites **** ***** ** beneficial."

Comments (21)

Undisclosed Distributor #1

08/10/17 04:15pm

It's a inheritance from theirs first DVRs time. Unstable FW was a risk as DVR malfunction lead to records of number of cameras loss potentially. Still this sign of non-stable FW exists.

Dirk Hedlund

08/11/17 05:13pm

Mobotix cameras automatically reboot between 3 and 4 am as part of the factory configuration. They are extremely stable and have been for years, this is certainly not a Dahua innovation. I've put in place automatic reboot scripts on some of the cheaper brand cameras we use, I think it's good practice. Of course, I am also a believer in the mentality of 'if it ain't broke, don't fix it.'

Lynn Harold

In reply to Dirk Hedlund | 08/11/17 07:26pm

I was going to mention the old Mobotix daily reboot, you beat me to it. However, the reason they used to give in the manuals was pretty hysterical - radiation at high altitudes?

Luis Carmona

IPVMU Certified | In reply to Lynn Harold | 08/11/17 07:36pm

3:32AM - Wait by back door.

3:36AM - Break through door, run to room with NVR while cameras reboot. Power off NVR.

3:38AM - Break into safe, steal jewels.

4:05AM - Run out back door.

9:25AM - Renew IPVM subscription.

Undisclosed #2

In reply to Luis Carmona | 08/11/17 08:27pm

3:36AM - Break through door, run to room with NVR while cameras reboot. Power off NVR

Any radiation hardened Mobotix installer working at high-altitudes will stagger the various camera reboot times to thwart such a move ;)

Luis Carmona

IPVMU Certified | In reply to Undisclosed #2 | 08/11/17 08:41pm

You may have made an indirect point about Mobotix installers being more proficient than other installers. But you have to admit, it's hard enough getting this industry just to change default passwords, let alone change factory set reboot times.

Undisclosed #2

In reply to Luis Carmona | 08/12/17 02:18am

btw, Mobotix may have the strangest default password yet: "meinism"

This, one might think, would encourage mobots to change the password tosomething else, but with no factory reset button, nor "one day password", you are mailing a brick to Germany if you forget it.

Daniel Kabs

In reply to Undisclosed #2 | 08/15/17 03:40pm

For the sake of clarity, the default password for MOBOTIX cameras is: "meinsm"

Daniel Kabs

In reply to Luis Carmona | 08/15/17 03:48pm

This automatic reboot behavior has been changed at least 5 years ago: by factory default, a MOBOTIX camera automatically reboots once a week (I think Mondays) at a random time between 3 a.m. and 4 a.m.

John Honovich

IPVM | In reply to Dirk Hedlund | 08/11/17 08:57pm

this is certainly not a Dahua innovation

The term 'innovation' in the opening was mostly meant as sarcasm. That was my fault for not making it clear. It does not take any 'innovation' to reboot a computer. It is more of a questionable practice.

Rodney Thayer

08/13/17 08:44pm

Some switch vendors are starting to add this. Not a good idea IMO. Thank you for exploring the topic.

Luis Carmona

IPVMU Certified | In reply to Rodney Thayer | 08/14/17 11:59am

Rodney, you mean the switch having a ping monitor and reboot of the port on the switch...? If so, why don't you think that is a good idea?

Luis Carmona

IPVMU Certified | In reply to Luis Carmona | 08/14/17 04:34pm

What I meant was "If so, why don't you think that is a bad idea?

Undisclosed Manufacturer #3

08/14/17 03:16pm

Certainly not new. Some Sony block equipped analogue PTZ domes used to have to reboot regularly as the focus mechanism would eventually stick if left on an indefinite tour. . A scheduled reboot could rectify all sorts of software issues without having to resort to user intervention.

Undisclosed End User #4

08/14/17 05:18pm

Reboot by schedule smells like to take away the symptoms of the problem. Workaround, not fix nor maintenance in my opinion.

Luis Carmona

IPVMU Certified | In reply to Undisclosed End User #4 | 08/14/17 05:31pm

True, I would consider a last resort, but it should be an option, anyways. Too often it takes too long for a manufacturer to finally admit there is a problem with their product, often the firmware. A scheduled reboot alleviates the problem at least until the maker gets a fix.

And, sometimes a device is up for a long time, say a camera, for maybe 9 months or so at a time before needing a reboot. Maybe a ping monitor reboot doesn't "solve the problem" per se, but at least it makes it more likely video will be captured if a simple reboot fixes it, and not going who knows how long before somebody finally notices it, often only after an incident occurred.

Undisclosed End User #5

08/14/17 08:00pm

We don't do it on a schedule, but when a location starts to have problems with cameras that have been up for an extended period of time we will proactively reboot every camera in that site. We manage ~10,000 cameras (almost all AXIS) and it is definitely not uncommon to see cameras with an up time of 3+ years.

Undisclosed Integrator #6

08/15/17 01:41pm

I would think doing scheduled reboots would cause more problems than anything. It would seem strange to even proactively do this. I can see using the switch to reboot a camera automatically if it loses connectivity which could help get a camera back online quickly but it is only masking some other issue. Out of thousands of cameras we have out in the field I can't say for sure but I would imagine rebooting them all would cause a lot more harm than good.

Luis Carmona

IPVMU Certified | In reply to Undisclosed Integrator #6 | 08/15/17 02:59pm

Maybe not all at the same time. But if a camera is going to have a problem rebooting, I think it's better to have it happen while you are there doing routine service and can address it immediately, rather have it happen off hours or over a weekend, and then it takes longer to turn around the repair.

Undisclosed End User #4

08/15/17 05:30pm

Weekly reboots on schedule smells bad to me, but of course now and then everything needs to be rebooted. Like during firmware updates and so on.

Whatever...

Undisclosed #7

08/27/17 05:17pm

I knew an end user's IT consultant that was facing network flooding issues... instead of fixing the root cause, he made a script to reboot the cameras when lost connection detected, by turning off and on the PoE in the switch port.

He burned half of the cameras, before stop doing this.

Aside of the topic of "to reboot or not to reboot", I think that there are some procedures to be avoided...

Read this IPVM report for free.

This article is part of IPVM's 6,533 reports, 880 tests and is only available to members. To get a one-time preview of our work, enter your work email to access the full article.