What does the -R option mean on event_demon?

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

Description:

Some of the event_demons are running with a -R option, some are not.
What does this option mean?

Solution:

A typical "ps -ef|grep event_demon" for an AutoSys instance in single EP mode, with an EPCount=4 and RestartEPs=1, that was started via "eventor" would look like this:

   $ ps -ef|grep event_demon   
   autosys 29179 29132 0 May 07 ? 11:16 event_demon -A MMM -c 4   
   autosys 29174 29132 0 May 07 ? 11:55 event_demon -A MMM -c 2   
   autosys 29132 1 0     May 07 ? 9:00  event_demon -A MMM -c 1 -R   
   autosys 6492 29132 0  May 07 ? 13:16 event_demon -A MMM -c 3  

In the above case EP1 is using the -R option to stand for recovery.
Meaning EP1 performed chase during startup.
------

If EP4 was killed or got hung up and was not able to write its heartbeat, EP1 can kill and restart it, or any other EP(s).
In a case like that, the ps output would look like:

   $ ps -ef|grep even_demon   
   autosys 13622 29132 0 07:27:00 ? 0:00 event_demon -A MMM -c 4 -R   
   autosys 29174 29132 0 May 07   ? 11:57 event_demon -A MMM -c 2   
   autosys 29132 1     0 May 07   ? 9:02 event_demon -A MMM -c 1 -R   
   autosys 6492 29132  0 May 07   ? 13:17 event_demon -A MMM -c 3  

The above is showing that EP4 was recovered/restarted.

In the $AUTOUSER/out/event_demon.$AUTOSERV file you would also see something similar to:

   [07:27:00.8590] [1] Checking EP heartbeats...   
   [07:27:00.8592] [1] EP #4's heartbeat is missing!   
   [07:27:00.8593] [1] Sending a MULTIPLE_EP_SHUTDOWN alarm.   
   [07:27:00.9264] [1] EP #4 has been successfully restarted.   
   [07:27:00.9564] [1] EVENT: ALARM ALARM: MULTIPLE_EP_SHUTDOWN   
   [07:27:00.9568] [1] <EP #4>   
   [07:27:01.1522] [4] ____________________________________________________   
   [07:27:01.1526] [4] Opening up the Database Connections...   
   [07:27:01.1531] [4] ____________________________________________________   
------  

If AutoSys was started via "eventor -n" then the ps output would not show -R for EP1 as the -n tells AutoSys to NOT run chase at startup
example:

      $ ps -ef|grep event_demon 
      autosys 348 316 0 08:12:50 pts/4 0:00 event_demon -A MMM -c 2 
      autosys 316   1 1 08:12:47 pts/4 0:00 event_demon -A MMM -c 1 
      autosys 359 316 0 08:12:50 pts/4 0:00 event_demon -A MMM -c 4 
      autosys 355 316 0 08:12:50 pts/4 0:00 event_demon -A MMM -c 3 

If one of the EP(s) # 2, 3, or 4 died and was restarted the ps output would look similar to:

      $ ps -ef|grep event_demon 
      autosys 8586 1267 0 08:35:14 pts/4 0:01 event_demon -A MMM -c 4 -R 
      autosys 1298 1267 0 08:15:10 pts/4 0:04 event_demon -A MMM -c 2 
      autosys 1267 1 0 08:15:07 pts/4 0:03 event_demon -A MMM -c 1 
      autosys 1305 1267 0 08:15:10 pts/4 0:03 event_demon -A MMM -c 3 
------

If AutoSys was started in Dual EP mode (without the -n option)
2 EP1's will be on the primary, both with -R option.
This is normal.
1 of the EP's is for processing events, while the other is for shadow pings.

      $ ps -ef|grep event_demon 
      autosys 23702 23584 0 10:39:28 pts/4 0:00 event_demon -A MMM -c 2 
      autosys 23584     1 1 10:39:12 pts/4 0:00 event_demon -A MMM -c 1 -M 142b225sun1 -R 
      autosys 23703 23584 0 10:39:28 pts/4 0:00 event_demon -A MMM -c 3 
      autosys 23708 23584 0 10:39:29 pts/4 0:00 event_demon -A MMM -c 4 
      autosys 23701 23584 0 10:39:28 pts/4 0:00 event_demon -A MMM -c 1 -M 142b225sun1 -R 
------

Notes:
The additional EPs can only be restarted if the setting RestartEPs is enabled (set to 1 in the $AUTOUSER/config.$AUTOSERV file).

The Info above applies to the Shadow EP(s)as well.