Dear all,
I recently upgraded the EKP Karlsruhe site to LCG 2.6.0.
The only problem we still have is related to the R-GMA.
The tests on the corresponding nodes sometimes succeed, but more often
they fail.
> $RGMA_HOME/bin/rgma-client-check
> $RGMA_HOME/bin/rgma-server-check
During the configuration of the monitoring box I get some messages
concerning tomcat5 and JAVA_LIBDIR (like it was described in the manual
upgrade, I first deinstalled tomcat4, then I installed tomcat5...
Can someone tell me what that means and how I can resolve it?
Best regards,
Anja
[root@ekp-lcg-mon root]# /opt/lcg/yaim/scripts/configure_node
/opt/lcg/yaim/examples/site-info_260.def MON
Configuring config_upgrade ...
Configuring config_ldconf ...
Configuring config_sysconfig_edg ...
Configuring config_sysconfig_globus ...
Configuring config_edgusers ...
Configuring config_java ...
Configuring config_crl ...
Configuring config_gip ...
/opt/lcg/yaim/scripts/configure_node: line 456:
/opt/lcg/sbin/lcg-info-generic-config: No such file or directory
Setting up an R-GMA Gin...
- Configuring a gip information provider
- Not configuring an fmon information provider
- Not configuring a glite-ce information provider
Wrote configuration to: /opt/glite/etc/rgma-gin/gin.conf
All done
Stopping rgma-gin: [ OK ]
Starting rgma-gin: [ OK ]
/opt/lcg/yaim/scripts/configure_node: line 529:
/opt/lcg/libexec/lcg-info-dynamic-ce: No such file or directory
chmod: failed to get attributes of
`/opt/lcg/libexec/lcg-info-dynamic-ce': No such file or directory
Configuring config_globus ...
Configuring config_rgma_client ...
Welcome to the R-GMA setup utility
----------------------------------
Configuration written to:
/opt/glite/etc/rgma/rgma.conf
Configuring config_rgma_server ...
Info: using default install root: /opt/glite
Info: using default configuration file:
/opt/glite/etc/glite-security-trustmanager/config.properties
Info: using default configuration directory:
/opt/glite/etc/glite-security-trustmanager
Warning: /opt/glite/etc/glite-security-trustmanager/server.xml already
exists! Saving old one as
/opt/glite/etc/glite-security-trustmanager/server.xml.old.
Info: you can clean up using the following commands
mv -f /etc/tomcat5/server.xml.old-glite /etc/tomcat5/server.xml
rm -f /var/lib/tomcat5/server/lib/bcprov-jdk14-122.jar
rm -f /var/lib/tomcat5/server/lib/log4j-1.2.8.jar
rm -f /var/lib/tomcat5/server/lib/glite-security-trustmanager.jar
rm -f /var/lib/tomcat5/server/lib/glite-security-util-java.jar
rm -f /etc/tomcat5/log4j-trustmanager.properties
rm -f /opt/glite/etc/glite-security-trustmanager/server.xml
waiting for processes to exit [ OK ]
waiting for processes to exit
Starting tomcat5: /usr/bin/rebuild-jar-repository: error: JAVA_LIBDIR
must be set
/usr/bin/rebuild-jar-repository: error: JAVA_LIBDIR must be set
/usr/bin/rebuild-jar-repository: error: JAVA_LIBDIR must be set
/usr/bin/rebuild-jar-repository: error: JAVA_LIBDIR must be set
/usr/bin/rebuild-jar-repository: error: JAVA_LIBDIR must be set
/usr/bin/rebuild-jar-repository: error: JAVA_LIBDIR must be set
/usr/bin/rebuild-jar-repository: error: JAVA_LIBDIR must be set
[ OK ]
Shutting down rgma-publish-site: [ OK ]
Starting rgma-publish-site: [ OK ]
Stopping rgma-servicetool: stty: standard input: Inappropriate ioctl for
device
[ OK ]
Starting rgma-servicetool: stty: standard input: Inappropriate ioctl for
device
[ OK ]
Configuring config_apel_rgma ...
Configuring config_fmon_client ...
Stopping edg-fmon-agent: [ OK ]
Starting edg-fmon-agent: [ OK ]
Configuration Complete
|