{"action":"opened","issue":{"url":"https://api.github.com/repos/tessel/t2-firmware/issues/227","repository_url":"https://api.github.com/repos/tessel/t2-firmware","labels_url":"https://api.github.com/repos/tessel/t2-firmware/issues/227/labels{/name}","comments_url":"https://api.github.com/repos/tessel/t2-firmware/issues/227/comments","events_url":"https://api.github.com/repos/tessel/t2-firmware/issues/227/events","html_url":"https://github.com/tessel/t2-firmware/issues/227","id":214234309,"number":227,"title":"Firmware slowdown/halt on long-running Tessel 2","user":{"login":"rungkutta","id":3440368,"avatar_url":"https://avatars2.githubusercontent.com/u/3440368?v=3","gravatar_id":"","url":"https://api.github.com/users/rungkutta","html_url":"https://github.com/rungkutta","followers_url":"https://api.github.com/users/rungkutta/followers","following_url":"https://api.github.com/users/rungkutta/following{/other_user}","gists_url":"https://api.github.com/users/rungkutta/gists{/gist_id}","starred_url":"https://api.github.com/users/rungkutta/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rungkutta/subscriptions","organizations_url":"https://api.github.com/users/rungkutta/orgs","repos_url":"https://api.github.com/users/rungkutta/repos","events_url":"https://api.github.com/users/rungkutta/events{/privacy}","received_events_url":"https://api.github.com/users/rungkutta/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-03-14T23:12:37Z","updated_at":"2017-03-14T23:12:37Z","closed_at":null,"body":"## The Setup\r\nI some Tessel 2s running an app that does three things:\r\n* Read an I2C temperature sensor attached to Port B every 2 seconds\r\n* Host an Express web server that serves the temperature reading in JSON format\r\n* Blink LED 2 and 3 back and forth as a visual status indicator.\r\n\r\nThe Tessels are connected by wifi to an access point.  They are set up with a static IP address on the local network.  Another computer on the network does an HTTP GET on each Tessel every five minutes to read the temperature.\r\n\r\n## The Problem\r\nTwo Tessels have been running this way for 3+ months with no issues.  However, a third one, with exactly the same software, seems to run for only 1-2 weeks before quitting.  A power cycle will bring it back, but it will then quit again after a week or two.  I have replaced this board with a brand new one, running the same software, but it showed the same problem.\r\n\r\nWhen I say \"quit,\" I mean that the app either stops running, or the whole board slows down so much that it's unresponsive (my blinking status lights stop, and the HTTP GET requests timeout).  I don't think the firmware crashes, because I can occasionally still ping it (maybe 1/100 succeed).  I am not able to SSH into the board in this state.\r\n\r\nThe only difference I can think of between the three boards is that the one that quits is located furthest from the access point, and has the weakest wifi signal strength.  It's not terrible, just worse than the other two, and network connectivity to it seems fine after a reboot.  The fact that a replacement board in the same location showed the same type of failure is suspicious.\r\n\r\n## Ideas?\r\nAny ideas on where to look to troubleshoot this?  Inability to SSH and the long time before failure makes it tough.  Starting the project, I wasn't sure what to expect regarding how long I could realistically run these, but I've had great results with a few of the boards.  \r\n\r\nIs there any sort of watchdog functionality on the Tessel 2 that could reset it if an app crashes?  If not, I've considered periodically running a `Tessel.reboot()` to see if that helps - but I'd hate to do that without looking for a better solution.\r\n\r\nThanks much.\r\n\r\n\r\n\r\n"}}
{"actor":{"display_login":"rungkutta"}}