Why does the TSPS database process show an incorrect status as 'Running' when the Process ID (PID) for the database does not exist?

TrueSight Presentation Server uses a Postgres database. If  the database process is terminated abnormally. for example, due to power outage, server crash or the database forcefully killed by an administrator then the postmaster.pid file which is used to keep track of last status of the database process may not be deleted and running the ‘tssh server status’ command returns false output.

Please take a look at the following example.
 

Process status
=====================================
Core Server     Not running
Index Server    Not running
Database Server Running (28081)

[patrol@mypsdevserver ~]$ tssh server stop
+-------------------------------------------------------------------------------------------+
|   BMC TrueSight Presentation Server - Command Line Interface 2020 version 11.3.04         |
|   Copyright 2014-2020. BMC Software, Inc. as an unpublished work.  All rights reserved.   |
+-------------------------------------------------------------------------------------------+
Stopping server ....
Done.

[patrol@mypsdevserver ~]$ tssh server status
+-------------------------------------------------------------------------------------------+
|   BMC TrueSight Presentation Server - Command Line Interface 2020 version 11.3.04         |
|   Copyright 2014-2020. BMC Software, Inc. as an unpublished work.  All rights reserved.   |
+-------------------------------------------------------------------------------------------+

Process status
=====================================
Core Server     Not running
Index Server    Not running
Database Server Running (28081)

[patrol@mypsdevserver ~]$ kill -9 28081
-bash: kill: (28081) - No such process

As a result of this inconsistent state, an Administrator will not be able to bring up other TSPS java processes such as CSR or Index server.
To fix this please delete <TSPS_Install_dir>/truesightpserver/data/pgsql/postmaster.pid file as it holds a record of the PID which no longer exists.
Then restart the TSPS application using the 'tssh server stop' and 'tssh server start' command.
1.Open a command prompt on the TSPS server
2 .Run the following command:
tssh server stop
3. Allow the processes to stop
4. Run the following command:
tssh server start
5. Allow the processes to come up