Originally Posted by Duragrouch

I think the system may be working better. Was up, I went to post, was down, but back up in about 5 minutes or less, HUGE improvement over 5 hours. Before coming back up so fast, I was planning to suggest the following, but this may have already been done:

During the Apollo 11 landing descent from lunar orbit to the surface, the crew had made an error in leaving one of the antennas still receiving, and the landing guidance computer memory filled up, and they'd get this alarm, *** but then the computer rebooted or reset state and continued ***. Several times this happened and in each case, no need to abort landing. This was due to *** fault-tolerant programming ***, a real innovation. The woman (IIRC) who wrote that code for the landing guidance computer was highlighted in a video I saw years ago.

Judging from this most recent DB error and time to correct, the techs may have implemented this solution; Sense overload or too much comm from one source, terminate process, reboot. If so, or other solution, kudos.

Note: During the Blue Screen Of Death era, that was a notable example of NOT having fault-tolerant programming.