After SSL certificate is changed under the GRPC configuration, the GRPC server needs to restart. A syslog message will then confirm the restart with a new PID.
The GRPC server restarts on Junos after SSL certificate rotation.
Initial configuration for GRPC:
system { services { extension-service { request-response { grpc { ssl { address 117.1.1.1; port 18100; local-certificate local-cert-1; <--- Existing certificate } max-connections 4; } } }
SSL certificate is rotated and the new GRPC configuration is changed:
system { services { extension-service { request-response { grpc { ssl { address 117.1.1.1; port 18100; local-certificate local-cert-2; <--- New certificate } max-connections 4; } } }
Once the certificate is changed, the GRPC server process on the router will restart in order for the new certificate to take into effect. The following message will appear:
Feb 12 08:00:54.399 router-r1 jsd[703]: %DAEMON-1-JSD_RESTART_ON_CONFIG_CHANGE: Grpc Server will restart for config changes to take effect
Since the JSD restarted, the PID for it will change too:
user@router-r1# run show system processes extensive | match jsd 703 root 20 0 744M 20808K select 1 0:30 0.00% jsd{JSD.EN_US} <-- This is the PID before the certification rotation
user@router-r1# run show system processes extensive | match jsd 17686 root 20 0 744M 20808K select 1 0:30 0.00% jsd{JSD.EN_US} <-- This is the PID after certification rotation