Difference between revisions of "Information System Open Issues"
Line 3: | Line 3: | ||
Additional Details: https://wiki.egi.eu/wiki/UMD-1:UMD-1.3.0#emi.bdii-site.sl5.x86_64 | Additional Details: https://wiki.egi.eu/wiki/UMD-1:UMD-1.3.0#emi.bdii-site.sl5.x86_64 | ||
https://ggus.eu/tech/ticket_show.php?ticket=71578 - glite-BDII hangs under heavy network load | https://ggus.eu/tech/ticket_show.php?ticket=71578 - glite-BDII hangs under heavy network load | ||
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: | 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 | https://tomtools.cern.ch/jira/browse/IS-244 | ||
https://ggus.eu/tech/ticket_show.php?ticket=72561 - EMI1 top-bdii bug: missing /etc/bdii/gip/glite-info-site-defaults.conf | https://ggus.eu/tech/ticket_show.php?ticket=72561 - EMI1 top-bdii bug: missing /etc/bdii/gip/glite-info-site-defaults.conf | ||
Line 14: | Line 13: | ||
the consequence is that | the consequence is that | ||
[root@topbdii01 ~]# cat /var/lib/bdii/gip/provider/glite-info-provider-service-bdii-top | [root@topbdii01 ~]# cat /var/lib/bdii/gip/provider/glite-info-provider-service-bdii-top | ||
.... | .... | ||
DEFAULTS=/etc/bdii/gip/glite-info-site-defaults.conf | DEFAULTS=/etc/bdii/gip/glite-info-site-defaults.conf | ||
... | ... | ||
# Check for the existence of the configuration file. | # Check for the existence of the configuration file. | ||
if [ -f ${DEFAULTS} ]; then | if [ -f ${DEFAULTS} ]; then | ||
source ${DEFAULTS} | source ${DEFAULTS} | ||
fi | fi | ||
SITE_NAME=${SITE_NAME:-$(hostname -d) } | SITE_NAME=${SITE_NAME:-$(hostname -d) } | ||
.... | .... | ||
it sets the sitename equal to the topbdii hostname, that is wrong | it sets the sitename equal to the topbdii hostname, that is wrong | ||
the further consequence are critical errors appearing in the GSTAT2 | the further consequence are critical errors appearing in the GSTAT2 | ||
===== | |||
https://ggus.eu/tech/ticket_show.php?ticket=73102 - Ramdisk space usage on top BDII | |||
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 | |||
https://ggus.eu/tech/ticket_show.php?ticket=73406 - bdii crash | |||
another performance issue solved by installing openldap2.4 | |||
asked EMI to consider this version the default (it isn't yet) | |||
https://ggus.eu/tech/ticket_show.php?ticket=73823 - emi-bdii-top-1.0.0-1.sl5.x86_64 packaging issue | |||
2 issues in this ticket: | |||
- "chkconfig bdii on" to start up the BDII at boot => solved using the new glite-yaim-bdii, release with EMI 1 Update 6 | |||
- 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 | |||
https://ggus.eu/tech/ticket_show.php?ticket=73840 - bdii memory leak | |||
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 |
Revision as of 13:28, 11 November 2011
List of current problems affecting BDII and the Information System in general
Additional Details: https://wiki.egi.eu/wiki/UMD-1:UMD-1.3.0#emi.bdii-site.sl5.x86_64
https://ggus.eu/tech/ticket_show.php?ticket=71578 - glite-BDII hangs under heavy network load
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
https://ggus.eu/tech/ticket_show.php?ticket=72561 - EMI1 top-bdii bug: missing /etc/bdii/gip/glite-info-site-defaults.conf
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
https://ggus.eu/tech/ticket_show.php?ticket=73102 - Ramdisk space usage on top BDII
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
https://ggus.eu/tech/ticket_show.php?ticket=73406 - bdii crash
another performance issue solved by installing openldap2.4
asked EMI to consider this version the default (it isn't yet)
https://ggus.eu/tech/ticket_show.php?ticket=73823 - emi-bdii-top-1.0.0-1.sl5.x86_64 packaging issue
2 issues in this ticket:
- "chkconfig bdii on" to start up the BDII at boot => solved using the new glite-yaim-bdii, release with EMI 1 Update 6
- 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
https://ggus.eu/tech/ticket_show.php?ticket=73840 - bdii memory leak
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