# runuser -l ldap -c /var/lib/bdii/gip/plugin/glite-info-dynamic-ce
dn:
GLUE2ShareID=sl6_ops_cream-ge-1-kit.gridka.de_ComputingElement,GLUE2ServiceID=cream-ge-1-kit.gridka.de_ComputingElement,GLUE2GroupID=resource,o=glue
GLUE2ComputingShareMaxRunningJobs: 29424
GLUE2ComputingShareMaxCPUTime: 432000
GLUE2ComputingShareMaxWallTime: 432000
GLUE2ComputingShareServingState: Production
On 12.05.2014 11:42, Sam Skipsey wrote:
> Hi,
>
> One immediate question:
>
> When you test the provider scripts on the CREAM CE itself, you *are*
> doing so as the same user that CREAM uses to run them?
>
> Sam
>
>
> On 12 May 2014 10:23, Dimitri Nilsen <[log in to unmask]> wrote:
>> Hi,
>>
>> we are facing the problem that GLUE2ComputingShareMax* parameters are not
>> showing in bdii output properly. By running ldapsearch to the CREAM_CE we
>> always get default values:
>>
>> ldapsearch -xLLL -b o=glue -p 2170 -h cream-ge-1-kit | grep
>> GLUE2ComputingShareDefaultWallTime
>> GLUE2ComputingShareDefaultWallTime: 999999999
>> GLUE2ComputingShareDefaultWallTime: 999999999
>> GLUE2ComputingShareDefaultWallTime: 999999999
>>
>> however on the CREAM itself running provider scripts seems to be fine:
>> /usr/libexec/glite-info-dynamic-ge --info -c /etc/lrms/scheduler.conf
>> dn:
>> GLUE2ShareID=sl6_ops_cream-ge-1-kit.gridka.de_ComputingElement,GLUE2ServiceID=cream-ge-1-kit.gridka.de_ComputingElement,GLUE2GroupID=resource,o=glue
>> GLUE2ComputingShareMaxRunningJobs: 29424
>> GLUE2ComputingShareMaxCPUTime: 432000
>> GLUE2ComputingShareMaxWallTime: 432000
>> GLUE2ComputingShareServingState: Production
>> ..
>>
>> and
>> cat /var/lib/bdii/gip/plugin/glite-info-dynamic-ce
>> #!/bin/sh
>> /usr/libexec/glite-ce-check-submission-state
>> /etc/glite-ce-dbtool/creamdb_min_access.conf
>> retcode=$?
>> if [ $retcode = 1 ] || [ $retcode = 2 ] ; then
>> # Submissions disabled. Publish Draining
>> /usr/libexec/glite-info-dynamic-ge --info -c /etc/lrms/scheduler.conf |
>> sed -e 's/GlueCEStateStatus: Production/GlueCEStateStatus: Draining/'
>> else
>> # Submissions enabled. The default cluster.state will be used
>> /usr/libexec/glite-info-dynamic-ge --info -c /etc/lrms/scheduler.conf
>> fi
>>
>>
>> so what could the problem that bdii does not take right values from provider
>> scripts?
>>
>> Regards
>> Dimitri
>>
>> --
>> Dimitri Nilsen, Dipl.-Ing(FH)
>>
>> Karlsruhe Institute of Technology (KIT)
>> Steinbuch Centre for Computing
>> Kaiserstr. 12
>> 76131 Karlsruhe, Germany
>>
>> Tel.: +49 721 608 28607
>> Email: [log in to unmask]
--
Dimitri Nilsen, Dipl.-Ing(FH)
Karlsruhe Institute of Technology (KIT)
Steinbuch Centre for Computing
Kaiserstr. 12
76131 Karlsruhe, Germany
Tel.: +49 721 608 28607
Email: [log in to unmask]
|