Good afternoon, was this problem solved in your box? i have the same problem here
Oct 25 15:20:08 BB-BNG-PE-PAL-PALMARES-MX104-01 /kernel: hw.chassis.startup_time update to 1665672187.422463
------------------------------
Renata Silva
------------------------------
Original Message:
Sent: 01-11-2020 01:28
From: Unknown User
Subject: Syslog Messages | chassisd[2982]: Cannot read hw.chassis.startup_time: No such file or directory
Hi,
I am seeing the below log messages frequently on MX104, Any suggestion why this logs are triggering frequently....
Jan 11 12:50:14 MX104 /kernel: amx_i2cs_refresh_mastership (163501): Refreshing mastership for 0, ore_present = 16
Jan 11 12:55:15 MX104 /kernel: amx_i2cs_refresh_mastership (163801): Refreshing mastership for 0, ore_present = 16
Jan 11 13:00:16 MX104 /kernel: amx_i2cs_refresh_mastership (164101): Refreshing mastership for 0, ore_present = 16
Jan 11 13:03:03 MX104 /kernel: hw.chassis.startup_time update to 1578562909.001378
Jan 11 13:05:17 MX104 /kernel: amx_i2cs_refresh_mastership (164401): Refreshing mastership for 0, ore_present = 16
Jan 11 13:10:19 MX104 /kernel: amx_i2cs_refresh_mastership (164701): Refreshing mastership for 0, ore_present = 16
Jan 11 13:15:20 MX104 /kernel: amx_i2cs_refresh_mastership (165001): Refreshing mastership for 0, ore_present = 16
Jan 11 13:20:21 MX104 /kernel: amx_i2cs_refresh_mastership (165301): Refreshing mastership for 0, ore_present = 16
Jan 11 13:25:23 MX104 /kernel: amx_i2cs_refresh_mastership (165601): Refreshing mastership for 0, ore_present = 16