Stopped sending sensor data to Telldus Live after running for about 2 weeks #2
Comments
|
You didn't happen to restart telldusd (perhaps due to a upgrade) around
|
|
No, I didn't do anything knowingly on that system. TelldusService (I suppose that's what you mean) is still running. By the way, I still haven't restarted neither TelldusService nor tellive_core_connector if you wan't me to try something. |
|
FWIW, simply stopping and restarting tellive_core_connector solved the 18 mar 2014 kl. 20:26 skrev Erik Johansson notifications@github.com: You didn't happen to restart telldusd (perhaps due to a upgrade) around
Reply to this email directly or view it on |
|
Which version of tellive are you using? |
|
tellcore-py 1.0.3 19 mar 2014 kl. 19:54 skrev Erik Johansson notifications@github.com:
|
|
Which version of Telldus Core are you using? |
|
TelldusCenter 2.1.2, if that's what you mean. I believe that's what provides TelldusCore to the mac. It's the only telldus application I have installed besides tellcore-py and tellive-py. |
|
Yes, exactly. Since you're using 2.1.2 it isn't the problem I suspected... The only thing I can think of now is to run with debug (-d or set debug option in config), reproduce and see if that gives any clue. |
|
OK, done. Will report back with any findings. 19 mar 2014 kl. 06:43 skrev Patrik Kempe patrik.kempe@gmail.com:
|
|
Now it has happened again. At approximately midnight last night Telldus Live stopped receiving updates (their website has the last report timed to 00:06). Since I've run tellive-py in debug mode, here's the log from just after midnight to now (before that there's nothing suspicious from what I can tell): After that it's just ping/pong every two minutes until right now. Other than timeouts with the server, I should mention that I changed ISP Friday, meaning that no values could be reported during a few hours before noon, and also that my previous ISP was a bit flaky w/r/t stability from time to time (implicating it might have affected the previous crash as well). Please also note:
|
|
This is very strange. Something should be sent to the server at least once every two minutes (ping). And if nothing is received within six minutes (pong), the client should disconnect and connect again. But after midnight it takes almost 3.5 hours before the client times out. Then, as you mentioned, it takes another 3.5 hours before reconnecting. After searching the web a bit it might be caused by the App Nap feature in OS X 10.9. Please see ipython/ipython#4431 for ideas on how to check for app nap and how to disable it. |
|
Can you try installing https://pypi.python.org/pypi/appnope and then run with the latest version of tellive-py? |
|
Can I upgrade to the new version through pip install --upgrade or do I need to checkout from github? 25 mar 2014 kl. 08:59 skrev Patrik Kempe patrik.kempe@gmail.com:
|
|
You need to get it from github. |
|
Updated and checked that your latest change exists, rebooted now. Now we wait two weeks… 8 apr 2014 kl. 20:37 skrev Erik Johansson notifications@github.com:
|
|
Can you check the activity monitor and verify that app nap is off for the process? |
|
I was trying to do that before, but unfortunately since I launch it as a I do still keep the debug logging, so at least I'll see if the Ping/pongs 8 apr 2014 kl. 21:19 skrev Erik Johansson notifications@github.com: Can you check the activity monitor and verify that app nap is off for the Reply to this email directly or view it on |
|
Now that the app has been running some time, I checked the logs. There are occasional disconnects, but this time the app reconnects after the advertised delay (a number of seconds). I think I would've seen the error by now if it still was an issue. |
|
Great. Thanks for confirming the fix. |
tellive_core_connector was launched correctly on system boot February 28 and has correctly reported sensor data and been able to remote control switches as expected. On March 17 at 18:35 CET (i.e about 17 days later) it stopped reporting sensor data and Telldus Live now reports the location as offline.
I have looked for error messages in the system logs, but haven't found anything. The python process is still running, nothing appears out of the ordinary.
System is Mac OS X 10.9.2.
The text was updated successfully, but these errors were encountered: