Please login if you have access to particular applications.
Event details
| Voyage: | IN2019_V03 [details] |
| Subject: | UHDAS os150 was found not to be logging |
| When: | 2019-05-22 22:25:40 UTC - entered into Elog/Everlog as 2019-05-22 22:25:40 |
| Log: | in2019_v03 |
| Equipment: | ADCP
75/150 KHz ADCP [view] |
| Position: |
Latitude: -30.5285 Longitude: 110
- entered into Elog as 30 31.71 S, 110 00 E |
| Action: | Reboot |
| The status of os150 was noticed as Red on 11/5/2019@21: | 01 and application restarted but os150 wouldn& 39;t start. A complete reboot of the UHDAS acquisition machine resolved the problem. On restarting, the machine reported a system internal error being encountered. This was reported as /usr/lib/acronis/back&recovery/mms CARSH. Screen shot of the error stored on adcp\tmp. |
| Comments: | The status of os150 was noticed as Red on 11/5/2019@21:56UTC. It appeared that it had encountered an error and had stopped logging on 22/5/2019@11:16:20. The overall data recording was stopped @22:01 and application restarted but os150 wouldn& 39;t start. A complete reboot of the UHDAS acquisition machine resolved the problem. On restarting, the machine reported a system internal error being encountered. This was reported as /usr/lib/acronis/back&recovery/mms CARSH. Screen shot of the error stored on adcp\tmp. |