Chk_auto_up shows CAUAJM_I_50039 No Scheduler is RUNNING

book

Article ID: 213042

calendar_today

Updated On:

Products

CA Workload Automation AE - Scheduler (AutoSys)

Issue/Introduction

We have installed r12 application in primary, shadow and tiebreaker server and post installation.

we do not see scheduler service running message in chk_auto_command for primary, secondary and tie breaker server.

The background services are running,

 


CAUAJM_I_50054 Attempting (1) to Connect with Database: xxxxPRI
CAUAJM_I_50055 *** Have Connected successfully with Database: xxxxxPRI. ***
______________________________________________________________________________

CAUAJM_I_50128 Connected with Event Server: xxxxxPRI

______________________________________________________________________________

CAUAJM_I_50054 Attempting (1) to Connect with Database: xxxxxxxSHD
CAUAJM_I_50055 *** Have Connected successfully with Database: xxxxxxxxSHD. ***
______________________________________________________________________________

CAUAJM_I_50128 Connected with Event Server: xxxxxxxSHD

______________________________________________________________________________

______________________________________________________________________________

CAUAJM_I_50038 Checking AutoSys Primary Scheduler on Machine: PRIMARY.xxdom.com
CAUAJM_I_50039 No Scheduler is RUNNING on machine: PRIMARY.xxdom.com
______________________________________________________________________________

CAUAJM_I_50038 Checking AutoSys Shadow Scheduler on Machine: SHADOW.xxdom.com
CAUAJM_I_50039 No Scheduler is RUNNING on machine: SHADOW.xxdom.com
______________________________________________________________________________

CAUAJM_I_50038 Checking AutoSys Tie-Breaker Scheduler on Machine: TIEBREAKER.xxdom.com
CAUAJM_I_50039 No Scheduler is RUNNING on machine: TIEBREAKER.xxdom.com
______________________________________________________________________________

 

 

Cause

The problem was due to the wrong hostnames PRIMARY.xxdom.com/SHADOW.xxdom.com/TIEBREAKER.xxdom.com  which was not reachable on the network. This was being picked up from /etc/host entries.

Environment

Release : 12

Component : CA Workload Automation AE (AutoSys)

Resolution

There was an entry in etc/hosts file with FQDN name which was wrong. After removing the entry from hosts file and restarting the autosys services in all three servers the issue was resolved.