Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "Information System Open Issues"

From EGIWiki
Jump to navigation Jump to search
Line 16: Line 16:
== Glue2 Information ==
== Glue2 Information ==
It isn't still clear when Glue2 will be used (GSTAT still check Glue1.3 information): we don't know how the information are coherent.
It isn't still clear when Glue2 will be used (GSTAT still check Glue1.3 information): we don't know how the information are coherent.
We should check the information already published and find out any anomalies
We should check the information already published and find out any anomalies



Revision as of 15:06, 11 November 2011

List of current problems affecting BDII and the Information System in general

Known Issues

Known issues affecting the BDII version 1.0.1

Frequent Problems

  • Performance/Load issues: memory leak, stuck processes
    • often solved by intalling openldap2.4, but some of them have to be well investigated
    • openldap2.4 isn't installed by default yet
  • Past issues:
    • bdii user change from edguser to ldap
    • enabling the start of bdii daemon and disabling the ldap one when a machine boot

Glue2 Information

It isn't still clear when Glue2 will be used (GSTAT still check Glue1.3 information): we don't know how the information are coherent.

We should check the information already published and find out any anomalies

Tickets in open status

glite-BDII hangs under heavy network load

GGUS 71578

the installation of openldap2.4 should have solved the problem, but the ticket is still "on hold" status because there is a feature request to detect the hanging issue using the status command: https://tomtools.cern.ch/jira/browse/IS-244

EMI1 top-bdii bug: missing /etc/bdii/gip/glite-info-site-defaults.conf

GGUS 72561

Issue still present, also for the site-bdii

the consequence is that

[root@topbdii01 ~]# cat /var/lib/bdii/gip/provider/glite-info-provider-service-bdii-top
....
DEFAULTS=/etc/bdii/gip/glite-info-site-defaults.conf
...
# Check for the existence of the configuration file.
if [ -f ${DEFAULTS} ]; then
source ${DEFAULTS}
fi

SITE_NAME=${SITE_NAME:-$(hostname -d) }
....

it sets the sitename equal to the topbdii hostname, that is wrong

the further consequence are critical errors appearing in the GSTAT2


Ramdisk space usage on top BDII

GGUS 73102 the usage of ramdisk space kept increasing and eventually full in about two or three weeks (top BDII on a XEN virtual machine) adding dncachesize into /etc/bdii/bdii-top-slapd.conf and setting it to double of cachesize makes slower the memory usage increment, but it doesn't limit it


bdii crash

GGUS 73406 another performance issue solved by installing openldap2.4

asked EMI to consider this version the default (it isn't yet)


emi-bdii-top-1.0.0-1.sl5.x86_64 packaging issue

GGUS 73823

2 issues in this ticket:

  1. "chkconfig bdii on" to start up the BDII at boot => solved using the new glite-yaim-bdii, release with EMI 1 Update 6
  2. the file /opt/glite/etc/gip/top-urls.conf still ends up in '/opt/glite/etc' rather than '/etc/'.

It is created in

/etc/glite/glite-info-update-endpoints.conf
> rpm -qf /etc/glite/glite-info-update-endpoints.conf
glite-info-update-endpoints-2.0.7-1.el5.noarch


bdii memory leak

GGUS 73840

updated to glite-BDII_top 3.2.12 and increased the VM memory to 4 GB. The situation improved but still after few days the memory usage keeps increasing.

in the file /etc/bdii/DB_CONFIG suggested to comment out the following lines:

#set_flags DB_LOG_INMEMORY
#set_flags DB_TXN_NOSYNC

and the memory usage was reduced considerably; it isn't still clear which process causes the increase of i/o load