Difference between revisions of "Middleware issues and solutions"
|Line 43:||Line 43:|
= WMS =
= WMS =
Revision as of 13:41, 15 November 2011
|Main||EGI.eu operations services||Support||Documentation||Tools||Activities||Performance||Technology||Catch-all Services||Resource Allocation||Security|
|Documentation menu:||Home •||Manuals •||Procedures •||Training •||Other •||Contact ►||For:||VO managers •||Administrators|
Purpose of this page is to document recurring middleware issues with broad impact and the respective solutions and/or workarounds.
This page is maintained by the Distributed Middleware Support Unit of EGI.
|EMI||VOMS||July 17, 2011||VOMS server fails with high number of VOs|
VOMS server fails with high number of VOs
VOMS server of gLite 3.2 is more memory greedy, it starts failing when configured to serve more than 10 (approx.) VOs.
Change -XX:MaxPermSize parameter of CATALINA_OPTS to the value of at least 512m in /etc/tomcat5/tomcat5.conf
CATALINA_OPTS="-Xmx1508M -server -Dsun.net.client.defaultReadTimeout=240000 -XX:MaxPermSize=512m"
* soft nofile 2048 * hard nofile 2048
GGUS ticket #72136
BDII does not start at SE node
BDII daemon does not start correctly at SE node, yielding the service not to be published to GOC, etc. Symptoms are error messages:
# service ldap restart Stopping slapd: [ OK ] Checking configuration files for slapd: bdb_db_open: Warning - No DB_CONFIG file found in directory /var/lib/ldap: (2) Expect poor performance for suffix dc=my-domain,dc=com. config file testing succeeded [ OK ] Starting slapd: [ OK ]
The problem is caused by settting the BDII_USER variable in site-info.def, which causes incorrect permission settings on some files slapd uses. This variable should not be set at SE nodes, it's intended for BDII node only.