WP8295 Add 2 channels to DAQ-DMT broadcaster
John Z, Dave:
Two new slow channels were added to h1broadcast0's ini file (H1:GRD-SEI_CONF_STATE_N, H1:GRD-SEI_CONF_STATUS). Change was applied during the DAQ reboot.
WP8296 New Guardian SEI nodes
Jim W, TJ, Dave:
A new H1EPICS_GRD.ini file was created with 115 additional channels for the 5 new nodes (H1:GRD-ISI_HAM[2-6]_BLND).Change was applied during the DAQ reboot.
WP8282 DAQ Reboot
Dave:
Instead of a usual DAQ restart, today I rebooted three DAQ machines which were suseptible to the kernel-2.6.35 208.5+day crash, and which had been running for 202 days. The machines rebooted are: h1dc0, h1tw1, h1broadcast0.
The reconfigure/restart/reboot sequence was:
01. Create the new H1EPICS_GRD.ini file from the Guardian generated H1EDCU_GRD.ini file (FRS13329 was opened for this issue)
02. Generate the new H1EDC.ini file. Verify all new channels exist.
03. Check DAQ for channel duplication errors.
04. h1dc0: turn off monit, kill daqd process (which is not then restarted), reboot h1dc0.
The following steps done while h1dc0 was rebooting:
05. h1edc, restart external edcu with new configuration (num channels increased from 40,549 to 40,664)
05. h1tw1 stop monit, kill daqd process, reboot h1tw0
06. h1broadcast0 stop monit, kill daqd process, reboot h1broadcast0
All reboots took about 5 minutes because after running for 202 days an FSCK was forced.
After h1dc0 started running again, the other DAQ systems which had not been rebooted restarted their daqd normally.
After h1tw1 completed its reboot, its daqd was started normally by monit.
After h1broadcast0 completed its reboot, monit did not restart its daqd process. I had to restart this manually via the monit Web Page.
Number of channels in the DAQ-DMT increased by 2 from 1,428 to 1,430
After 20 mins I renamed the truncated second trend frame files on h1fw[0,1] to force NDS2 to rescan the channel lists.
Decommisioned lockloss virtual machine
Carlos
the virtual machine lockloss was powered down at 11:15PDT.