Systemedge agent service fails to start with the error: "Failed to initialize file-based configuration module: [1] CAM has shutdown"

book

Article ID: 35360

calendar_today

Updated On:

Products

CA Systems Performance for IM (SystemEdge)

Issue/Introduction

If you try to start SystemEDGE service with no success, and the following errors appear in SystemEDGE logs:


[A]-012478-f771d6c0- se/cfsyswrapper.c[1193]    : cf_Init(): SystemEDGE is running in managed mode, manager is 'xxx.xxx.xxx.xxx'
[I]-012478-f771d6c0- caismcomm/config_handler.c[2508]: CfSys_Init(): Cannot connect to CAM yet - Unable to connect to CAM server
[F]-012478-f771d6c0- se/cfsyswrapper.c[1297]     : cf_Init(): Failed to initialize file-based configuration module: [1] CAM has shutdown

or

[I]-060930-f75b1700- caismcomm/config_handler.c[2532]: CfSys_Init(): Cannot connect to CAM yet - An application with this name is already connected to CAM


You check the CAM logs and the following errors appear too:

Starting CAM version 1.13 (Build 10_8)
no port defined for service "camudp", using default
no port defined for service "camtcp", using default
localhost didn't resolve to an IPv6 address.  Adding ::1
Local hostname is >xxxxxx<
Local address is >xxx.xxx.xxx.xxx<
UDP port is 4104
TCP port is 4105
bind() failed in init_listen with ai->ai_addr = 0.0.0.0:4104: socket error (98) Address already in use
bind() failed in init_listen with ai->ai_addr = [::]:4104: socket error (98) Address already in use
UDP port unavailable
CAM error: unable to bind to port (CAM probably already running) - (98) Address already in use

 

 

Cause

Cause: 

  • When SystemEDGE is configured to run in Managed Mode (considering it is being managed by CA VAIM ), it depends on CAM to work properly.
  • In this scenario, there is a problem with CAM (bind error/port in use) and it is preventing SystemEDGE service to start.

 

Environment

CA SystemEdge 5.x

Release:
Component: SEAGNT

Resolution

  • CAM is used for VAIM agent registration and policy deployment. 
  • If there is no VAIM manager used you can put the agent into unmanaged mode, then CAM is no longer needed as SystemEDGE configuration is managed locally or via snmpset (via spectrum).

To put agent in unamaged mode and break the connection with CAM:

a-) Stop SystemEDGE service:

if Unix/linux -> Open a command line and Issue "/opt/CA/SystemEDGE/bin/sysedgectl stop" command.
if Windows -> Click on "stop agent" button in SystemEDGE Control Panel.

b-) Switch SystemEDGE to non-managed mode:

- Open SystemEDGE\config\sysedge.cf

- Comment out or remove the following line:

   "manager_name"

- Save the file.

- Open SystemEDGE\data\<port_number>\sysedge.cf

- Comment out or remove the following 3 lines:

    "manager_name"
    "manager_policy_name"
    "manager_policy_version"

- Save the file.

c-) Start SystemEDGE service:

if Unix/linux -> Open a command line and Issue "/opt/CA/SystemEDGE/bin/sysedgectl start" command.
if Windows -> Click on "start agent" button in SystemEDGE Control Panel.

If agent needs to remain in Managed Mode:
  • kill all instances of cam process
  • kill all instances of sysedge process
  • rename port# folder to port#.old (/opt/CA/SystemEDGE/config)
  • run a netstat on the box and make sure the following ports arent being used by an other processes before starting sysedge
    1. UPD 4104
    2. TCP 4015
    3. UDP 1691 or 161 depending on what SysEDGE is configured to use (PORT# folder will indicate the port)
  • start systemedge - ./sysedgectl start