Pivotal Knowledge Base

Follow

gptext-start or gptext-stop fails with error message "process already running"

Environment 

Product Version
Pivotal GPText  1.2.x, 1.3.x
OS RHEL 6.x

Symptom

gptext-start or gptext-stop fails with the error as shown below: 

[gpadmin@mdw ~]$ gptext-start
20160425:12:21:12:003862 gptext-start:mdw:gpadmin-[INFO]:-Retrieving configuration from database...
20160425:12:21:12:003862 gptext-start:mdw:gpadmin-[CRITICAL]:-Error starting GPText cluster: GPText start process already running
20160425:12:21:12:003862 gptext-start:mdw:gpadmin-[ERROR]:-Some of the GPText instances failed to start.

Cause 

gptext-start and gptext-stop create a temporary .pid file under "/usr/local/greenplum-text-1.x/" during the run length of these commands. The file is usually called:

/usr/local/greenplum-text-1.3.0.2/gptext-start.pid

/usr/local/greenplum-text-1.3.0.2/gptext-stop.pid

If this file already exists when "gptext-start" or "gptext-stop" is run, it will fail with the above error.  

Note: Please verify that the pid in the file does not exist before renaming it. If the pid exists in the system, then it means that some other session is also attempting a gptext-start or gptext-stop. In that case, do not rename the file.      

The command to check if pid exists is: [ps -ef | grep <pid>]

Resolution 

Check if there is an existing gptext*.pid file under "/usr/local/greenplum-text-1.x/". If yes, rename the file to ".old". Then attempt

gptext-start 

or

gptext-stop

 

Internal Comments

This article references jira : https://jira.eng.pivotal.io/browse/TA-976

Comments

Powered by Zendesk