Hi,
Sorry for the late reply. We were investigating the reason for this problem.
In this case problem looks like of a diffrent nature. The solution that you suggested works in case globus-mds refuses to start. We have gone through that excercise earlier and considered it even this time.
But in this case globus-mds starts and show OK status. sldap keeps on running at port 2135. But status shows globus-mds is stopped.
[root@CE root]# /etc/init.d/globus-mds restart
Stopping Globus MDS [FAILED]
Starting Globus MDS
Using sysconfig: /etc/sysconfig/globus
Using GLOBUS_LOCATION: /opt/globus
Using grid-functions: /etc/rc.d/init.d/grid-functions
Using configuration file: /etc/globus.conf
Using grid-mapfile: /etc/grid-security/grid-mapfile
Using cert: /etc/grid-security/hostcert.pem
Using key : /etc/grid-security/hostkey.pem
Executing: /opt/globus/sbin/grid_info_daemon - /opt/globus/sbin/grid-info-soft-register -log /var/tmp/edginfo-globus-mds.log -f /opt/globus/etc/grid-info-resource-register.conf -- /opt/globus/libexec/slapd -h ldap://ce.pakgrid.org.pk:2135 -f /opt/globus/etc/grid-info-slapd.conf -d 2 -u edginfo > /dev/null 2>&1 &
[ OK ]
[root@CE root]# ps -aux|grep 2135
root 24205 0.0 0.0 2140 1048 ? S 11:28 0:00 /bin/sh /opt/globus/sbin/grid-info-soft-register -log /var/tmp/edginfo-globus-mds.log -f /opt/globus/etc/grid-info-resource-register.conf -- /opt/globus/libexec/slapd -h ldap://ce.pakgrid.org.pk:2135 -f /opt/globus/etc/grid-info-slapd.conf -d 2 -u edginfo
edginfo 24248 0.1 0.1 18344 3952 ? S 11:28 0:13 /opt/globus/libexec/slapd -h ldap://ce.pakgrid.org.pk:2135 -f /opt/globus/etc/grid-info-slapd.conf -d 2 -u edginfo
root 24254 0.0 0.0 2128 1036 ? S 11:28 0:00 /bin/sh /opt/globus/sbin/grid-info-soft-register -log /var/tmp/edginfo-globus-mds.log -register -t mdsreg2 -h ce.pakgrid.org.pk -p 2135 -period 600 -dn Mds-Vo-Op-name=register, Mds-Vo-name=site, o=grid -daemon -t ldap -h ce.pakgrid.org.pk -p 2135 -ttl 1200
root 3032 0.0 0.0 4764 672 pts/6 S 13:49 0:00 grep 2135
[root@CE root]# /etc/init.d/globus-mds status
globus-mds is stopped
Again ldapsearch gives wrong info, as such it info is not being populated.
[root@CE root]# ldapsearch -x -H ldap://CE.pakgrid.org.pk:2135 -b mds-vo-name=local,o=grid|more
version: 2
#
# filter: (objectclass=*)
# requesting: ALL
#
# ce.pakgrid.org.pk, local, grid
dn: Mds-Host-hn=ce.pakgrid.org.pk,Mds-Vo-name=local,o=grid
objectClass: MdsComputer
objectClass: MdsComputerTotal
objectClass: MdsFsTotal
objectClass: MdsHost
objectClass: MdsMemoryRamTotal
objectClass: MdsMemoryVmTotal
objectClass: MdsNet
objectClass: MdsNetTotal
objectClass: MdsOs
Mds-Computer-isa: i686
Mds-Computer-Total-nodeCount: 1
Mds-Computer-platform: i686
Mds-Fs-Total-count: 4
Mds-Fs-Total-freeMB: 89597
Mds-Fs-Total-sizeMB: 129513
Mds-Fs-freeMB: 23612
Mds-Fs-freeMB: 46
Mds-Fs-freeMB: 64940
Mds-Fs-freeMB: 999
Mds-Fs-sizeMB: 39369
Mds-Fs-sizeMB: 89047
Mds-Fs-sizeMB: 98
Mds-Fs-sizeMB: 999
Mds-Host-hn: ce.pakgrid.org.pk
Mds-Memory-Ram-Total-freeMB: 293
Mds-Memory-Ram-Total-sizeMB: 1998
Mds-Memory-Ram-freeMB: 293
Mds-Memory-Ram-sizeMB: 1998
Mds-Memory-Vm-Total-freeMB: 1583
Mds-Memory-Vm-Total-sizeMB: 2047
Mds-Memory-Vm-freeMB: 1583
Mds-Memory-Vm-sizeMB: 2047
Mds-Net-Total-count: 2
Mds-Net-addr: 127.0.0.1
Mds-Net-addr: 203.135.53.244
Mds-Net-name: eth0
Mds-Net-name: lo
Mds-Net-netaddr: 127.0.0.0/8
Mds-Net-netaddr: 203.135.53.224/27
Mds-Os-name: Linux
Mds-Os-release: 2.4.21-47.EL.cernsmp
Mds-Os-version: 1 SMP Mon Jul 24 15:33:59 CEST 2006
Mds-keepto: 20080104082956Z
Mds-validfrom: 20080104082956Z
Mds-validto: 20080104082956Z
# memory, ce.pakgrid.org.pk, local, grid
dn: Mds-Device-Group-name=memory, Mds-Host-hn=ce.pakgrid.org.pk,Mds-Vo-name=lo
cal,o=grid
objectClass: MdsMemoryRamTotal
objectClass: MdsMemoryVmTotal
objectClass: MdsDeviceGroup
Mds-Device-Group-name: memory
Mds-validfrom: 20080104082956Z
Mds-validto: 20080104092956Z
Mds-keepto: 20080107032316Z
Mds-Memory-Ram-Total-sizeMB: 1998
Mds-Memory-Ram-Total-freeMB: 293
Mds-Memory-Vm-Total-sizeMB: 2047
Mds-Memory-Vm-Total-freeMB: 1583
Mds-Memory-Ram-sizeMB: 1998
Mds-Memory-Ram-freeMB: 293
Mds-Memory-Vm-sizeMB: 2047
Mds-Memory-Vm-freeMB: 1583
Any more suggestion?
Cheers,
Asif Osman
-----Original Message-----
From: LHC Computer Grid - Rollout on behalf of Rod Walker
Sent: Thu 1/3/2008 5:05 PM
To: [log in to unmask]
Subject: Re: [LCG-ROLLOUT] problem with running globus-mds
Hi,
This is one reason globus-mds won`t start (on the SE) - from our
logbook...
-----
/etc/init.d/globus-mds
would not start after move. Running by hand
/opt/globus/libexec/slapd -h ldap://srm.triumf.ca:2135 -f
/opt/globus/etc/grid-info-slapd.conf -d 1 -u edginfo
showed
could not open config file "/opt/glue/schema/ldap/Glue-CORE.schema" -
absolute path?
I added the ldap link to
ls -l /opt/glue/schema
total 8
lrwxrwxrwx 1 root root 29 Sep 17 22:54 ldap ->
/opt/glue/schema/openldap-2.0
drwxr-xr-x 2 root root 4096 Sep 15 23:07 openldap-2.0
drwxr-xr-x 2 root root 4096 Sep 15 23:07 openldap-2.1
The 2.1 version fails with a differnet error.
-----
Cheers,
Rod.
GIP.ldif
On Thu, 3 Jan 2008, Asif Osman wrote:
> Dear All,
>
> Happy new year!!!!!!!
>
> I am getting problem with running globus-mds. The service starts with OK status, but it stops afterwards:
>
> [root@CE etc]# /etc/init.d/globus-mds restart
> Stopping Globus MDS [FAILED]
> Starting Globus MDS
> Using sysconfig: /etc/sysconfig/globus
> Using GLOBUS_LOCATION: /opt/globus
> Using grid-functions: /etc/rc.d/init.d/grid-functions
> Using configuration file: /etc/globus.conf
> Using grid-mapfile: /etc/grid-security/grid-mapfile
> Using cert: /etc/grid-security/hostcert.pem
> Using key : /etc/grid-security/hostkey.pem
> Executing: /opt/globus/sbin/grid_info_daemon - /opt/globus/sbin/grid-info-soft-register -log /var/tmp/edginfo-globus-mds.log -f /opt/globus/etc/grid-info-resource-register.conf -- /opt/globus/libexec/slapd -h ldap://ce.pakgrid.org.pk:2135 -f /opt/globus/etc/grid-info-slapd.conf -d 2 -u edginfo > /dev/null 2>&1 &
> [ OK ]
> [root@CE etc]# /etc/init.d/globus-mds status
> globus-mds is stopped
>
> I tried again after killing slapd, but same pattern is repeated.
>
> This behaviour is shown after running the yaim configure.
>
> Please suggest any fix?
>
> Cheers,
> Asif Osman
>
>
--
Tel. +1 604 222 7667
|