This article describes the "shmp_client_get_id_cb: Error getting client id. status: 1" error that is seen continuously in logs and indicates what must be done to resolve the error.

The following errors are continuously seen in the logs:

Dec 13 22:44:26  JTAC last message repeated 2 times
Dec 13 22:44:46  JTAC sdk-vmmd[1593]: %DAEMON-3: shmp_client_get_id_cb: Error getting client id. status: 1
Dec 13 22:45:06  JTAC sdk-vmmd[1593]: %DAEMON-3: shmp_client_get_id_cb: Error getting client id. status: 1
Dec 13 22:45:26  JTAC sdk-vmmd[1593]: %DAEMON-3: shmp_client_get_id_cb: Error getting client id. status: 1
Dec 13 22:45:46  JTAC sdk-vmmd[1593]: %DAEMON-3: shmp_client_get_id_cb: Error getting client id. status: 1
Dec 13 22:46:26  JTAC last message repeated 2 times

The app-engine information shows the default-node as offline.

{master:0}
user@JTAC> show app-engine information
Compute cluster: default-cluster
  Compute node       Model           Kernel release                 Machine    Management IP
  default-node      --- Offline ---                                            192.168.1.1/24

{master:0}
user@JTAC> show app-engine crash
Compute cluster: default-cluster

  Compute node: default-node
  --- Offline ---

No new logs are seen in the vehostd (host shell logs) after the compute node goes offline.

The system may log the above errors in some scenarios after commit/reboot.

SHMP stands for SDK Host Management Protocol and is used for communication between the Junos and Host OS over TCP. It indicates that the message/response that was received from the hostd has an error and hence the above error is seen. This error message has no impact on the functionality of the node.

To resolve the issue, configure the default compute-node to bring it online.

#set services app-engine compute-cluster default-cluster compute-node default-node hypervisor