Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[acellier]

    One of our several DCS-930L cameras needed reboot today - it was showing up as a connected wifi device in several utilities, but the camera functions were not operative - a repowering of the camera brought it back.
    This one had been running flawlessly since June 2013 (except for a few Edison outages).

[acellier]

    how very weird - that 930 had last sensed motion at about 5 AM
    Now, a DCS-932L (good since July 2012) has stopped as of about 1130 AM, also while still showing up as a connected wifi device ...
    Guessing that our router firmware upgrade yesterday might have been a factor, I rebooted the router before power-cycling the 932, but the router reboot made no difference. Again, re-powering the camera fixed it.
   We have most of our cameras set for ftp motion detect, and each sending a single email daily as a health indicator - the missing email was the clue that things had changed.
    BUT, why 2 cameras jamming in one day?

[FurryNutz]

What was this router upgrade yesterday?
What model router do you have?

[acellier]

What was this router upgrade yesterday?
What model router do you have?

... NetGear R7000 now at V1.0.3.56_1.1.25

[JavaLawyer]

Does this issue still persist? You can try downgrading your firmware to see if the connectivity stabilizes. Do you have access to a release log that would indicate any changes with potential impact to your network cameras? I'm also presuming that to the best of your knowledge the FW upgrade did not change any existing settings.

[acellier]

All cameras are operating normally today. (7 here, 2 elsewhere)
No logs available to show anything having happened yesterday AM - by rebooting the router (to find that it was not involved) I lost its' log.
It is just so odd that two cameras independently decided to stop functioning, yet stayed connected. And, they were of two slightly different types.
Conspiracy theory - D-Link promoting its' new power control device ...
Solar flare theory - active solar mass ejections at about 0500 and 1100 PDST

[JavaLawyer]

All cameras are operating normally today. (7 here, 2 elsewhere)
No logs available to show anything having happened yesterday AM - by rebooting the router (to find that it was not involved) I lost its' log.
It is just so odd that two cameras independently decided to stop functioning, yet stayed connected. And, they were of two slightly different types.

I'm glad everything stabilized. I encountered a somewhat similar scenario after upgrading the firmware on one of my legacy D-Link routers a year ago. At the time I only had a DCS-932L attached and the camera behaved flaky after the router FW upgrade for about a day before returning to normal.  

Conspiracy theory - D-Link promoting its' new power control device ...

We can also refer to this one as the untimely targeted remotely-activated network destabilization scenario.  

[Popovice]

Conspiracy theory - D-Link promoting its' new power control device ...

I'm just wondering why cannot D-Link include a simple HW based watchdog circuit to all its camera models. Preferably the circuit should be such that you could configure a regular HW reset to the device, e.g. once in a day. Now I'm performing this function with an external AC timer, but I guess that this kind of built-in functionality would not have a significant cost impact to the cameras, but would increase the usability significantly, especially in those cases where the camera is located physically far away or in a difficult to access location.

[JavaLawyer]

I'm just wondering why cannot D-Link include a simple HW based watchdog circuit to all its camera models. Preferably the circuit should be such that you could configure a regular HW reset to the device, e.g. once in a day. Now I'm performing this function with an external AC timer, but I guess that this kind of built-in functionality would not have a significant cost impact to the cameras, but would increase the usability significantly, especially in those cases where the camera is located physically far away or in a difficult to access location.

As you pointed out, this type of change would require a hardware modification which would be extremely costly since we're now talking about modifying the manufacturing process. Although it doesn't help here, D-Link recently added a FW feature "Scheduled Reboot" on the DCS-942L.

[acellier]

    Today we realized that a THIRD DCS-930L stopped working, 2 days back - no correlation with anything. I forgot to check whether it was still showing on the LAN (WiFi), but it had failed to "call in" with an email yesterday morning and again today.
    A power reboot got it going again.
    The 3 cameras that have done this in the last 2 weeks are all registered on mydlink.com - wonder if that is a factor.

[JavaLawyer]

. . . The 3 cameras that have done this in the last 2 weeks are all registered on mydlink.com - wonder if that is a factor.

Two weeks also isn't that far off from when firmware v1.11 was released. . . Correlation? 

[acellier]

    We have not updated to the latest firmware, because when we tried (multiple times) on the first wired camera, it kept still reporting the old version number, so we did not want to corrupt the other cameras.
    Yesterday, a fourth and fifth different camera (DCS-930Ls again) similarly stopped serving the scheduled daily email and will not respond with video. However, they show up for ping, and in the (Mac application) WakeOnLan device list, the iPad Fing app, and the iPad NetGear Genie device list.
    I think this disproves a remote shut-off by mydlink.com, as one of these two 930s has never been registered on mydlink. Of course, when accessed on my Snow Leopard (10.6. Mac, that site keeps nagging me to do the firmware updates. On the other hand, the iOS mydlink+ app works fine, currently seeing 4 out of 5 registered cameras (does not see one which stopped emailing yesterday); iOS does not use Java.
   Power reboot brought these two DCS-930L back to full operation.
   It sure seems odd that the video function quits, while the connectivity function continues, at widely separated times.
   

[acellier]

    About 45 minutes ago, a sixth, different camera (DCS-930L again) similarly stopped in middle of sending an ftp to remote server (as seen by the incomplete jpg stored), and will not respond with video nor accept entry into its' command panels. However, this one also did not show up for ping, nor in the (Mac application) WakeOnLan device list.
   Power reboot brought this DCS-930L back to full operation.
   So very weird ...
  
    I just noticed that in this latest case,  the successful email was at 2014-06-03 16:06:01 then the incomplete ftp jpg was at datetime 2014-06-04-16:07:44 #01  - wonder if maybe the email process was not finished when the cam tried to send the ftp ...

    All but one camera NOT updated to the latest small change firmware.

[acellier]

in the last 2 days, our single DCS-932L and 1 (of) 5 DCS-930L repeated the dysfunctional behavior - could be pinged and seen on the LAN, but not serving their daily email, ftp video, video on request, or management html pages.
A power reboot was required.
We never had this problem prior to the v1.10 firmware update for the 930 (1.08 for the 932).

IS ANYONE ELSE EXPERIENCING THIS?
Many months ago, it seemed many people were, then the problem seemed to have subsided.

[acellier]

And sometime last night, one of the DCS-930L (v1.10 firmware) again went out of service ... noted by failure to send its' daily 11AM email ... while continuing to appear on the LAN as awake and pingable ...