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:

***** ******* ************* ****** weekly, ** *******.

** **** ** ********** by *** ******* ****-************ ** a **** ** * problems?

*** *********** **** **** what **** ** ***** rebooting *******, ****** *****, on * ******** ** for ******* ******** *******.

Statistics ******* 

*******, **** ***** * in * *********** ****** cameras ** * ********:

[***************]

*****

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

Login to read this IPVM report.
Why do I need to log in?
IPVM conducts unique testing and research funded by member's payments enabling us to offer the most independent, accurate and in-depth information.

Related Reports

HTTPS / SSL Video Surveillance Usage Statistics on Apr 01, 2019
HTTPS / SSL / TLS usage has become commonplace for websites to improve security and, in particular, to help mitigate attackers reading or modifying...
Security Fail: ASISNYC Auto Emails Passwords In Plain Text on May 14, 2019
ASIS NYC automatically emails a user with the password the user just entered, in plain text, when one registers for the site / event, as the...
LifeSafety Power NetLink Vulnerabilities And Problematic Response on May 20, 2019
'Power supplies' are not devices that many think about when considering vulnerabilities but as more and more devices go 'online', the risks for...
Vivotek Trend Micro Cyber Security Camera App Tested on Jul 22, 2019
Vivotek and Trend Micro are claiming five million blocked attacks on IP cameras, with their jointly developed app for Vivotek cameras. This new...
Dahua Wiretapping Vulnerability on Aug 02, 2019
IPVM has validated, with testing, and from Dahua, that many Dahua cameras have a wiretapping vulnerability. Even if the camera's audio has been...
Axis Suffers Outage, Provides Postmortem on Aug 15, 2019
This week, Axis suffered an outage impacting their website and cloud services. Inside this note, we examined what happened, what was impacted...
Critical Vulnerability Across 18+ Network Switch Vendors: Cisco, Netgear, More on Aug 26, 2019
Cisco, Netgear and more than a dozen other brands, including small Asian ones, have been found to share the same critical vulnerability, discovered...
Warning: Windows 7 Update Crashing NVRs on Aug 26, 2019
Windows 7 updates are causing VMS servers to fail to boot. After running the update, impacted systems do not boot as normal, instead display this...
ONVIF Exposure To "Devastating DDoS Attacks" Examined on Sep 06, 2019
ZDnet reported "Protocol used by 630,000 devices can be abused for devastating DDoS attacks", citing exposure of ONVIF devices. And after an...
Remote Access (DDNS vs P2P vs VPN) Usage Statistics on Oct 25, 2019
Remote access can make systems more usable but also more vulnerable. How are integrators delivring remote access in 2019? How many are using...

Most Recent Industry Reports

Verkada Paying $100 For Referrals Just To Demo on Jan 22, 2020
Some companies pay for referrals when the referral becomes a customer. Verkada is taking it to the next level - paying $100 referrals fees simply...
Camera Analytics Shootout 2020 - Avigilon, Axis, Bosch, Dahua, Hanwha, Hikvision, Uniview, Vivotek on Jan 22, 2020
Analytics are hot again, thanks to a slew of AI-powered cameras, but whose analytics really work? And how do these new smart cameras compare to top...
Intersec 2020 Final Show Report on Jan 21, 2020
IPVM spent all 3 days at the Intersec 2020 show interviewing various companies and finding key trends. We cover: Middle East Enterprise...
Vehicle & Long Range Access Reader Tutorial on Jan 21, 2020
One of the classic challenges for access control are parking lots and garages, where the user's credential is far from the reader. With modern...
Clearview AI Alarm - NY Times Report Says "Might End Privacy" on Jan 20, 2020
Over the weekend, the NY Times released a report titled "The Secretive Company That Might End Privacy as We Know It" about a company named...
Favorite Camera Manufacturers 2020 on Jan 20, 2020
The past 2 years of US bans and sanctions have shaken the video surveillance industry but what impact would this have on integrators' favorite...
"Severely Impacted" Mercury Security 2020 Leap Year Firmware Issue on Jan 17, 2020
One of the largest access controller manufacturers has a big problem: February 29th. Mercury Security, owned by HID, is alerting partners of the...
Apple Acquires XNOR.ai, Loss For The Industry on Jan 16, 2020
Apple has acquired XNOR.ai for $200 million, reports GeekWire. This is a loss for the video surveillance industry. XNOR.ai stunned the industry...
Installation Course January 2020 - Last Chance on Jan 16, 2020
Thursday, January 16th is your last chance to register for the Winter 2020 Video Surveillance Installation Course. This is a unique installation...
Halo Smart Vape Detector Tested on Jan 16, 2020
The Halo Smart Sensor claims to detect vaping, including popular brand Juul and even THC vapes. But how well does it work in real world...