Unable to Kill a Process Due to "No Such Process" Error
Processes in a chassis cluster setup have different process IDs for specific nodes (e.g., node0 or node1). If you try to kill a process from the wrong node, you will receive the error message "No such process" because the process is running on a different node, not the one you're currently logged into.Example:
{primary:node1}root@jtac-srx4100-r2025> show system processes extensive |match mib2d22493 root 20 0 761M 23M select 1 2:14 8.00% mib2d14151 root 20 0 763M 36M select 1 2:30 0.00% mib2d
{primary:node1}root@jtac-srx4100-r2025> start shellroot@jtac-srx4100-r2025:~ # kill -9 2249322493: No such processroot@jtac-srx4100-r2025:~ # exit
{primary:node1}root@jtac-srx4100-r2025> request routing-engine login node 0Last login: Wed Dec 11 11:14:27 on ttyu0
--- JUNOS 23.4R2-S3.9 Kernel 64-bit JNPR-12.1-20240604.39c9257_builroot@jtac-srx4100-r2025:~ # cli{secondary:node0}root@jtac-srx4100-r2025>
{secondary:node0}root@jtac-srx4100-r2025> start shellroot@jtac-srx4100-r2025:~ # kill -9 22493root@jtac-srx4100-r2025:~ #