Hi 

If you do rpm -ql globus-gridftp-server
I think you will find that that package is installing in /usr/share
not where yaim (or the gridftp start up scripts) are looking for it. Which seems to be the old glite location. 

Something overwritten by cfengine or whatever management tool you may be using? 

Anyway is gridftp running - if it is all working then I guess there is no problem - but perhaps bear in mind in case it comes and bites you later .


Wahid

On 10 Apr 2012, at 10:23, Santanu Das wrote:

Thanks Wahid, completely overlooked the globus-gridftp-server error.
BTW, it's certainly not from epel repo.

[root@disk12 bin]# rpm -qi globus-gridftp-server
Name        : globus-gridftp-server        Relocations: (not relocatable)
Version     : 6.5                               Vendor: (none)
Release     : 4.1.el5                       Build Date: Mon 12 Mar 2012 19:49:24 GMT
Install Date: Tue 03 Apr 2012 09:58:00 BST      Build Host: lscf28
Group       : System Environment/Libraries   Source RPM: globus-gridftp-server-6.5-4.1.el5.src.rpm
Size        : 394205                           License: ASL 2.0
Signature   : DSA/SHA1, Mon 12 Mar 2012 21:40:42 GMT, Key ID e1eb6726b4d025b3
URL         : http://www.globus.org/
Summary     : Globus Toolkit - Globus GridFTP Server
In fact, no DPM rpms are installed from epel repo:

[root@disk12 bin]# for tx in $(rpm -qa); do echo -e "$tx\t: `rpm -qi $tx | \
grep -o 'Vendor:.*[^ ]'`"; done | grep -i "Fedora Projec" | awk '{print $1}'
fetch-crl-2.8.5-1.el5
perl-XML-DOM-1.44-2.el5
perl-XML-RegExp-0.03-2.el5
w.r.t the warranting, disk12 is mentioned in the site-info.def, this way: 

[root@disk12 bin]# egrep 'disk12|DPM_D12' /post-config/Script/source/site-info_SL5x.def
DPM_D12=disk12.$MY_DOMAIN
DPM_FILESYSTEMS="$DPM_D01:/dpm_data $DPM_D02:/dpm_data $DPM_D03:/dpm_data $DPM_D04:/dpm_data \
$DPM_D05:/dpm_data $DPM_D06:/dpm_data1 $DPM_D06:/dpm_data2 $DPM_D07:/dpm_data1 \
$DPM_D07:/dpm_data2 $DPM_D08:/dpm_data $DPM_D09:/dpm_data $DPM_D10:/dpm_data1 \
$DPM_D10:/dpm_data2 $DPM_D11:/dpm_data1 $DPM_D11:/dpm_data2 $DPM_D12:/dpm_data1 $DPM_D12:/dpm_data2"

It's working fine for other disk-servers. dpm-qryconf is working just fine:

[root@serv02 ~]# dpm-qryconf --si
POOL dpmCam_2007 DEFSIZE 209.72M GC_START_THRESH 0 GC_STOP_THRESH 0 DEF_LIFETIME 7.0d DEFPINTIME 2.0h MAX_LIFETIME 1.0m MAXPINTIME 12.0h FSS_POLICY maxfreespace GC_POLICY lru RS_POLICY fifo GIDS 0 S_TYPE - MIG_POLICY none RET_POLICY R
                              CAPACITY 294.97T FREE 48.57T ( 16.5%)
  disk01.hep.phy.cam.ac.uk /dpm_data CAPACITY 8.25T FREE 165.01G (  2.0%) 
  [ .... ]
  disk11.hep.phy.cam.ac.uk /dpm_data2 CAPACITY 27.96T FREE 10.15T ( 36.3%) 
  disk12.hep.phy.cam.ac.uk /dpm_data1 CAPACITY 20.00T FREE 20.00T (100.0%) 
  disk12.hep.phy.cam.ac.uk /dpm_data2 CAPACITY 20.00T FREE 20.00T (100.0%)
Cheers,
Santanu

On 10/04/2012 10:05, Wahid Bhimji wrote:
[log in to unmask]" type="cite"> 
Hi 


You still have

Globus GridFTP binary not found: /opt/globus/sbin/globus-gridftp-server


which seems like some sort of mismatch of installations. Probably just worth checking everything is from EMI not EPEL (or glite)

The warnings at the end are not a problem. Though normally you would have that node mentioned in the DPM_FILESYSTEMS variable in site-info.def but it shouldn't stop it working (you can double check if you can see it in dpm-qryconf on the head node). 

Ultimate check is if files end up going there when copied.... 

The DAV NFS warnings are not a problem unless you want to experiment with DAV or NFS access .

Cheers

Wahid