Contents
Checks in the Computing Element
- Make sure that you have java properly installed and configured (Java 1.5 for SL4, Java 1.6 for SL5; please use openjdk in SL5 nodes).
# java -version java version "1.5.0_16" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-b02) Java (TM) Server VM (build 1.5.0_16-b02, mixed mode)
- Make sure that you can contact mysql server running in your gLite-APEL from your CE
telnet "FQDN gLite-APEL" 3306
- Check that you have /etc/cron.d/apelparser configured and active
Be sure that user accounting can access database accounting in your gLite-APEL from your CE. Access data information is configured in /etc/glite-apel-pbs/parser-config-yaim.xml (built by yaim).
Be sure that the LRMS accounting information is accessible in your CE, and properly configured in /etc/glite-apel-pbs/parser-config-yaim.xml (under EventLogProcessor tag).
- Check the last log information from /var/log/apel.log for errors, or run the content of /etc/cron.d/apelparser in the prompt.
Checks in the gLite-APEL
- Make sure that you have java properly installed and configured (Java 1.6 for SL5; please use openjdk in SL5 nodes).
# java -version java version "1.6.0_17" Runtime Environment ( 1.7.5) (rhel-1.16.b17.el5-x86_64) 64-Bit Server VM (build 14.0-b16, mixed mode)
- Make sure mysql server running in up and running
# service mysqld status mysqld (pid 1064) is running...
- Check that you have /etc/cron.d/glite-apel-publisher configured and active
Be sure that user accounting can access mysql database accounting from the localhost. Access data information is configured in /etc/glite-apel-publisher/publisher-config-yaim.xml (built by yaim).
- Check the last log information from /var/log/apel.log for errors, or run the content of /etc/cron.d/glite-apel-publisher in the prompt
- If necessary, log into mysql, and execute the following comands to check what was the last day you received accounting data
mysql> use accounting; mysql> SELECT ExecutingSite, COUNT(*), MIN(EventDate), MAX(EventDate) FROM LcgRecords GROUP BY 1; (...) +---------------+----------+----------------+----------------+ | LIP-Lisbon | 3109853 | 2008-06-06 | 2011-01-17 | +---------------+----------+----------------+----------------+ 1 row in set (16.20 sec)
Summary reports and rnagios tests
- After some successfully publishing, the following web pages (used by rnagios tests) may take one day to be updated
Troubleshooting
javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown
Error: Tue Oct 4 16:34:39 UTC 2011: apel-publisher - program aborted org.glite.apel.core. : org.glite.apel.core. : javax.jms.JMSException: Could not connect to broker URL: ssl://apel-broker.esc.rl.ac.uk:61617. Reason: javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown (...)
- Check that your certificate is valid
openssl x509 -text -noout -in /etc/grid-security/hostcert.pem
- Check which java version are you using
# java -version java version "1.6.0_20" Runtime Environment ( 1.9.8) (rhel-1.22.1.9.8.el5_6-x86_64) 64-Bit Server VM (build 19.0-b09, mixed mode)
- Check if the /usr/bin/keytool link is coherent with the java version you are using
# ll /usr/bin/keytool lrwxrwxrwx 1 root root 49 Oct 6 11:41 /usr/bin/keytool -> /usr/lib/jvm/jre-1.6.0-openjdk.x86_64/bin/keytool
- Check if key_trust_store_maker.sh script runs OK
# /opt/glite/share/glite-apel-publisher/scripts/key_trust_store_maker.sh
- Try to run glite-apel-publisher content manually
# env APEL_HOME=/opt/glite /opt/glite/bin/apel-publisher -f /opt/glite/etc/glite-apel-publisher/publisher-config-yaim.xml
java.util.concurrent.TimeoutException: APEL Consumer did not respond to a request for confirmation of pre-published data
Increase the ConsumerTimeout value in APEL configuration.
Index
No Pages to show