Troubleshooting PowerHA SystemMirror GUI

You can view log files to help you troubleshoot PowerHA® SystemMirror® GUI.

The information in this section is only a reference guide for different techniques and log files you might be able to use to troubleshoot problems with thePowerHA SystemMirror GUI. You must contact IBM support if you are uncertain about the information here or how to solve your problem.

Log files

You can use the following log files to troubleshoot PowerHA SystemMirror GUI:

smui-server.log: This log file is located in the /usr/es/sbin/cluster/ui/server/logs/ directory. The smui-server.log file contains information about the PowerHA SystemMirror GUI server.
smui-agent.log: This log file is located in the /usr/es/sbin/cluster/ui/agent/logs/ directory. The smui-agent.log file contains information about the agent that is installed on each PowerHA SystemMirror node.
notify-event.log: This log file is located in the /usr/es/sbin/cluster/ui/agent/logs/ directory. The notify-event.log file contains information about all PowerHA SystemMirror events that are sent from the agent to the PowerHA SystemMirror server.

Problems logging in to PowerHA SystemMirror GUI

If you are experiencing problems in logging in to the PowerHA SystemMirror GUI, complete the following steps:

Check for issues in the /usr/es/sbin/cluster/ui/server/logs/smui-server.log file.
Verify that the smuiauth command is installed correctly. Also, verify that the smuiauth command has the correct permissions by running the ls -l command from the /usr/es/sbin/cluster/ui/server/node_modules/smui-server/lib/auth/smuiauth directory. An output that is similar to the following example is displayed when you run the ls -l command:
```
-r-x------    1 root     system        21183 Aug 31      21:48
```
Verify that you can run the smuiauth command by running the smuiauth -h command.
Verify that the pluggable authentication module (PAM) framework is configured correctly by locating the following lines in the /etc/pam.conf file:
Note: The PAM configuration occurs when you install the cluster.es.smui.server file set.
```
smuiauth        auth       required     pam_aix
smuiauth        account    required     pam_aix
```

Problem adding clusters to the PowerHA SystemMirror GUI

If you are not able to add clusters to the PowerHA SystemMirror GUI, complete the following steps:

Check for issues in the /usr/es/sbin/cluster/ui/server/logs/smui-server.log file.
1. If SFTP-related signatures exist in the log file, such as Received exit code 127 while establishing SFTP session, a problem exists with the SSH communication between the PowerHA SystemMirror GUI server and the cluster you are trying to add.
2. From the command line, verify that you can connect to the target system by using SSH File Transfer Protocol (SFTP). If you cannot connect, verify that the daemon is running on the PowerHA SystemMirror GUI server and the target node by running the ps –ef | grep –w sshd | grep –v grep command. You can also check the SFTP subsystem configuration in the /etc/ssh/sshd_config file and verify that following path is correct:
```
Subsystem       sftp    /usr/sbin/sftp-server
```
  If the path is not correct, you must enter the correct path in the /etc/ssh/sshd_config file, and then restart the sshd subsystem.
Check for issues in the /usr/es/sbin/cluster/ui/agent/logs/agent_deploy.log file on the target cluster.
Check for issues in the /usr/es/sbin/cluster/ui/agent/logs/agent_distribution.log file on the target cluster.

PowerHA SystemMirror GUI does not update cluster status

If PowerHA SystemMirror GUI does not update the cluster status or does not display new events, or if the cluster displays data gathering error or displays communication error when you discover the cluster in the PowerHA SystemMirror GUI, complete the following steps:

Check for the certificate error in the following log files:
- /usr/es/sbin/cluster/ui/server/logs/smui-server.log
- /usr/es/sbin/cluster/ui/agent/logs/smui-agent.log
If a certificate error is written to the log file, it indicates that the certificate on the target cluster and the certificate on the server do not match. A certificate error in the log file might be similar to the following example:
```
WebSocket server - Agent authentication failed, remoteAddress:::ffff:10.40.20.186, Reason:SELF_SIGNED_CERT_IN_CHAIN 
```
Resolve the certificate error by regenerating security files on the server node. To regenerate security files, run the following script:
```
/usr/es/sbin/cluster/ui/server/node_modules/smui-server/resources/makesec.ksh -f
```
Note: If you regenerate security files, communication problems might occur in clusters that are discovered in the PowerHA SystemMirror GUI.
Restart the server and discover clusters again in the PowerHA SystemMirror GUI. This operation also resolves the communication problem in the cluster.

Migrating the PowerHA SystemMirror GUI database

See Migrating the PowerHA SystemMirror GUI database.