*****
**** *********** ** *** 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
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.
Create New Topic
Dirk Hedlund
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.'
Create New Topic
Undisclosed
Some switch vendors are starting to add this. Not a good idea IMO. Thank you for exploring the topic.
Create New Topic
Undisclosed Manufacturer #3
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.
Create New Topic
Undisclosed End User #4
Reboot by schedule smells like to take away the symptoms of the problem. Workaround, not fix nor maintenance in my opinion.
Create New Topic
Undisclosed End User #5
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.
Create New Topic
Undisclosed Integrator #6
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.
Create New Topic
Undisclosed End User #4
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...
Create New Topic
Undisclosed #7
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...
Create New Topic