Dcm problems March2013 » History » Version 24
Dcm problems March2013¶
DCM "hard" failures.¶
DCMs that can never be contacted.
|DCM||First reported by||Date first reported||Occurrences||Comments||Resolution|
DCMs that can be contacted for some amount of time before they seize.
- Please use the full dcm name in the table below, to aid searching.
- The "Occurrences" count is the number of confirmed times the problem has occurred. It may well be greater...
|DCM (location)||DCM (S/N)||First reported by||Date first reported||ECL Entries||Occurrences||Comments||Resolution|
|dcm-2-01-03||dcm-1143||Peter||3/8/13||800 802 808||2||Andrew noted it was using it's SN name on 3/8/13|
|dcm-2-01-08||dcm-1039 (?)||Peter||3/8/13||800 801||1||Seems to have recovered.|
|dcm-2-03-02||dcm-1225||Peter||3/8/13||800 802 819||2||Hung after starting ssh daemon|
|dcm-2-03-03||dcm-1227||Peter||3/8/13||800 802||2||Doesn't seem to finish reboot (Andrew)|
|dcm-2-03-06||?||?||Not included in partition since 2/20/13, but no comment why in ECL.|
|dcm-2-03-09||dcm-1222||Peter||2/18/12||Problems were general network/DDS issues. Not clear there is a problem with this DCM.|
|dcm-2-04-10||Peter||3/8/13||810||1||Hung during ps/grep command|