Security

 View Only
last person joined: 4 days ago 

Ask questions and share experiences with Juniper Connected Security. Discuss Advance Threat Protection, Policy Enforcer, SecIntel, Secure Analytics, Secure Connect, Secure Director and all things related to Juniper security technologies.

  • 1.  Syslog Messages | chassisd[2982]: Cannot read hw.chassis.startup_time: No such file or directory

    Posted 10-10-2017 03:44

    Hi all,

     

    I'm getting the following message on one of my ACX2100's.

     

    chassisd[2982]: Cannot read hw.chassis.startup_time: No such file or directory

     

    Firmware: 16.2R1.6

     

    I can't seem to find any information online regarding this. Does anyone know why the error is showing in the logs?



  • 2.  RE: Syslog Messages | chassisd[2982]: Cannot read hw.chassis.startup_time: No such file or directory

    Posted 10-10-2017 05:13

    Hi,

     

    This is a cosmetic bug which is non-impacting. Do you see any impact due to these log messages?

     

    https://prsearch.juniper.net/InfoCenter/index?page=prcontent&id=PR1092711

     

     



  • 3.  RE: Syslog Messages | chassisd[2982]: Cannot read hw.chassis.startup_time: No such file or directory

    Posted 10-11-2017 01:33

    Nope, there is no actual impact. Just seeing hundred's of entires for it.

     

    Hopefully just a bug that gets resolved at some point



  • 4.  RE: Syslog Messages | chassisd[2982]: Cannot read hw.chassis.startup_time: No such file or directory

    Posted 10-11-2017 01:39

    ok..

    You can supress those log messages if you want

     

    set system syslog file messages match "!(Cannot read hw.chassis.startup_time)"

     

    HTH



  • 5.  RE: Syslog Messages | chassisd[2982]: Cannot read hw.chassis.startup_time: No such file or directory

    Posted 01-11-2020 01:29

    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



  • 6.  RE: Syslog Messages | chassisd[2982]: Cannot read hw.chassis.startup_time: No such file or directory

    Posted 10-25-2022 20:08 
    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