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)

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.

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.'

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? 

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.

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 ;)

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.

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.

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

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. 

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.

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

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?

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

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.

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

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.

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.

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.  

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.

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...

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.

Already a member? Login here | Join now

Related Reports

Beware Rigged China Fever Cameras on Sep 08, 2020
Many China fever camera manufacturers have rigged algorithms dynamically...
Uniview Deep Learning Camera Tested on Jul 14, 2020
Uniview's intrusion analytics have performed poorly in our shootouts. Now,...
Fever Camera Sales From Integrators Surveyed on Jun 01, 2020
Fever cameras are the hottest trend in video surveillance currently but how...
Dynamic vs Static IP Addresses Tutorial on Apr 16, 2020
While many cameras default to DHCP out of the box, that does not mean you...
Alabama Schools Million Dollar Hikvision Fever Camera Deal on Aug 11, 2020
The Baldwin County, Alabama public schools purchased a $1 million, 144-camera...
Pivot3 Mass Layoffs on Mar 27, 2020
Pivot3 has conducted mass layoffs, the culmination of grand hopes, a quarter...
Thermology Expert: "95-99%" Doing Fever Screening Wrong, Unjustified Compensating Algorithms "Insane" on Aug 27, 2020
A thermology expert tells IPVM "95 to 99% of people" are doing fever...
Verkada Disruptive Embedded Live Help on Sep 24, 2020
Call up your integrator? Have someone come by the next day? Verkada is...
Access Visitor Management Systems Guide on Jul 22, 2020
"Who are you, and why are you here?" Facilities that implement Visitor...
Forced Door Alarms For Access Control Tutorial on Aug 17, 2020
One of the most important access control alarms is also often ignored....
School District Admits Not Following FDA Guidelines With 144, No Blackbody, Hikvision Fever Cameras on Aug 21, 2020
The Baldwin County School District has admitted it is not following FDA...
Mobile Access Control Usage Statistics 2020 on Sep 21, 2020
Most smartphones can be used as access control credentials, but how...
Anixter Runs Fake Coronavirus Marketing Using Shutterstock Watermarked Images on Jul 24, 2020
Coronavirus faked marketing is regrettably commonplace right now but Anixter...
Sunell Panda Cam Body Temperature Measurement Camera Tested on May 14, 2020
Sunell is far less well known than its gargantuan domestic competitors Dahua...
Integrators Avoiding Coronavirus Air Travel on May 29, 2020
IPVM asked integrators if air travel is part of their 2020 plans to see how...

Recent Reports

Hikvision Sues Over Brazilian Airport Loss on Sep 24, 2020
Hikvision was excluded from a Brazilian airport project because it is owned...
China General Chamber of Commerce Calls Out US Politics on Sep 24, 2020
While US-China relations at an all-time low, optimism about relations...
Verkada Disruptive Embedded Live Help on Sep 24, 2020
Call up your integrator? Have someone come by the next day? Verkada is...
IP Networking Course Fall 2020 - Last Chance - Register Now on Sep 23, 2020
Today is the last chance to register for the only IP networking course...
Drain Wire For Access Control Reader Tutorial on Sep 23, 2020
An easy-to-miss cabling specification plays a key role in access control, yet...
IPVM Camera Calculator User Manual / Guide on Sep 23, 2020
Learn how to use the IPVM Camera Calculator (updated for Version 3.1). The...
Installation Course Fall 2020 - Save $50 - Last Chance on Sep 22, 2020
Today is your last chance to save $50 on registration for the Fall 2020 Video...
SimpliSafe Business Security Launched Examined on Sep 22, 2020
SimpliSafe has launched "SimpliSafe Business Security" that the company...
FLIR CEO: Many New Fever Entrants "Making Claims That The Science Just Won't Support" on Sep 22, 2020
FLIR's CEO joins a growing number calling out risks with fever / screening...
China Bems Temperature Measurement Terminal Tested on Sep 22, 2020
Guangzhou Bems (brand Benshi) is the manufacturer behind temperature...
Axis Exports To China Police Criticized By Amnesty International on Sep 21, 2020
Axis Communications and other EU surveillance providers are under fire from...
Milestone XProtect on AWS Tested on Sep 21, 2020
Milestone finally launched multiple cloud solutions in 2020, taking a...
Mobile Access Control Usage Statistics 2020 on Sep 21, 2020
Most smartphones can be used as access control credentials, but how...
Axis Compares Fever Camera Sellers to 9/11 on Sep 18, 2020
Axis Communications, the West's largest surveillance camera manufacturer, has...