Around UTC0:00 (9:00 JST) today, the GPS got into trouble as shown in Figure 1. Because of this trouble, some applications such as ndscope could not be used.

Michimura-kun guessed

• the leap data cached from IETF page is in /usr/share/zoneinfo/leap-seconds.list, and this file says, "File expires on 28 December 2024".
• Since there is no leap seconds after 2017, and we can just update the expiration timestamp Or update leaps.py (gpstime) with the latest file?

He also found the messages, "ietf.org is no longer serving this file. Use https://data.iana.org/time-zones/data/leap-seconds.list instead." Oshino-kun also said, "Maybe we only need to update tzdata package to update leap-seconds.list file.". However, a careful manner seems to be necessary for the simultaneous update of the GPS file for all servers, and it used to be done by only YamaT-san. 

As an emergency measure, we decided to update the GPS file only in k1ctr0 in the DAB control room to use this server as a remote desktop server from the KAGRA site for today's activities, and Oshino kun performed the attached command for the update. Then ndscope could be active in this server.

Of course, we need the GPS file update for all servers.