(r12) BDII < EGEE

EGEE Web>InformationSystem>BDII (revision 12) (raw view)~~EditAttachPDF~~
---+ Berkeley Database Information Index V5

<strong>Note: This page is no longer maintained. For up to date information on Information Systems, please check the [[https://tomtools.cern.ch/confluence/display/IS/Home][Information System online documentation.]]</strong> 

<!--
*Note: For information on BDIIv4 please see [[BDIIv4][this documentation]]*. 

%TOC%
---++ Overview

The Berkeley Database Information Index (BDII) consists of a standard [[http://www.openldap.org/doc/admin22/intro.html#What%20is%20LDAP][LDAP]] database which is updated by an external process. The update process obtains [[http://www.openldap.org/doc/admin22/dbtools.html#The%20LDIF%20text%20entry%20format][LDIF]] from a number of sources and merges them. It then compares this to the contents of the database and creates an LDIF file of the differences. This is then used to update the database.

<img alt="bdii.png" src="%ATTACHURLPATH%/bdii.png" />

---++ Configuration

The BDII requires four configuration files:
   * /opt/bdii/etc/bdii.conf
   * /opt/bdii/etc/bdii-slapd.conf
   * /opt/bdii/etc/default.ldif

---+++ bdii.conf

This configuration file is used to configure the BDII itself. The format is key/value pairs with an '=' sign as the separator. A default configuration file comes with the BDII. This may require editing in order for the BDII to function as desired. The table belows describes the key/value pairs found in the configuration file.

| *Key* | *Typical Value* | *Description* |
| BDII_LOG_FILE | /var/log/bdii/bdii-update.log |  The log file for the BDII update process |
| BDII_LOG_LEVEL | ERROR | The log level for the update process [ERROR, WARNING, INFO, DEBUG ] |
| BDII_LDIF_DIR | /opt/glite/etc/gip/ldif | The directory containing LDIF files |
| BDII_PROVIDER_DIR | /opt/glite/etc/gip/provider | The directory containing information providers |
| BDII_PLUGIN_DIR | /opt/glite/etc/gip/plugin | The directory containing plugins |
| BDII_BIND | mds-vo-name=local,o=grid | The bind point of the database |
| BDII_PORT | 2170 | The port which is used for the LDAP server |
| BDII_VAR_DIR | /var/bdii | The directory to use by the BDII for writing data |
| BDII_BREATHE_TIME | 120 | Time to wait before updating the next database |
| BDII_READ_TIMEOUT | 300 | Time to wait for LDAP sources to return |
| BDII_ARCHIVE_SIZE | 0 | The number of updates that the changes should be logged |
| BDII_USER | edguser | The user runing the update process and the slapd databases |
| FIX_GLUE | yes | Fixes some common schema errors like publishing duplicate attributes |
| SLAPD_CONF | /opt/bdii/etc/bdii-slapd.conf | The LDAP database configuration file to use. |

---++ Starting and Stopping the BDII

The BDII is started and stopped by a daemon script =/etc/init.d/bdii=

---++ File Locations and Descriptions

The following table contains a list of files and locations which may be useful during troubleshooting.

| *Location* | *Description* |
| /opt/bdii/etc/bdii.conf | BDII configuration file |
| /opt/bdii/etc/bdii-slapd.conf | The slapd.conf template for use with the bdii |
| /opt/bdii/etc/default.ldif | A default LDIF file to populate the bdii |
| /etc/init.d/bdii | BDII init.d script |
| /opt/bdii/bin/bdii-update | Main update script |
| /opt/bdii/bin/bdii-proxy | Creates proxy for the BDII |
| /var/log/bdii/bdii-update.log | The BDII log file |
| /var/run/bdii-update.pid | The bdii-update.pid of the main process |
| /opt/bdii/var/2171 | Directory containing slapd data/config for the running instance |

---++ Running Processes

When a BDII is started, the following processes run:
   * One multithreaded slapd process.The number of (active) threads may depend on the query load and/or the /opt/bdii/etc/bdii-slapd.conf file.

   * 1 bdii-update process.
   * Periodically, one ldapadd, ldapdelete or ldapmodify process.

---++ Monitoring the BDII Instance

Status information about the BDII is available by querying the *o=infosys* root for the UpdateStats object. This entry contains a number of metrics relating to the latest update such as the time to update the database and the total number of entries. And example of such entry is shown below.

<pre>dn: Hostname=lxbra2510.cern.ch,o=infosys
objectClass: UpdateStats
Hostname: lxbra2510.cern.ch
FailedDeletes: 0
ModifiedEntries: 4950
DeletedEntries: 1318
UpdateTime: 150
FailedAdds: 603
FailedModifies: 0
TotalEntries: 52702
QueryTime: 8
NewEntries: 603
DBUpdateTime: 11
ReadTime: 0
PluginsTime: 4
ProvidersTime: 113
</pre>

The following table shows the meaning of these metrics: <noautolink>
| *Metric* | *Description* |
| Hostname | The hostname of the BDII instance |
| FailedDeletes | The number of delete statements which failed |
| ModifiedEntries | The number of objects to modify |
| DeletedEntries | The number of objects to delete |
| UpdateTime | To total update time in seconds |
| FailedAdds | The number of add statements which failed |
| FailedModifies | The number of modify statements which failed |
| TotalEntries | The total number of entries in the database |
| QueryTime | The time taken to query the database |
| NewEntries | The number of new objects |
| DBUpdateTime | The time taken to update the database in seconds |
| ReadTime | The time taken to read the LDIF sources in seconds |
| PluginsTime | The time taken to run the plugins in seconds |
| ProvidersTime | The time taken to run the information providers in seconds |

</noautolink>

---+++ Nagios Plugins

Nagios plugins are available to monitor the bdii. For more details see the GStat [[http://www.cern.ch/gridinfo documentation]].

---++ glite-info-provider-ldap

This information provider glite-info-provider-ldap enables information to be obtained by querying other BDIIs or LDAP servers. The script requires as input a configuration file containing a list of LDAP URLs.

<verbatim>
Usage: /opt/glite/libexec/glite-info-provider-ldap -c <config file> [-m <mds-vo-name>] [-v validity] -[d dynamic] [-t timeout] [-s size] 

This information provider takes a list of LDAP urls from the configuration
file and queries the LDAP sources. It then merges the results and modifies
the dn to append the mds-vo-name as specified on the command line.
The configuration file has lines typically with the following format:

entity  ldap://host.domain:2170/mds-vo-name=something,o=grid

Comments starting with "#" and are ignored.

Options:

    -c  The configuration file listing all the LDAP URLs.

    -m  The mds-vo-name which should be used.

    -h  Displays this helpful message.

    -d  This option will change the search filter to only
        retrieve the dynamic information. (currently not supported)

    -t  The timeout of the ldapsearch in seconds.

    -v  The validity of the cache files in seconds.

    -s  Maximum file size in megabytes for a single source.
</verbatim>
-->
Attachments
Topic attachments
I	Attachment	History	Action	Size	Date	Who	Comment
png	bdii.png	r1	manage	37.2 K	2009-02-11 - 16:56	LaurenceField
Topic revision: r12 - 2012-10-15 - MariaALANDESPRADILLO
EGEE
Main.WebList
Welcome Guest
- Cern Search
- TWiki Search
- Google Search
EGEE All webs
Copyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback