ok.. noticed that running this from /root/ doesnt work, because it try
to write to current directory.(I have find out it with strace)
but running it from /tmp/ did the job.
BUT! :( running a ldapsearch from remote or localhost still have 444444
values.
hier is my scheduler.conf
# cat /etc/lrms/scheduler.conf
[Main]
static_ldif_file: /var/lib/bdii/gip/ldif/static-file-CE.ldif
static_glue2_ldif_file_computingshare:
/var/lib/bdii/gip/ldif/ComputingShare.ldif
outputformat: both
vomap :
atlasprd:atlas
[LRMS]
lrms_backend_cmd: /usr/libexec/lrmsinfo-pbs
and hier is a result from ldapsearch:
ldapsearch -xLLL -b o=grid -p 2170 -h localhost | grep Waiting
GlueCEStateWaitingJobs: 444444
GlueCEPolicyMaxWaitingJobs: 999999999
GlueCEStateWaitingJobs: 444444
GlueCEStateWaitingJobs: 444444
On 10/05/2012 02:37 PM, Dimitri Nilsen wrote:
> Hi Massimo,
>
> thanks, adjusting /etc/lrms/scheduler.conf helped.
> now I see results running /usr/libexec/lcg-info-dynamic-scheduler -c
> /etc/lrms/scheduler.conf
>
> but running it as ldap user (/sbin/runuser -s /bin/sh ldap -c
> "/usr/libexec/lcg-info-dynamic-scheduler -c /etc/lrms/scheduler.conf")
> still does'n have a result. which permissions/owners should have
> /usr/libexec/lcg-info-dynamic-scheduler, /etc/lrms/scheduler.conf
>
> Regards
> Dimitri
>
> On 10/05/2012 09:10 AM, Massimo Sgaravatto wrote:
>> On 10/05/2012 08:54 AM, Dimitri Nilsen wrote:
>>> Hi Massimo,
>>>
>>> thank you,
>>> now running /usr/libexec/vomaxjobs-maui -h cream-6-kit.gridka.de
>>> I get
>>> /usr/libexec/vomaxjobs-maui: command 'diagnose -g
>>> --host=cream-6-kit.gridka.de' exited with nonzero status
>>>
>>> the command "diagnose" is not know by the system.
>>> what is a "diagnose" command? which package is it from?
>>
>>
>> In "my" system, it is provided by maui-client
>>
>> PS: To debug, I suggest to run the commands as user ldap (the one
>> running bdii). E.g.:
>>
>> /sbin/runuser -s /bin/sh ldap -c
>> "/usr/libexec/lcg-info-dynamic-scheduler -c /etc/lrms/scheduler.conf"
>>
>> Cheers, Massimo
>>
>>
>>>
>>> Regards
>>> Dimitri
>>>
>>> On 10/05/2012 06:31 AM, Massimo Sgaravatto wrote:
>>>> I think there is something weird in your scheduler.conf
>>>> Mine is:
>>>>
>>>> [Main]
>>>> static_ldif_file: /var/lib/bdii/gip/ldif/static-file-CE.ldif
>>>> static_glue2_ldif_file_computingshare:
>>>> /var/lib/bdii/gip/ldif/ComputingShare.ldi
>>>> f
>>>> outputformat: both
>>>> vomap :
>>>> cmssgm:cms
>>>> cmsprd:cms
>>>> cmssilver:cms
>>>> cmssilver:cms
>>>> cmsgold:cms
>>>> cmsbronze:cms
>>>> cmsbronze:cms
>>>> dteamsgm:dteam
>>>> dteamprd:dteam
>>>> infngridsgm:infngrid
>>>> alicesgm:alice
>>>> aliceprd:alice
>>>> sgmtesters:testers.eu-emi.eu
>>>> piltesters:testers.eu-emi.eu
>>>> module_search_path : ../lrms:../ett
>>>> [LRMS]
>>>> lrms_backend_cmd: /usr/libexec/lrmsinfo-pbs
>>>> [Scheduler]
>>>> cycle_time : 0
>>>> vo_max_jobs_cmd: /usr/libexec/vomaxjobs-maui -h cream-38.pd.infn.it
>>>>
>>>>
>>>> This file is supposed to be created during yaim configuration (the
>>>> relevant functions are config_cream_gip_scheduler_plugin and
>>>> config_gip_sched_plugin_pbs)
>>>>
>>>>
>>>> Cheers, Massimo
>>>>
>>>>
>>>> On 10/04/2012 10:23 PM, Dimitri Nilsen wrote:
>>>>> Hi Govind,
>>>>>
>>>>> no, all GLUE2PolicyRule_s are correct and I do not see any errors in
>>>>> bdii log(like described in a known issue). Actually, the bdii log is
>>>>> empty. I thing because of this lines in bdii.conf:
>>>>> BDII_LOG_FILE=/var/log/bdii/bdii-update.log
>>>>> BDII_LOG_LEVEL=ERROR
>>>>>
>>>>> Bdii is running and I could connect to 2170 and get glue data more or
>>>>> less correct, except this Waiting/Running jobs.
>>>>>
>>>>> What I found is, that running
>>>>> /usr/libexec/lcg-info-dynamic-scheduler -c /etc/lrms/scheduler.conf
>>>>>
>>>>> doesn't provide any output at all.. but I thing, it should.
>>>>> how could I debug this?
>>>>>
>>>>> Regards
>>>>> Dimitri
>>>>>
>>>>> On 10/04/2012 07:01 PM, Govind Songara wrote:
>>>>>> Hi Dimitri,
>>>>>>
>>>>>> I think you are hit by known issue of GLUE2PolicyRule:
>>>>>> http://www.eu-emi.eu/products/-/asset_publisher/1gkD/content/cream-2
>>>>>>
>>>>>> Cheers
>>>>>> Govind
>>>>>>
>>>>>> On Thu, Oct 4, 2012 at 4:40 PM, Dimitri
>>>>>> Nilsen<[log in to unmask]> wrote:
>>>>>>> Hi
>>>>>>>
>>>>>>> after installing cream ce from emi 2, I am not able to get dynamic
>>>>>>> cluster
>>>>>>> info for such values as running/waiting jobs etc..
>>>>>>>
>>>>>>> by executing
>>>>>>> /usr/libexec/lcg-info-dynamic-scheduler -c /etc/lrms/scheduler.conf
>>>>>>> there is no output.
>>>>>>>
>>>>>>> hier ist scheduler.conf:
>>>>>>>
>>>>>>> [Main]
>>>>>>> static_ldif_file: /var/lib/bdii/gip/ldif/static-file-CE.ldif
>>>>>>> static_glue2_ldif_file_computingshare:
>>>>>>> /var/lib/bdii/gip/ldif/ComputingShare.ldif
>>>>>>> outputformat: both
>>>>>>> vomap
>>>>>>>
>>>>>>> what could be wrong? or how to configure it right?
>>>>>>>
>>>>>>> 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]
|