Hey all, it's been a while because everything has been working great. Still come and read just no posts...
About a week ago the MyMidnite online app stopped recording data. 06-9 at 0212 in the morning. Going to the local status app on the PC it won't hook up either. It has a the correct DYNDNS name/IP address that has been working for months now. It also has the number of the classic above it and says "CONNECTING" but finally goes to "RETRYING" but never hooks up.
The IP has not changed because all the other gizmos that address it still work fine (IP cameras, the Magnum monitor etc.) I've been on the road and would have rebooted the Classic but unfortunately I won't be back for one more week.
Have you seen this before? What do you think happened? What do I need to do to get it going again?
Paul
Quote from: plongson on June 25, 2013, 09:35:39 PM
Have you seen this before? What do you think happened? What do I need to do to get it going again?
TomW has been reporting similar issues recently too. Both of his will (now and then) simply "drop off the network" and not talk to either local-app or mymidnite, but apparently still respond to pings.
His cure has been to powercycle the classic and it comes straight back up. He's going to try unplugging and replugging the network cable next time. When they go offline like this, they seem to stay in that state and not automatically recover.
Thanks Ross, that's what I was thinking too. Problem is, when I 1000 miles away, power cycle is a tough option, LOL. Must just be a bug. I know from my Magnum Monitoring device, the Classic is working fine so I'm not worried. Just an inconvenience.
THANKS!! Paul
Was talking with Tom last night (my time) - and he'd had another network loss on one of his boxes.
He confirmed he could ping the classic, but not connect to it via my utility, or local-app, and that it had stopped sending data to mymidnite.
Tried unplugging the ethernet cable to it and re-plugging. Several times. No good. So while that doesn't make a nice easy reset, it does perhaps give bob/andrew some additional insight to the possible source.
This is just a suggestion, Tom may already have done this...
Last year I had a 150 that just stopped communicating to the local app although I could ping it. Only a power on reset woke it up - until the next time. It was so annoying as I had another 150 same fw etc and it worked much longer but occasionally did hang up too.
I looked at the ethernet signalling with an HP testset and the noise on it was just crazy and at the other end of the 8 metre cat5 cable the situation was even further degraded. It seemed to me that the Classic ethernet just gave up trying to keep comms up.
I connected via 1 metre cat5 cable to a small powered 5 port hub and then the 8 metre cable to the router and the 150 has never went offline since..
Maybe try something similar :)
dgd
Quote from: dgd on June 26, 2013, 07:33:41 PM
This is just a suggestion, Tom may already have done this...
Last year I had a 150 that just stopped communicating to the local app although I could ping it. Only a power on reset woke it up - until the next time. It was so annoying as I had another 150 same fw etc and it worked much longer but occasionally did hang up too.
I looked at the ethernet signalling with an HP testset and the noise on it was just crazy and at the other end of the 8 metre cat5 cable the situation was even further degraded. It seemed to me that the Classic ethernet just gave up trying to keep comms up.
I connected via 1 metre cat5 cable to a small powered 5 port hub and then the 8 metre cable to the router and the 150 has never went offline since..
Maybe try something similar :)
dgd
dgd;
This issues happens to both Classics here and never at same time. Both connect to the same powered ethernet hub then to my router. I am trying some other stuff like disabling the communications with mymidnite. I am convinced it is something to do with ethernet stack or the comms with mymidnite. I really have no need of remote logging so am concentrating on getting local logging sorted out.
Just from here.
Tom
Thanks all for the information. Looks like there is not much to do on my end other than reboot...That'll be next week. THANKS AGAIN
When you are back there maybe you want to turn on Auto Reset (A-RST) in the tweaks enu. It reboots the unit every night at midnight. This was designed for just what you are dealing with. If the Classic is in a remote location and the network hangs this should fix it.
Of course we prefer to fix the bug but Andrew is knee deep into My Midnite at the moment so it will be a few weeks.
Ryan
Thanks Ryan, I will check that as soon as i can. I thought I already had it turned on after some earlier issues a year or so ago, but I'll make sure it's activated.
Paul