KAMN285-E
Program:aa....aa is terminated with an error.
Reason:bb....bb Details:cc....cc
Start or restart of the program indicated by the program alias name has failed.
aa....aa: Program alias name
bb....bb: Cause code (unique to HA Monitor, 1 or 2 digits)
cc....cc: Detail code
The detail and cause codes are defined as follows:
Cause code |
Detail code |
Meaning |
---|---|---|
1 |
1 |
The program's restart command did not finish before the timeout period elapsed. |
2 |
The UAP did not invoke the hamon_patrolstart function before the timeout period elapsed. |
|
3 |
The program's restart command did not finish before the timeout period elapsed, and the UAP did not invoke the hamon_patrolstart function. |
|
2 |
126 |
The file specified in the restartcommand operand does not have permission to execute the command. |
127 |
The file specified in the restartcommand operand does not exist. |
|
256 |
A system call error occurred when the program's restart command was executed. |
|
Other value |
Displays the value returned by the program's restart command. |
- S:
-
If the cause code is 1, stops execution of the server start command and begins execution a restarts according to the settings. If the preset number of restarts is exceeded, a hot standby is executed if the active server is in a state that allows hot standbys.
If the cause code is 2, stops processing.
- O:
-
Contact a system administrator.
- Action:
-
Take one of the following actions, as indicated by the cause code.
Cause code
Corrective action
1
Determine the reason the program's restart command did not return a value or the reason the program did not invoke the hamon_patrolstart function, and then eliminate the cause. Manually perform a planned hot standby, if necessary. Alternatively, restart the active server or the program that failed.
2
Check whether the program restart command can be executed. If it can, eliminate the cause of the error for the cause code that is output. If it cannot, correct the command. Manually perform a planned hot standby, if necessary. Alternatively, restart the active server or the program that failed.