IBM Verify

IBM Verify

Join this online user group to communicate across Security product users and IBM experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Back to discussions
Expand all | Collapse all

Problems with pdmgrd (ivmgrd) logging path changed from isam_runtime to verify_access_runtime on v10.0.2.0 IF1

  • 1.  Problems with pdmgrd (ivmgrd) logging path changed from isam_runtime to verify_access_runtime on v10.0.2.0 IF1

    Posted Fri March 04, 2022 11:18 AM
    Does anyone know if this is resolved in v10.0.3.0 IF1?

    When you start a container on v10.0.2.0 IF1, and the shared logging directory has been wiped out, pdmgrd won't start on the config nor WRP containers.

    In aznapi-configuration the log-cfg value in the LMI reads:
    logcfg = audit:file path=audit_pdmgrd.log,flush_interval=20,log_id=PDMgrAudit

    However, in /var/PolicyDirector/etc/ivmgrd.conf on the containers it reads:
    logcfg = audit:file path=/var/application.logs.local/isam_runtime/policy/audit_pdmgrd.log,flush_interval=20,log_id=PDMgrAudit

    The bootstrap does not create isam_runtime anymore, it creates verify_access_runtime.  So either the bootstrap needs to be creating that directory, OR whatever updates ivmgrd.conf needs to update that path.

    We had to recreate the shared logging directory due to some corruption on several environments and none of the containers would start pdmgrd until I created /var/application.logs.local/isam_runtime

    Thanks.

    ------------------------------
    Matt Jenkins
    ------------------------------


  • 2.  RE: Problems with pdmgrd (ivmgrd) logging path changed from isam_runtime to verify_access_runtime on v10.0.2.0 IF1

    Posted Sun March 06, 2022 03:28 PM

    Matt,

     

    I just tried this in a 10.0.3.1 container and the correct path was set for the logcfg configuration entry (/var/applications.logs.local/verify-access-runtime/policy/audit_pdmgrd.log).  I didn't try an upgrade from an older release, but the configuration should be migrated to the correct path as a part of the upgrade.

     

    Thanks.

     

     

    Scott A. Exton
    Senior Software Engineer
    Chief Programmer - IBM Security Verify Access
    IBM Master Inventor

     

     




    Original Message


Related Content