Table 2.40. Supervisor Fault Codes
| faultCode | faultString | Description |
|---|---|---|
| 1 | UNKNOWN_METHOD | Returned if the server was asked to dispatch a method it didn’t know about. |
| 2 | INCORRECT_PARAMETERS | This fault is returned when the server has signature(s) defined for a method, and the parameters passed by the client do not match any of signatures. |
| 3 | BAD_ARGUMENTS | This fault is returned when the method rejects the parameters passed by the client for any reason other than a type mismatch. |
| 4 | SIGNATURE_UNSUPPORTED |
This fault is returned when the client calls the XML-RPC
system.methodSignature() method. This method is not
supported by the API implementation.
|
| 6 | SHUTDOWN_STATE |
Fault raised when any method is called while Supervisor is in
SHUTDOWN.
|
| 10 | BAD_NAME | Fault raised when Supervisor does not recognize the subprocess name or subprocess group name given by the client. |
| 7 | NO_FILE | Supervisor expected to find a file on the filesystem but found none. |
| 21 | NOT_EXECUTABLE |
The process could not be started by
supervisor.startProcess() because the file was
not executable.
|
| 30 | FAILED | The operation failed for an unknown or unanticipated reason. |
| 40 | ABNORMAL_TERMINATION |
The process successfully started by
supervisor.startProcess(), however it exited
prematurely during the timeout period.
|
| 50 | SPAWN_ERROR |
A method call to supervisor.startProcess()
requested Supervisor to (re)start a subprocess but spawning
that subprocess failed.
|
| 60 | ALREADY_STARTED |
A method call to supervisor.startProcess()
requested Supervisor to (re)start a subprocess but that subprocess
has already been started.
|
| 70 | NOT_RUNNING |
A method call to supervisor.stopProcess()
requested Supervisor to stop a subprocess but that subprocess
is not running.
|
| 80 | SUCCESS |
Some methods return envelopments of multiple results inside
XML-RPC structs. For these, SUCCESS
indicates no error.
|
| 90 | TIMED_OUT | Future expansion. |