Description

This KB article explains how to resolve "error: the chassis-control subsystem is not responding to management requests" messages.

Symptoms

Following error is seen when trying to run "show chassis" commands

user@hostname> show chassis hardware
error: the chassis-control subsystem is not responding to management requests

user@hostname> show chassis power
error: the chassis-control subsystem is not responding to management requests

CPU Utilisation of chassisd process
  
user@hostname> show system processes extensive no-forwarding

last pid: 23035;  load averages:  1.10,  1.18,  1.22  up 454+14:20:04    03:42:36
379 processes: 7 running, 343 sleeping, 1 zombie, 28 waiting

Mem: 778M Active, 7813M Inact, 1304M Wired, 440M Buf, 5997M Free
Swap: 8192M Total, 8192M Free


  PID USERNAME PRI NICE   SIZE    RES STATE   C   TIME    WCPU COMMAND
26280 root      99    0   856M 77888K CPU1    1 944.4H  88.67% chassisd{chassisd} >> high cpu
   11 root     155 ki31     0K    64K RUN     0    ???  84.28% idle{idle: cpu0}
From process output, we can see that CPU utilisation is high for chassisd process. Due to this, chassisd might not be responding to any queries.

 

Solution

When the I2C bus gets stuck, the chassisd daemon might get stuck and become unresponsive. If you issue a chassisd-related show command, the command returns an error message: error: the chassis-control subsystem is not responding to management requests.

This error just means that chassisd is not running and is in the problematic condition.

In order to resolve this issue,restart the chassis management process. You can use the below command  
user@host> restart chassis-control

If the above step doesn't work, note the process for which the CPU utilization is high [In the above case chassisd process at 88.67%]. In such cases, it is important to restart the process in order to re-initiate its functioning.

Caution: The process must be restarted during a Maintenance Window. 

Steps to Restart:

user@host>start shell user root %kill -9 26280 ---> 26280 indicates the PID as obtained from the system processes output.

  • After the above step is performed, confirm whether the process has respun by running the "show system processes extensive | match chassisd" command.
  • Contact Support if you observe any discrepancies. 
In case restarting the process doesn't work please reboot the respective Routing engine in a scheduled Maintenance window and check if the issue resolves.

For further assistance ,reach out to Support for analysis. Collect the following output information before opening a case for faster analysis: 
> show log messages
> request support information | no-more
> show krt queue
> show krt state
>start shell

Modification History

2024-02-29 : Article Created

Related Information

https://www.juniper.net/documentation/us/en/software/junos/cli-reference/topics/ref/command/restart-chassis-control.html