h1daqfw0 crashed during the daq restart while trying to load metadata.  Log output for the service showed a panic on an out of range request.

Sep 01 11:13:10 h1daqfw0 daqd_rs[10370]:  - going to request channel list update
Sep 01 11:13:10 h1daqfw0 daqd_rs[10370]: attempting to load metadata from /opt/rtcds/lho/h1/daq0/running/master
Sep 01 11:13:11 h1daqfw0 daqd_rs[10370]: loaded metadata from /opt/rtcds/lho/h1/daq0/running/master, it took 1.0284032s
Sep 01 11:13:11 h1daqfw0 daqd_rs[10370]:  - going to request channel list update
Sep 01 11:13:11 h1daqfw0 daqd_rs[10370]: attempting to load metadata from /opt/rtcds/lho/h1/daq0/running/master
Sep 01 11:13:12 h1daqfw0 daqd_rs[10370]: thread 'dq_input' (10428) panicked at ifo_stream/src/data_store.rs:527:13:
Sep 01 11:13:12 h1daqfw0 daqd_rs[10370]: available range is [0..245944), requesting [245944..245948) IFOChannel { name: "H1:DAQ-DAQSTAT_FW_SECOND_FRAME_GPS_STATUS", dcu_id: 52, ifo_id: 0, data_type: Float32, seq_num: 237380, ch_num: 0, data_rate: 16, bytes_per_cycle: 4, offset: 245944, test_point_dcu: None, acquire: 1, signal_gain: 1.0, signal_slope: 6.1028e-5, signal_offset: 0.0, units: "V" }
Sep 01 11:13:12 h1daqfw0 daqd_rs[10370]: note: run with 'RUST_BACKTRACE=1' environment variable to display a backtrace

A restart of the rts-daqd_rs service restored the server to normal operation.