Bug #21492

Updated by Richard Neswold about 2 years ago

If one driver continually crashes too much (10x, 1 second), the @dev_registry@ dev_registry supervisor tree gives up, dies, and gets restarted by its
supervisor, @daq_sup@. daq_sup. This causes all the device drivers to restart, but they are running in a semi-uninitialized
state because their settings never get downloaded (after this type of restart), so any actions dependent on settings download won't be running.

Example: clx57 Dec 5, 2018, 18:36.

This had happened a couple days earlier also, with the main symptom being that it appeared @T:CDLPID@ T:CDLPID device's settings weren't downloaded. Since its @dpmclient@ it's dpmclient readings depend on the downloaded settings, the @copyset@ copyset app wasn't doing its it's job properly.

It looks like this in the log:

=SUPERVISOR REPORT==== 5-Dec-2018::18:36:32.944666 ===
supervisor: {<0.145.0>,daq_sup}
errorContext: child_terminated
reason: shutdown
offender: [{pid,<0.149.0>},