search cancel

Cannot Start PAMSC Agent

book

Article ID: 200675

calendar_today

Updated On:

Products

CA Virtual Privilege Manager CA Privileged Identity Management Endpoint (PIM)

Issue/Introduction

PAMSC Admin successfully installed PAMSC Build v14.10.0.1119 on AIX 6.1.

Then tried to import the rules from the previous install using /opt/CA/PAMSC/bin/selang -l -f /development_bkp/pamsc/File3toimport -o /development_bkp/pamsc/File3toimport.log,

The import was successful with no error in the log file /development_bkp/pamsc/File3toimport.log, the import file had about 9,000 lines.

Then tried to start PAMSC and it is failing:

_____________________
# ../bin/seload
CA Privileged Access Manager Server Control seload v14.10.0.1119 - Loader Utility
Copyright (c) 2018 CA. All rights reserved.
25 Sep 2020 14:17:53> WAKE_UP : Server going up
25 Sep 2020 14:17:53> INFO    : Filter mask: 'WATCHDOG*' is registered
25 Sep 2020 14:17:53> INFO    : Filter mask: 'INFO    : Setting PV*' is registered
25 Sep 2020 14:17:53> INFO    : Filter mask: 'INFO    : DB*' is registered
25 Sep 2020 14:17:53> INFO    : Filter mask: '*seosd.trace*' is registered
25 Sep 2020 14:17:53> INFO    : Filter mask: '*FILE*secons*(*/log/*)*' is registered
Starting seosd. PID = 37290046.
Checking database ...
ERROR: Timeout waiting for CA Privileged Access Manager Server Control daemon.
Executing [daemons] command: /opt/CA/PAMSC/bin/selogrd
Starting selogrd. PID = 64159932
Executing [daemons] command: /opt/CA/PAMSCShared/lbin/report_agent.sh
Executing [daemons] command: /opt/CA/PAMSCShared/lbin/agent_manager.sh
/opt/CA/PAMSCShared/bin/ReportAgent
# /opt/CA/PAMSCShared/bin/AgentManager start
WARNING: Security daemon is not running.
ERROR: Report Agent already running.
Starting AgentManager. PID = 46399648.

Environment

Release : 14.0

Component : CA ControlMinder

Resolution

Resolved Issue by:

1.- redudcing the number of the rules by 10% ~500 rules less.

2.- in seos.ini modified the following parameters:

; This token defines the maximum number of file rules allowed in the database

; note that putting very large number may cause strange behavior

; on different platforms

; Valid Values: > 4095 (must be bigger then 4095)

; Default Value: 4096

max_regular_file_rules = 20000


; This token defines the maximum number of generic file rules allowed in the database.

; Setting a very large number can decrease the system throughput.

; Default Value: 256

max_generic_file_rules = 2048


3.- restarted and the issue is resolved.