adaptershim log(arcotadaptershim.log) file not generated on Policy server
search cancel

adaptershim log(arcotadaptershim.log) file not generated on Policy server

book

Article ID: 207026

calendar_today

Updated On:

Products

CA Advanced Authentication - Strong Authentication (AuthMinder / WebFort) CA Advanced Authentication CA Strong Authentication

Issue/Introduction

When trying to access a protected resource, SHIM library is loaded but the arcotadaptershim.log file is not generated on the Policy Server machine in <ARCOT_HOME>/logs folder.

Environment

Release : 9.1.x

Component : Symantec Strong Authentication (Arcot WebFort)

Resolution

Here are the few reasons which can cause the log file not to generate:

  1. The user starting the Policy Server does not have access to the ARCOT_HOME/logs directory to write the logs.

  2. Specify the absolute path for parameter Param1=LOG_FILE_NAME=ARCOT_HOME/logs/arcotadaptershim.log in adaptershim.ini and specify the path where Policy Server is writing logs and check if that works.

  3. In adaptershim.ini file, look for ParamSupported=3 and make sure that there are 3 Param1/2/3 configured else log file will not be generated. If any of the parameters are duplicate for Param1/2/3 that will also cause this issue because now there are 4 Param but it is configured to only have 3 parameters. Here is the section of the adaptershim.ini file referenced.

    # "ParamSupported" property specifies the count of parameters to pass to the
    # logging object. This will depend on the specific logging object and what
    # it needs to know.
    ParamSupported=3

    # Param<M> specifies a parameter in name=value format.

    # "LOG_FILE_NAME" specifies the name of the log file. You can provide a complete
    # path or a relative path with ARCOT_HOME. In the later case, ARCOT_HOME will be
    # substituted with the installation directory that is fetched from the environment
    # variable. For example, for Win32 "LOG_FILE_NAME=D:\My Documents\arcotadaptershim.log"
    # or for Unix "LOG_FILE_NAME=/usr/spool/logs/arcotadaptershim.log"

    # LOG_FILE_NAME is for the ArcotLog2File logger. You can change the
    # location and names of the log file by updating this value.
    Param1=LOG_FILE_NAME=ARCOT_HOME/logs/arcotadaptershim.log

    # "LOG_FILE_ROLLOVER_INTERVAL" property specifies how often you want the log file to
    # rollover to the backup file. The values recognized are HOURLY, DAILY,
    # WEEKLY, and MONTHLY. DAILY results in the file rolling over when the first
    # log message is received after midnight. The time check is
    # based on the logged time. By default, the local time zone is used for
    # logging.
    Param2=MAX_LOG_FILE_SIZE=10000000

    # "MAX_LOG_FILE_SIZE" property indicates the maximum size of the log file.
    # When the log file reaches the maximum size, then it rolled over to backup file.
    # The log file size is expressed in bytes. The default value is 10000000 (10MB).
    # If this is set to 0, the log file will never be rolled over
    # and will continue to grow indefinitely.
    Param3=BACKUP_LOG_FILE_LOCATION=ARCOT_HOME/logs/backup
    Param2=MAX_LOG_FILE_SIZE=10000000

    # "BACKUP_LOG_FILE_LOCATION" property indicates the directory where the log
    # files are rolled over to. This directory must already exist
    # and have permissions allowing the State Manager to create files in it.
    Param3=BACKUP_LOG_FILE_LOCATION=ARCOT_HOME/logs/backup

  4. Please ensure that the ARCOT_HOME/logs have backup directory in it and if for some reason it was deleted, please create with correct privileges.