Description

This article provides information on "CHASSISD_HOST_TEMP_READ: Error reading host temperature sensor" messages.

Symptoms

In RE(routing-engine) busy state by some reason, "CHASSISD_HOST_TEMP_READ: Error reading host temperature sensor" message may be seen even it comes from temporal single event. Chassisd sometimes reports continues these messages in messages logs but there is not chassis alarm is observed.

Log example;
Aug 10 12:10:00.980 20XX  Router chassisd[xxxxx]: CHASSISD_HOST_TEMP_READ: Error reading host temperature sensor
Aug 10 15:25:02.720 20XX  Router chassisd[xxxxx]: CHASSISD_HOST_TEMP_READ: Error reading host temperature sensor
Aug 12 05:10:04.982 20XX  Router chassisd[xxxxx]: CHASSISD_HOST_TEMP_READ: Error reading host temperature sensor


Usually, the above error message is accompany with "ichsmb0: device timeout" and "SMB read/write failed" messages.
However, even if the following messages happen the above error message is not always generated.

kernel: ichsmb0: device timeout, status=0x40
kernel: SMB read failed xxxxxx / kernel: SMB write failed xxxxxx

Solution

There is no functional impact but it may be happen coincidental reading failure and error message will be displayed unnecessary. Retry mechanism for raising error message is implemented from PR1615863 and messages caused by transient error is reduced.

Not all commits trigger the message, but as a trend, it is easy to generate it during committing.

The message is transient and informational. It is seen occasionally and system is able to read this device on the next iteration. So, basically the message can be ignore safely.

Please note, PR1615863 ​​​​​​​ doesn't purpose to suppress messages completely. Almost all messages can be considered transient error message but, in rare case, real hardware issue can be considered.

Regardless of Junos releases pre or post PR1615863 ​​​​​​​, please try rebooting chassis when the error messages can be seen so frequently. If rebooting doesn't help to resolve the issue, please open a JTAC case to investigate any hardware failure of the components.

 

 

Modification History

05/30/2023 - Initial draft
12/08/2023 - Update