Rob
I've attached the config files.
APEL was setup a while ago and was working until I installed LCG 2.5.0.
I think the problem then was APEL_DB_PASSWORD set wrongly in
site-info.def (now fixed). These are the databases and tables in
accounting:
mysql> show databases;
+------------+
| Database |
+------------+
| accounting |
| mysql |
| test |
+------------+
mysql> use accounting;
mysql> show tables;
+----------------------+
| Tables_in_accounting |
+----------------------+
| EventRecords |
| GkRecords |
| LcgProcessedFiles |
| LcgRecords |
| MessageRecords |
| RepublishInfo |
| SpecRecords |
+----------------------+
Our CE is ce.epcc.ed.ac.uk and our MON runs on the Classic SE at
glenmorangie.epcc.ed.ac.uk.
Thanks for your help,
Steve
> -----Original Message-----
> From: Byrom, R (Rob) [mailto:[log in to unmask]]
> Sent: 03 August 2005 07:24
> To: Testbed Support for GridPP member institutes; Steve Thorn
> Cc: Kant, D (Dave)
> Subject: RE: apel broken with LCG 2.6.0
>
> Hi Steve,
>
> I suspect there's a problem in how Yaim has configured these
> config files, can you send me a copy of the configs used on
> the mon box and ce?
>
>
> CE: /opt/glite/etc/glite-apel-pbs/parser-config-yaim.xml
> MON: /opt/glite/etc/glite-apel-publisher/publisher-config-yaim.xml
>
> I think the Yaim install has incorrectly configured the CE to
> use a deleteProcessor. This will delete all the db contents
> before carrying out a log parse!
>
> Btw, is this the first time you've set up the apel? If so,
> you'll need to install a mysql database on the rgma mon box.
> If you're just upgrading, make sure the databasename,
> username and password of your old accounting db are setup
> within the config file (it's assuming that you've setup a
> database called accounting - but this may not be the case).
>
> I've attached the new apel user guide, check the apel core
> installation notes (page 7) on how to create a new database
> (if required).
>
> Thanks,
>
> Rob
>
> -----Original Message-----
> From: Testbed Support for GridPP member institutes
> [mailto:[log in to unmask]] On Behalf Of Steve Thorn
> Sent: 02 August 2005 16:40
> To: [log in to unmask]
> Subject: apel broken with LCG 2.6.0
>
>
> Hello all,
>
> I've upgraded our CE and MON to 2.6.0. The crons on CE and
> MON give the following errors:
>
> CE# /opt/glite/bin/apel-pbs-log-parser -f
> /opt/glite/etc/glite-apel-pbs/parser-config-yaim.xml
> Tue Aug 2 15:35:09 UTC 2005: apel-pbs-log-parser - Read-in
> configuration: [quiet, d, c, e, recursiveEventFiles, g,
> recursiveGKFiles] [DBPassword=****, site=ScotGRID-Edinburgh,
> pbslog=/var/spool/pbs/server_priv/accounting,
> CEhost=gppce.test.ac.uk, GIIS=ce.epcc.ed.ac.uk,
> extraEventLogFile=[/home/toucan/pbslog00021123.gz,
> /home/toucan/pbslog00021100.log], gklog=/var/log,
> DBURL=jdbc:mysql://glenmorangie.epcc.ed.ac.uk:3306/accounting,
> DBUsername=accounting, mslog=/var/log, timeZone=UTC] Tue Aug
> 2 15:35:09 UTC 2005: apel-pbs-log-parser - ------ Starting
> the apel application ------ Tue Aug 2 15:35:09 UTC 2005:
> apel-pbs-log-parser - program aborted
> org.glite.apel.core.ApelException: Unable to setup a database
> connection: org.gjt.mm.mysql.Driver
> at org.glite.apel.core.db.MySQLImpl.<init>(MySQLImpl.java:93)
> at
> org.glite.apel.core.processor.DeleteProcessor.<init>(DeletePro
> cessor.jav
> a:31)
> at org.glite.apel.pbs.ApelLogParser.run(ApelLogParser.java:65)
> at
> org.glite.apel.pbs.ApelLogParser.main(ApelLogParser.java:274)
>
> MON# /opt/glite/bin/apel-publisher -f
> /opt/glite/etc/glite-apel-publisher/publisher-config-yaim.xml
> Tue Aug 2 15:32:14 UTC 2005: apel-publisher - Read-in configuration:
> [logenabled, j] [DBUsername=accounting,
> DBURL=jdbc:mysql://glenmorangie.epcc.ed.ac.uk:3306/accounting,
> DBPassword=****, site=ScotGRID-Edinburgh, republish=all] Tue
> Aug 2 15:32:14 UTC 2005: apel-publisher - ------ Starting
> the apel application ------ Tue Aug 2 15:32:14 UTC 2005:
> apel-publisher - program aborted
> org.glite.apel.core.ApelException: Unable to setup a database
> connection: org.gjt.mm.mysql.Driver
> at org.glite.apel.core.db.MySQLImpl.<init>(MySQLImpl.java:93)
> at
> org.glite.apel.publisher.AccountManager.<init>(AccountManager.java:69)
> at
> org.glite.apel.publisher.ApelPublisher.runJoinProcessor(ApelPu
> blisher.ja
> va:110)
> at
> org.glite.apel.publisher.ApelPublisher.run(ApelPublisher.java:68)
> at
> org.glite.apel.publisher.ApelPublisher.main(ApelPublisher.java:234)
>
> Any ideas?
>
> I suspect something is wrong with the mysql database but I
> have no idea how to debug it as I don't know what should be
> there. Is there any up-to-date documentation on this glite
> incarnation of apel?
>
> cheers
> Steve
> _________________________
> Dr Steve Thorn
>
> Systems Administrator
> National e-Science Centre
> 15 South College Street
> Edinburgh EH8 9AA
> United Kingdom
>
> Tel: +44 (0)131 650 9815
>
>
|