The Primary AutoSys scheduler host ran out of disk space. Should the Shadow take over?

Document ID : KB000049223
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

The Primary AutoSys scheduler host ran out of disk space. Should the Shadow take over?

$AUTOUSER/out/event_demon.$AUTOSERV log on the primary:

CAUAJM_E_40360 ERROR: No disk space left to write the Unicenter AutoSys JM Scheduler log file issue.
CAUAJM_I_40247 CA Unicenter AutoSys JM Scheduler processing of events complete.
CAUAJM_I_40248 CA Unicenter AutoSys JM Scheduler shutdown complete. Exiting.

Solution:

You should expect to see messages such as the following in the

$AUTOUSER/out/event_demon.$AUTOSERV log on the primary:

CAUAJM_E_40360 ERROR: No disk space left to write the Unicenter AutoSys JM Scheduler log file issue.
CAUAJM_I_40247 CA Unicenter AutoSys JM Scheduler processing of events complete.
CAUAJM_I_40248 CA Unicenter AutoSys JM Scheduler shutdown complete. Exiting.

This will result in the primary scheduler shutting down gracefully.

It removes its high availability entries in the database which the shadow and tiebreaker use to monitor its availability.

With those entries removed, the shadow and tiebreaker remain in dormant mode.

This is an example of what you would see in the shadow or tie-breaker scheduler logs:

[01/29/2012 06:07:16]      Last Four Scheduler Heartbeats:
[01/29/2012 06:07:16]      Interval  Primary                Shadow       Tertiary
[01/29/2012 06:07:16]      --------- ---------------------  ----------------- ----  ---------------------
[01/29/2012 06:07:16]      0         1327846035(Dormant)    1327846035(Active )     1327846032(Active)
[01/29/2012 06:07:16]      -1        1327846025(Active)     1327846030(Active )     1327846027(Active)
.

So the answer is no, the shadow will not take over in the above case where the primary scheduler machine runs out of disk space.