Reports 1-1 of 1 Clear search Modify search
DGS (General)
takahiro.yamamoto - 17:01 Monday 27 July 2026 (37272) Print this report
Upgrade of ca-gateway server
The new ca-gateway server prepared in klog#37249 was deployed.
Detailed information about the server construction can be found in JGW-T2617453.

A ca-gateway process is now managed by systemd + journald, so it can be operated by
systemctl {start|stop|restart|...} ca-gateway.service
journalctl -u ca-gateway.service


Now following logs are recorded but it doesn't seem to be an issue on ca-gateway.
Jul 27 15:17:19 k1epics start-ca-gateway.sh[1031]: Jul 27 15:17:19 gateServer::exCB: Channel Access Exception:
Jul 27 15:17:19 k1epics start-ca-gateway.sh[1031]: Channel Name: Unavailable
Jul 27 15:17:19 k1epics start-ca-gateway.sh[1031]: Native Type: Unavailable
Jul 27 15:17:19 k1epics start-ca-gateway.sh[1031]: Native Count: 0
Jul 27 15:17:19 k1epics start-ca-gateway.sh[1031]: Access: Unavailable
Jul 27 15:17:19 k1epics start-ca-gateway.sh[1031]: IOC: Unavailable
Jul 27 15:17:19 k1epics start-ca-gateway.sh[1031]: Message: Identical process variable names on multiple servers
Jul 27 15:17:19 k1epics start-ca-gateway.sh[1031]: Context: Channel: "K1:PICO-TEST_4_POSITION", Connecting to: k1script0.kagra.icrr.u-tokyo.ac.jp:34571, Ignored: k1script0.kagra.icrr.u-tokyo.ac.jp:42879
Jul 27 15:17:19 k1epics start-ca-gateway.sh[1031]: Requested Type: TYPENOTCONN
Jul 27 15:17:19 k1epics start-ca-gateway.sh[1031]: Requested Count: 0
Jul 27 15:17:19 k1epics start-ca-gateway.sh[1031]: Source File: ../cac.cpp
Jul 27 15:17:19 k1epics start-ca-gateway.sh[1031]: Line number: 1297


According to Ikeda-san's check, it comes from duplicated launching of pcas process by each application
and he will fix it on a future maintenance day.

Anyway, the ca-gateway server was upgraded properly from expired OS to modern one.
Comments to this report:
satoru.ikeda - 14:34 Monday 03 August 2026 (37309) Print this report

K-Log#37272

According to Ikeda-san's check, it comes from duplicated launching of pcas process by each application and he will fix it on a future maintenance day.

Two PCAS server instances were being launched for each device, so I removed the redundant server instance.
The affected devices are Picomotor, Stepper (VIS and CRY), and Traverser.
I verified that Picomotor and Stepper (VIS) are working properly. The code for Stepper (CRY) and Traverser has also been updated. 
Their operation will be verified the next time they are used.

[Before]

class PcasServer(pcaspy.SimpleServer):
    def __init__(self, prefix, driverIP):
        super(PcasServer, self).__init__()  # Creates the first instance 
        self.server = pcaspy.SimpleServer()  # Creates the second instance

[After]

class PcasServer:
    def __init__(self, prefix, driverIP):
        self.server = pcaspy.SimpleServer()
Non-image files attached to this comment
Search Help
×

Warning

×