09/01/19-20:16:12 doLaunch() : AME counter is 25 (at 3725314.046365310). List of 1 app uuid managed is  "1567267349133928000". doLaunch() : For app "1567267349133928000": this application monitoring was already active. dependencyCheck() : Dependency list is empty doLaunch() : For app "1567267349133928000": application script "/tmp/HA/app1_mon.sh" being  forked ! pidParent(12648876) forks pidChild(11731218). doLaunch() : For app "1567267349133928000": computing time of timeout by adding xmlAppTimeout(3)  to appEntry.m_timeScriptTimeoutAt => 3725317.046365310. doLaunch() : Synthesis: list of 1 processes forked during this loop is  "(uuid=1567267349133928000;monitor;/tmp/HA/app1_mon.sh) ". doNonBlockingWait() : AME waiting for 1 script(s) (at 3725314.050309701). doNonBlockingWait() : +Synthesis of all (1) applications: doNonBlockingWait() : | UUID STATE RESULT RUN MON DEL FAIL STOP START RESTART DESCRIPTION doNonBlockingWait() : | 1567267349133928000 3(FAILING) 2(TIMOUT) 1 1 0 1/ 2 0/  3 0/ 3 0/1 doNonBlockingWait() : + The next round in Example 2-169 on page 193, 25, starts the monitoring script after the first  failure, computes its timeout time, and updates the status, which is  RUN  set to  1 . Example 2-170 shows the next relevant rounds, 29, 30, and 31. In round 29, the monitoring  script that restarted earlier in round 25 is found again in timeout by  doInspectForTimeout() ,  so its process is killed again. Example 2-170 The next three relevant AME log rounds for the monitoring script timeout scenario: 29, 30, and 31 09/01/19-20:16:16 doLaunch() : AME counter is 29 (at 3725318.043083808). List of 1 app uuid managed is  "1567267349133928000". doNonBlockingWait() : AME waiting for 1 script(s) (at 3725318.043125326). doNonBlockingWait() : +Synthesis of all (1) applications: doNonBlockingWait() : | UUID STATE RESULT RUN MON DEL FAIL STOP START RESTART DESCRIPTION doNonBlockingWait() : | 1567267349133928000 3(FAILING) 2(TIMOUT) 1 1 0 1/ 2 0/  3 0/ 3 0/1 doNonBlockingWait() : + doInspectForTimeout() : For app "1567267349133928000": timeout was set to 3725317.046365310. doInspectForTimeout() : For app "1567267349133928000": script was in timeout, killing now script  process (pid "11731218"). 09/01/19-20:16:17 doLaunch() : AME counter is 30 (at 3725319.044798625). List of 1 app uuid managed is  "1567267349133928000". doLaunch() : For app "1567267349133928000": script was killed because of timeout. doNonBlockingWait() : AME waiting for 1 script(s) (at 3725319.044863876). doNonBlockingWait() : For app "1567267349133928000": pid "11731218" killed, result set to  "TIMOUT" doNonBlockingWait() : For app "1567267349133928000": app state is "3(FAILING)", previous result  was "2(TIMOUT)", current result is "2(TIMOUT)". doNonBlockingWait() : For app "1567267349133928000": monitor failures(2)/max(2). Needs to be  stopped. doNonBlockingWait() : app '1567267349133928000' restartcount '0' appEntry.m_statsCollectionDone  : 'false' doNonBlockingWait() : appEntry.m_lastStatsCollectedAt : '0' currentTime : '3725319' doNonBlockingWait() : +Synthesis of all (1) applications: 194  Implementing IBM VM Recovery Manager for IBM Power Systems