Bug 771221

Summary: init.d script for RedHat doesn't create PID file
Product: [Community] GlusterFS Reporter: Jaroslav Pulchart <jaroslav.pulchart>
Component: scriptsAssignee: kaushik <kbudiger>
Status: CLOSED CURRENTRELEASE QA Contact: Ujjwala <ujjwala>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.2.5CC: gluster-bugs, mjc, sdharane, sghai
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.4.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-24 17:29:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 817967    
Attachments:
Description Flags
patch for glusterd init.d script none

Description Jaroslav Pulchart 2012-01-02 15:42:01 UTC
Created attachment 550266 [details]
patch for glusterd init.d script

Description of problem:
init.d script for RedHat doesn't create PID file

Version-Release number of selected component (if applicable):
3.2.5
  
Actual results:
Gluster daemon started by init scripts for RedHat doesn't create /var/run/glusterd.pid file.

Expected results:
When glusterd is started by glusterd init script for RedHat the /var/run/glusterd.pid pidfile will be created with PID of gluster daemon.

Additional info:
-

Comment 1 kaushik 2012-01-11 09:09:41 UTC
Thanks for the fix Jaroslav Pulchart , and the same fix is applicable for all the releases as well.
You could send the fix yourself:

http://www.gluster.org/community/documentation/index.php/Development_Work_Flow

Let us know if you need any help regarding the same.

Comment 2 Anand Avati 2012-02-03 16:16:24 UTC
CHANGE: http://review.gluster.com/2668 (extras: create PID file for glusterd when started from init scripts) merged in master by Vijay Bellur (vijay)

Comment 3 Sachin Ghai 2012-06-01 06:04:45 UTC
Verified with following glusterfs packages on RHS2.0:

glusterfs-fuse-3.3.0qa45-1.el6.x86_64
glusterfs-3.3.0qa45-1.el6.x86_64
glusterfs-server-3.3.0qa45-1.el6.x86_64
glusterfs-rdma-3.3.0qa45-1.el6.x86_64
org.apache.hadoop.fs.glusterfs-glusterfs-0.20.2_0.1-1.noarch
glusterfs-geo-replication-3.3.0qa45-1.el6.x86_64
[root@dhcp201-154 run]# 


When we restart the glusterd service, /var/run/gluster.pid file is updated with the PID of glusterd.

--
[root@dhcp201-154 run]# pwd
/var/run
[root@dhcp201-154 run]# ll -h | grep glusterd.pid 
-rw-r--r--. 1 root      root         5 Jun  1 04:32 glusterd.pid
[root@dhcp201-154 run]# cat glusterd.pid 
6908
[root@dhcp201-154 run]# ps -ef | grep -i glusterd
root      6908     1  0 04:32 ?        00:00:00 /usr/sbin/glusterd --pid-file=/var/run/glusterd.pid
--