I have 3 Yuns. One of the older ones has been running non-stop for the past 5 years in a very hot garage. It monitors water use and ultimately provides graphs of usage to about 10 second time intervals.
Probably not many people care about Yun, given it has been obsolete for a long time now, but anyway...
After all this time (5 years), it started throwing socket errors on localhost, 5700, related to Bridge activity.
The s/w is fairly fault tolerant. There is a manager process that kills and restarts anything that seems to be a miss. Typically, though, this only happened very infrequently. In 5 years, I rebooted the Yun probably twice because it stalled, plus the one time that a rodent ate the sensor cable outside.
Now it is hitting the socket issue all the time. It runs for about a day, and once the error triggers, none of the auto-clobber and restart seems to fix it. In the past, this would have been handled transparently by the manager. Power cycling works, but isn't a useful option here.
I thought maybe a h/w problem. So I coded up the other Yun, but it did the same thing. Hum... 5 years without an issue on one, and now both have the same issue today. The Yun does not have access to the outside world, so it could not have updated itself -- and the package manager doesn't seem to work anymore anyway.
Any creative thinkers out there as to how this might happen? Old as Yun is, I would like it to continue to run, as I find the program particularly useful -- and the Yun can literally take the heat. None of the suggested replacements seems to quite fit the bill.