Yo,
rpm version:
bdii-3.3.7-1_sl3
here is the whole conf file
> BDII_PORT_READ=2170
> BDII_USER=lcgbdii
> BDII_BIND=mds-vo-name=local,o=grid
> BDII_PASSWD=none.yet
> BDII_SEARCH_FILTER='*'
> BDII_SEARCH_TIMEOUT=30
> BDII_BREATHE_TIME=60
> BDII_AUTO_UPDATE=yes
> BDII_AUTO_MODIFY=yes
> BDII_DIR=/opt/bdii/
> BDII_UPDATE_URL=http://grid-deployment.web.cern.ch/grid-deployment/gis/lcg2-bdii/dteam/lcg2-all-sites.conf
> BDII_UPDATE_LDIF=http://
> SLAPD=/opt/openldap/libexec/slapd
> SLAPADD=/opt/openldap/sbin/slapadd
> BDII_PORTS_WRITE="2171 2172 2173"
i am not sure how this got changed; what do you recommend?
let me know.
JT
Laurence Field wrote:
> Hi Jeff
>
> The second config line is not used if
>
> BDII_AUTO_MODIFY=no
>
> What version of the BDII do you have installed?
>
> Laurence
>
>
> Jeff Templon wrote:
>
>> Hi
>>
>> what about these lines in bdii.conf?? the second one looks very
>> suspicious
>>
>> BDII_UPDATE_URL=http://grid-deployment.web.cern.ch/grid-deployment/gis/lcg2-bdii/dteam/lcg2-all-sites.conf
>>
>> BDII_UPDATE_LDIF=http://
>>
>> JT
>>
>> Jeff Templon wrote:
>>
>>> Hi
>>>
>>> very strange; i checked the conf file and the NS is configured to use
>>> bosheks (the RB machine itself) as BDII.
>>>
>>> if i do an ldapsearch to bosheks
>>>
>>> ldapsearch -h bosheks.nikhef.nl -p 2170 -x -b "o=grid"
>>>
>>> the command prints a bit of header information and then just stops.
>>> command prompt doesn't come back, and neither does the ream of site
>>> information. this would certainly cause the WM to slow down.
>>>
>>> Really strange because I typed it twice, the first time it ran fine,
>>> the second time it hung.
>>>
>>> a /etc/init.d/bdii restart
>>>
>>> appears not to help much, and the log files don't either ...
>>>
>>> from bdii-fwd.log:
>>>
>>>> 20051108_124543 Now forwarding to port 2173 (genNr 3)
>>>> 20051108_124543 Reaped process 15186 (genNr 2)
>>>> 20051108_124544 [Connect from 192.16.186.252:36107]
>>>> 20051108_124544 [Connecting to localhost...done]
>>>> 20051108_124544 Forked process 15821 -> 2173
>>>> 20051108_124546 Reaped process 15821 (genNr 3)
>>>> 20051108_124717 Now forwarding to port 2171 (genNr 4)
>>>> 20051108_124717 [Connect from 192.16.186.252:36291]
>>>> 20051108_124717 [Connecting to localhost...done]
>>>> 20051108_124717 Forked process 16436 -> 2171
>>>> 20051108_124722 Reaped process 16436 (genNr 4)
>>>> 20051108_124944 Now forwarding to port 2172 (genNr 5)
>>>> 20051108_124944 [Connect from 192.16.186.252:36653]
>>>> 20051108_124944 [Connecting to localhost...done]
>>>> (
>>>
>>>
>>>
>>>
>>> and from bdii.log
>>>
>>>> TRIUMF-GC-LCG2: ldap_bind: Can't contact LDAP server
>>>> ru-Novgorod-NOVSU-LCG2: ldap_bind: Can't contact LDAP server
>>>> obsARMuk: ldap_bind: Can't contact LDAP server
>>>> Time for searches: 34 s
>>>> Time to sort: 1 s
>>>> Time to update DB: 4 s
>>>> Grabbing port 2170 for 2173
>>>> Tue Nov 8 12:50:29 CET 2005
>>>
>>>
>>>
>>>
>>> hmm the obsARMuk looks a bit suspicious.
>>>
>>> I will keep looking, any help appreciated.
>>>
>>> JT
>>>
>>> David Smith wrote:
>>>
>>>> On Tue, 8 Nov 2005, Jeff Templon wrote:
>>>>
>>>>
>>>>> our RB (bosheks) has been acting rather strangely today. from the
>>>>> WM daemon
>>>>> log file:
>>>>
>>>>
>>>>
>>>>
>>>> [...]
>>>>
>>>> Hi Jeff,
>>>>
>>>> In principal the Timed out message means that there was a very slow
>>>> response from the BDII. (The query and response are normally on the 1
>>>> second timescale). Which BDII does bosheks use? I notice that the
>>>> problem
>>>> seemed to appear at about 10:39 this morning and seems to have gone
>>>> again
>>>> since about 11:25. Do you know of any changes on the BDII between
>>>> those
>>>> times?
>>>>
>>>> Yours,
>>>> David
>>>>
|