init script problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Marcus - 
Can you file a bug at http://bugs.gluster.com? 



Thanks, 

Craig 

-- 
Craig Carl 













Sales Engineer; Gluster, Inc. 
Cell - ( 408) 829-9953 (California, USA) 
Office - ( 408) 770-1884 
Gtalk - craig.carl at gmail.com 
Twitter - @gluster 
Installing Gluster Storage Platform, the movie! 
http://rackerhacker.com/2010/08/11/one-month-with-glusterfs-in-production/ 



From: "Marcus Bointon" <marcus at synchromedia.co.uk> 
To: "Gluster General Discussion List" <gluster-users at gluster.org> 
Sent: Monday, September 27, 2010 1:29:31 PM 
Subject: init script problem 

I just ran into an odd issue with the init script in 3.0.5. It uses LSB's pidofproc to see if there's already a server running, however, pidofproc uses the full path to the binary to ensure it's looking at the right one, however, since gluster server and client use the same binary (glusterfs is a symlink to glusterfsd), if it's running a client but not a server, it will erroneously return the pid of the client, report that a server instance is already running (though fail to find a pid), and thus prevent the server from starting. Looking at the docs for pidofproc, it's supposed to fail to return a pid if it doesn't find a pid file, however it wasn't in this case. 

I solved it by stopping the client, then the server started ok, then I remounted the client and it all worked. 

Marcus 
_______________________________________________ 
Gluster-users mailing list 
Gluster-users at gluster.org 
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users 


[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux