The following issues can occur when you are using cells.
1 | The cell will not start
Explanation:
It is possible that a statbld failure has occurred.
User Response:
If there is nothing in the log trace files to help you diagnose the issue, try running the cell in the foreground. This frequently provides the information needed to correct the issue or enough information for BMC Support to diagnose the problem. To run the cell in the foreground, enter mcell -n cellName -d If a statbld failure has occurred, to correct this problem, perform these steps: - Look for the following files in the installationDirectory/pw/server/var/cellName directory:
- If either or both of these files are present, delete them.
- Restart the cell.
|
2 | BMC-IMC890104W:The cell is not responding to a client request
Explanation:
The client has made a request to the cell, but the cell is not responding.
User Response:
Check the connection status of the cell. |
3 | The primary and secondary servers for the high availability cell are in active mode simultaneously or are unsynchronized.
Explanation:
This can occur for one of the following reasons: - The primary and secondary servers are running on a network that has an unreliable connection.
- When a high availability cell has started using any of the mcell -I initialization options (for example, -ia, -id, or other variants).
- When the primary server is started first and terminates before the secondary server is started.
User Response:
Synchronize the mcdb and xact files of the primary and secondary servers. Perform the following steps to synchronize the primary and secondary servers: - If the issue was caused by an unreliable network, resolve the network issue.
- Shut down both cell servers.
- Copy the mcdb and xact files of the preferred server to the other server. (The preferred server can be either primary or secondary.)
- Start the secondary cell server.
- Start the primary cell server.
|
