The operation performed on the hardware database was unsuccessful. Normally the system will initiate a fix automatically.
When a CHASSISD_HWDB_ERROR event occurs, a message similar to the following is reported:
chassisd: CHASSISD_HWDB_ERROR: hwdb call hwdb_picinfo_inst_iter_start failed, pic 709, error No such attribute
Chassis control process: CHASSISD_HWDB_ERROR: hwdb call hwdb_open_db failed, pic 0, error No such file or directory
This is an internal log message which is corrected by the internal database. A change was made and new ifds (interface identifications hardware database is updated) are added and old ones removed. The message CHASSISD_HWDB_ERROR means this change failed, but an internal action then corrects this change. These messages pose no impact as the error is detected and resolved.
Examine the following outputs to help determine the cause of this message:
show log messages
show log chassisd
show tnp addresses
Look for any related events that occurred at or just before the CHASSISD_HWDB_ERROR message in the log messages and chassisd outputs.
Perform these steps:
- If the message appeared in connection with a commit, upgrade, or Routing Engine Failover due to GRES, this event can be expected as certain PICs (i.e. IQE PICs are not supported in some Junos builds) may need to be restarted. Service PICS will always need to be restarted on such events.
- During a maintenance window, as it will impact transit traffic, try reseating the associated FPC/PIC units, or move these to other slots.
- If the log messages continue, open a case with your technical support representative to investigate the issue further.