 |
 |
UPDATE: when the APEL consumer was restarted yesterday data started to appear. Daniela said Imperial publication looked OK yesterday afternoon. I've just checked RAL-LCG2 and that published OK this morning. MYEGEE for UK shows Birmingham and a couple of Irish sites passing the Apel-Pub tests at 2310 last night. I suspect most of you publish overnight so won't appear until the probe runs again. Not sure why Imperial doesn't pass though. More later. John > -----Original Message----- > From: Testbed Support for GridPP member institutes [mailto:TB- > [log in to unmask]] On Behalf Of J Coles > Sent: 05 January 2011 12:39 > To: [log in to unmask] > Subject: Re: Dteam & sites meeting @ 11am today > > Hi Daniela > > There are three tickets for APEL support to look at today and the one > from Chris Curtis covers the issue you are seeing: > https://gus.fzk.de/ws/ticket_info.php?ticket=65862. I would be inclined > to add a comment to that ticket that you also see the problem. I can > also add comments if anyone is unable to edit the ticket. > > Thanks, > Jeremy > > > On 5 Jan 2011, at 12:25, Daniela Bauer wrote: > > > Hi All, > > > >> 3) The RAL broker for APEL went down on 31st December as the log > file was too big. This has now been fixed but there will be a period > when the central accounting data is not as up-to-date as you would > expect. > > > > If I look in my logs I see: > > Wed Jan 5 11:51:03 UTC 2011: apel-publisher - Record/s found: 8735 > > Wed Jan 5 11:51:03 UTC 2011: apel-publisher - Checking Archiver is > Online > > Wed Jan 5 12:21:18 UTC 2011: apel-publisher - program aborted > > org.glite.apel.core.ApelException: > > java.util.concurrent.TimeoutException: APEL Consumer did not respond > > to a request for confirmation of pre-published data. Please contact > > APEL Support Staff. > > at org.glite.apel.publisher.AccountChecker.execute(Unknown > Source) > > at > org.glite.apel.publisher.AccountChecker.countArchivedRecords(Unknown > > Source) > > at > org.glite.apel.publisher.AccountManager.chkArchivedTuples(Unknown > > Source) > > at org.glite.apel.publisher.AccountManager.run(Unknown Source) > > at > org.glite.apel.publisher.ApelPublisher.runJoinProcessor(Unknown > > Source) > > at org.glite.apel.publisher.ApelPublisher.run(Unknown Source) > > at org.glite.apel.publisher.ApelPublisher.main(Unknown Source) > > Caused by: java.util.concurrent.TimeoutException: APEL Consumer did > > not respond to a request for confirmation of pre-published data. > > Please contact APEL Support Staff. > > ... 7 more > > > > > > I've just reran apel, but got the same result. > > Do I just wait or go ahead and file a ticket ? > > > > Cheers, > > > > Daniela