App Visibility – Receiving “Umask setting 0077 is not supported. Change umask setting to 0022 and restart the installation.” when performing the App Visibility Server 11.3.01 installation on a Linux server

Version 1
    Share This:

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


    PRODUCT:

    TrueSight App Visibility Manager Server


    COMPONENT:

    App Visibility Portal


    APPLIES TO:

    App Visibility Portal 11.3.01 App Visibility Collector 11.3.01 App Visibility Proxy 11.3.01



    PROBLEM:

     

    When performing the App Visibility Server 11.3.01 installation on a Linux server, the “Umask setting 0077 is not supported. Change umask setting to 0022 and restart the installation.” message appears, and cannot continue with the installation.  See the screen shot below for the message:

    User-added image

     


    CAUSE:

    The installation looks for the umask setting of 0022 under the root user


    SOLUTION:

     

    If the App Visibility Server installation is started with a non-root user, but has UID=0 and umask was set to 0022 then the above message will still appear.  To resolve this issue, su to the root user and run the umask command.  If the umask is set to 0077 then change umask from 0077 to 0022 on the root user.
     
    Note: Setting the umask on the root user needs to be permanent change and not just on the bash shell.

    Changing the umask on the command line is not enough.  The default system profile file will need to be changed, and insert the umask command in it. This file is typically /etc/profile on a Red Hat Linux 7.x.

    Here is the default code:

    if [ $UID -gt 199 ] && [ "`/usr/bin/id -gn`" = "`/usr/bin/id -un`" ]; then
        umask 002
    else
        umask 022
    fi

    Comment these lines out, add a line as "umask 0022" and save the file. After installing App Visibility Manager server, restore the file to its original version.

    Then start the App Visibility Manager server installation again, and the message will not appear.

    Note:
    If the above steps still does not resolve the issue then ensure there is no protection in place in the bash_profile that routed root commands through the script command.  If there is a protection then this will modify the output and the system will not be received the expected behavior.  Comment it out, and retry the App Visibility Manager installation.

     


    Article Number:

    000156776


    Article Type:

    Solutions to a Product Problem



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