DGS (General)takahiro.yamamoto - 18:28 Thursday 11 June 2026 (37062)
Print this reportRe-trying upgrade of k1scriptk1script was upgraded to the new system in klog#36519. But some scripts depending on instruments in the old PICO network didn't work well (see also klog#36789 and klog#36987). So one of script servers were downgraded and problematic scripts were moved to it in klog#36803. This work is not a final solution but we could avoid this issue by changing network settings on the script servers which is a temporal solution until removing the old PICO network. Now all scripts are running on the new script server again.
Though this issue comes from a bad design of some of site networks such as the old PICO network, it cannot be fixed soon because VLAN settings and/or cabling work are required. So I tried to apply a temporal network configuration on the script servers and was able to avoid this issue. Detailed settings can be seen in JGW-T2617213. After changing the network configuration, I could confirm the picomotor drivers in the old PICO network work well on the new script servers. So all downgraded scripts were moved to the new system again and they are now running on the k1script0.
Comments to this report:
takahiro.yamamoto - 17:05 Saturday 13 June 2026 (37068)
Print this reportAll scripts were moved to k1script0, so k1script1 was upgrade to the new OS again. Now all user process were running on k1script0. Some of them will be moved to k1script1 for balancing CPU load.