GUI fails to restart after upgrade of all other GPFS packages on SLES 15 SP3

This issue might occur as a result of version conflicts in PostgreSQL packages.

Try the following procedure to resolve version conflicts and successfully restart the GUI.

Delete all PostgreSQL packages from the node.

Install the PostgreSQL modules by specifying the specific version. For example,

# zypper install postgresql-13-8.30.noarch

# zypper install postgresql-contrib-13-8.30.noarch

Issue the following command to check that the installed packages do not have any conflict in versions. For example,

# rpm -qa | grep "postgresql

If there is a version conflict in the installed packages, the output displays the details as shown in the following example:

postgresql13-contrib-13.6-5.25.1.s390x
postgresql13-server-13.6-5.25.1.s390x
postgresql-server-14-10.6.2.noarch
postgresql13-13.6-5.25.1.s390x
postgresql-contrib-14-10.6.2.noarch
postgresql-14-10.6.2.noarch

In the following example the output indicates there is no conflict mismatch:

postgresql13-contrib-13.6-5.25.1.s390x      
postgresql13-server-13.6-5.25.1.s390x        
postgresql-server-13-8.30.noarch             
postgresql13-13.6-5.25.1.s390x               
postgresql-contrib-13-8.30.noarch            
postgresql-13-8.30.noarch

If the GUI service failed to validate the checkpoint record then issue the following command to reset the transaction logs.
```
 # pg_resetwal -f /usr/local/var/postgres/
```
Note: If the pg_resetwal: error: cannot be executed by "root" error occurs then issue the command in sudo mode. For example,
```
su postgres
```

Issue the following commands to clean up the data, initialize the database and start the PostgreSQL service.

 # rm -rf /var/lib/pgsql/data
 # su postgres -c 'initdb -D /var/lib/pgsql/data'
 #systemctl start postgresql

Issue the following command to check if the service status is in running state.
```
# systemctl status postgresql
```
Issue the following command to restart the GUI service.
```
# systemctl restart gpfsgui
```