Interpreting cell execution failure codes
When the cell runs as a daemon or a service, it has no standard output or error stream. Tracing that is configured to go to stderr is redirected to a file in this case. You can configure the path for that file in mcell.conf. The default is installationDirectory\pw\server\tmp\cellName\trace.
If the cell service setup fails, an error file, mcell.err, is generated. Additional service setup failures can be appended to the original file, resulting in a file content of multiple lines. Normally, each line corresponds to one failed service setup. This error file contains exit codes specific to BMC Impact Manager.
The following table lists the exit codes for the Infrastructure Management cell:
Code | Description |
|---|---|
| Invalid command line options used. |
| Incorrect home directory specification through option |
| No home directory could be determined. |
| Specified home directory is invalid. |
| Internal initialization failure. |
| Tracing configuration failed. |
| System process handling module initialization failure. |
| Logging facility initialization failure. |
| Service control module initialization failure. |
| Knowledge Base load failed. |
| Message handling module initialization failure. |
| Internal object initialization failure. |
| Event processing module initialization failure. |
| Saved state reload failed. |
| Query handling module initialization failure. |
| Service activation failed. |
| Internal object module initialization failure. |
| Metrics initialization failed. |
| Data processing module initialization failure. |
| Metrics activation failed. |
| Service setup failed. |
Comments
Log in or register to comment.