I have remotely restarted h1nds1 via the management port. It look like the machine probably kernel panic'ed. If it happens again today please call me on my cell phone so we can capture the error message before restarting.

From h1nds1 logs, daqd crashed at 11:30PDT Sat morning. It was processing a second-trend request to retrieve 6 hours of data (actually it looks like two identical requests one second apart).

[Sat Jun 25 11:28:59 2016] ->12: start trend net-writer "7000" 1150892875 21600 { "H1:IMC-PWR_IN_OUT_DQ.min" "H1:IMC-PWR_IN_OUT_DQ.max" "H1:IMC-PWR_IN_OUT_DQ.mean" }

[Sat Jun 25 11:28:59 2016] ->23: version

[Sat Jun 25 11:29:00 2016] ->23: revision

[Sat Jun 25 11:29:00 2016] ->23: status channels 3

[Sat Jun 25 11:29:00 2016] connected to 10.22.0.108.22811; fd=32

[Sat Jun 25 11:29:00 2016] ->23: start trend net-writer "7001" 1150892875 21600 { "H1:IMC-PWR_IN_OUT_DQ.min" "H1:IMC-PWR_IN_OUT_DQ.max" "H1:IMC-PWR_IN_OUT_DQ.mean" }

h1fw1 continues to be stable, 1 day 18 hours now.