Discovery: The Performance > DDD Removal graph is blank

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    BMC Discovery


    COMPONENT:

    BMC Discovery 11.1


    APPLIES TO:

    BMC Discovery 11.1



    PROBLEM:

    Discovery 11.1. The Performance > DDD Removal graph is blank.

    Confirmed that log files had not been deleted, and logging level is set to INFO.
     
    The graph is fed by /usr/tideway/log/tw_ddd_removal_perf.log files and the customer has a full set of these.
     
    Restarting tideway services makes no difference.
     
    None of the other graphs under Performance are affected.

    The customer has localized the timezone on the appliance, and it looks like this:
     
    [tideway@xxxxxx ~]$ date
    Wed May 22 15:09:09 UTC 2017
     
    [tideway@xxxxxx ~]$ more /etc/sysconfig/clock
    ZONE="US/Eastern"
     


    SOLUTION:

    The cause is that RedHat changed the permissions of /etc/localtime so that only the root user can read the file. This can be seen on an appliance where the timezone has been localized. Running "date" as both tideway and root will show different results. 

    The way this affects the DDD Removal graph is that the code that produces the graph is expecting "hour" values of 3, 9, 15 and 21 hours in the log file. For example, before localizing the timezone, the entries look like this: 

    [tideway@myaddm log]$ more tw_ddd_removal_perf.log.2017-05-24 
    2017-05-24 03:00:00,005: DAs in datastore 0, DAs eligible for removal 0, DDD ageing timeout 2419200, pending removal 0 
    2017-05-24 09:00:00,003: DAs in datastore 0, DAs eligible for removal 0, DDD ageing timeout 2419200, pending removal 0 
    2017-05-24 15:00:00,003: DAs in datastore 0, DAs eligible for removal 0, DDD ageing timeout 2419200, pending removal 0 

    After localizing the timezone the values start looking like this: 

    [tideway@myaddm log]$ more tw_ddd_removal_perf.log 
    2017-05-25 01:00:00,004: DAs in datastore 0, DAs eligible for removal 0, DDD ageing timeout 2419200, pending removal 0 
    2017-05-25 07:00:00,005: DAs in datastore 0, DAs eligible for removal 0, DDD ageing timeout 2419200, pending removal 0 
    2017-05-25 13:00:00,004: DAs in datastore 0, DAs eligible for removal 0, DDD ageing timeout 2419200, pending removal 0 

    As the hours do not match the expected values they are ignored. 

    Defect DRUD1-19151 was created. We have raised a case with RedHat but there currently is no ETA for a fix. So a change has been made in the OS upgrade releases (as of March 2017) to make sure the permissions are correct.  

    The workaround is to: 

    1. At the command line, su to root and run: 

    chmod 644 /etc/localtime 

    2. Exit root and restart services: 

    sudo /sbin/service tideway restart 

    3. Wait for new DDD removal data to be logged. Once it does, values should appear on the graph. 






     


    Article Number:

    000136854


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles