=> I rebooted it and ALS models seemed to come back online. It is necessary to check that IFO lock can be recovered because unusual lockloss occurred due to a hang-up of a front-end computer.
- k1fw0 hung up around 2am.
=> I rebooted it and OS comes back but some network interfaces didin't come back yet. I'm still checking it.
- DGS wi-fi and also wired network at some location are unavailable maybe around 14:00?
=> I haven't check it. It interrupts an investigation above problems.
> - k1fw0 hung up around 2am.
> - DGS wi-fi and also wired network at some location are unavailable maybe around 14:00?
Unfortunately, these two were caused by a hang-up of k1boot.
Because k1als0 came back without any PXE and NFS troubles, k1boot was alive at least until 13:52. When I rebooted k1fw1 around 14:02, an NFS related trouble occurred. So k1boot downed between 13:52 - 14:02.
Anyway, I rebooted k1boot from the BMC interface and fortunately it comes back online without any problem. Commissioning works are not expected to be affected by this issue for now. But it might be better to shutdown once and to re-launch whole real-time system. (It would be better to be done when Ikeda-san or Oshino-san are present because we may need to split into center and end stations.)
History is as follows.
~2:00 k1fw1 hung up
13:23 k1als hung up
13:52 k1als came back
13:53-14:01 k1boot hung up
14:02 k1fw1 came back incompletely
14:50 k1boot came back
14:55 k1fw1 came back
Fig.1 represents a internal clock of k1iopals0 and shows that this clock stop to increment at a hang-up time of k1als0.
Fig.2-4 are the mesages on the console of k1als0, k1fw1 and k1boot when they have hung up.
