Workaround 1

Increase the SendBufferSize value in SAS Web Server httpd.conf file, as follows:

  1. Stop the SAS Web Server with this command:

    /opt/sasinside/sasconfig/Lev1/Web/WebServer/bin/httpdctl stop

  2. Make a backup copy of the httpd.conf file that resides in the /opt/sasinside/sasconfig/Lev1/Web/WebServer/conf/ directory.

  3. Locate the SendBufferSize value in the httpd.conf file and increase the value, as shown in this example:

    SendBufferSize 16384 to SendBufferSize 65536

  4. Start the SAS Web Server with this command:

    /opt/sasinside/sasconfig/Lev1/Web/WebServer/bin/httpdctl start

  5. Clear the browser cache and run your browser in private mode to ensure that no other cache-based items remain when you try to access the web applications in the browser. Note: Each browser has a different option you select to run in private-browse mode. For example, in the Google Chrome browser, you initiate private browsing by opening an Incognito window. In the Mozilla Firefox browser, you select an option called Private Browsing.

  6. If setting the SendBufferSize parameter to 65536 does not help, try to set it to a higher value (for example,128000) in the httpd.conf file and repeat steps 1-5 above.

Workaround 2

Delete the cacheroot folder in SAS Web Server, as follows:

  1. Stop the SAS Web Server with this command:

    /opt/sasinside/sasconfig/Lev1/Web/WebServer/bin/httpdctl stop

  2. Navigate to the WebServer directory by submitting the following command:

    cd /opt/sasinside/sasconfig/Lev1/Web/WebServer

  3. Save the original contents by just renaming the directory, as shown in this example:

    mv cacheroot cacheroot.sav

  4. Create a cacheroot directory:

    mkdir cacheroot

  5. Start the SAS Web Server with this command:

    /opt/sasinside/sasconfig/Lev1/Web/WebServer/bin/httpdctl start

  6. Clear the browser cache and run your browser in private mode to ensure that no other cache-based items remain when you try to access the web applications in the browser. Note: Each browser has a different option you select to run in private-browse mode. For example, in the Google Chrome browser, you initiate private browsing by opening an Incognito window. In the Mozilla Firefox browser, you select an option called Private Browsing.

Workaround 3

Place comment delimiters around the mod_cache module in the SAS Web Server sas.conf file, as follows:

  1. Stop the SAS Web Server with this command:

    /opt/sasinside/sasconfig/Lev1/Web/WebServer/bin/httpdctl stop

  2. Make a backup copy of the sas.conf file that resides in the /opt/sasinside/sasconfig/Lev1/Web/WebServer/conf/ directory.

  3. Locate the mod_cache module in the sas.conf file and add comment delimiters around the module, as shown in this example:

    #<IfModule mod_cache.c>
    # <IfModule mod_disk_cache.c>
    # CacheRoot "/opt/sasinside/sasconfig/Lev1/Web/WebServer/cacheroot"
    # CacheEnable disk /SASTheme_default
    # CacheEnable disk /SASFlexThemes
    # CacheDirLevels 5
    # CacheDirLength 3
    # </IfModule>
    #</IfModule>

  4. Start the SAS Web Server with this command:

    /opt/sasinside/sasconfig/Lev1/Web/WebServer/bin/httpdctl start

  5. Clear the browser cache and run your browser in private mode to ensure that no other cache-based items remain when you try to access the web applications in the browser. Note: Each browser has a different option you select to run in private-browse mode. For example, in the Google Chrome browser, you initiate private browsing by opening an Incognito window. In the Mozilla Firefox browser, you select an option called Private Browsing.

Workaround 4

Reboot the middle-tier RHEL 7.6 machine into the previous kernel 3.10.0-957.21.2.el7.x86_64 or into an earlier RHEL 7.6 kernel (where the problem does not occur). You can do that by using the GRUB boot menu (without rolling back the patch or removing the problematic kernel.)

Workaround 5

Roll back the applied operating-system patch.