JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for LCG-ROLLOUT Archives


LCG-ROLLOUT Archives

LCG-ROLLOUT Archives


LCG-ROLLOUT@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

LCG-ROLLOUT Home

LCG-ROLLOUT Home

LCG-ROLLOUT  April 2008

LCG-ROLLOUT April 2008

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Publishing local accounted data

From:

Alastair Duncan <[log in to unmask]>

Reply-To:

LHC Computer Grid - Rollout <[log in to unmask]>

Date:

Mon, 21 Apr 2008 13:22:47 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (205 lines)

Hi Carsten,

What you can attempt is to setup a continuous consumer on the command line

set query continuous
select * from LcgRecords WHERE ExecutingSite = 'GSI-LCG2'

By default this will be for 60 seconds change this to longer if necessary. eg. 
set timeout 120

Then from another terminal run your publishing code so see if the data is 
published continuously. If it isn't then have a look in your MON log files to 
see if there is any indiction of any 
problems. /var/log/glite/rgma-server/rgma-server.log

You can also look on the inspector to see if the producer has been created.

https://rgma19.pp.rl.ac.uk:8443/Inspector/Main.do/getSiteStatus?serviceType=primary&siteName=lcg01.gsi.de&portNumber=8443&lookupType=statusDetails

I noticed that a producer had been started while I was checking
  	[C-L--]Query type  	16Last contact (mins)  	6Last registry update (mins)  	
20Termination interval (mins)  	 Mon Apr 21 10:13:54 UTC 2008

Client hostname  LcgRecordsTable  Table count
 688151444ID  	 grid13.gsi.de 		1

Query type	Last contact (mins)Last registry update (mins) 
[C-L--]		16				6

Termination interval (mins)	Time created
20					Mon Apr 21 10:13:54 UTC 2008

And clicking the id shows that one tuple was inserted and that there was 1 
consumer attached and that was at goc01.grid-support.ac.uk is there any 
particular reason why you

I've done a query using the 

select * from LcgRecords WHERE ExecutingSite = 'GSI-LCG2' 

and this at present is returning ~250 records(13:18BST). This was not working 
earlier today. I'm attempting at present so figure out what could be the 
cause of the problems.

I'm curious why you think the remote DB is running on rgma20.pp.rl.ac.uk, this 
machine is archiving some of the Glue tables but not LcgRecords. The archiver 
for LCGRecords is goc01.grid-support.ac.uk but you don't need to query these 
machines directly this should be done via your own mon box.

The code you have running on your MON box is pretty old now 
5.0.31 the latest release is 5.0.49 

regards

Alastair

On Monday 21 April 2008 10:01:49 Preuss, Carsten wrote:
> Hello Jeff,
>
> thanks for your reply.
>
>
> rgma> select * from GlueSite where Name='GSI-LCG2'
>
> +--------------+----------+--------------------------+-------------------+-
>-------------------+-------------------+--------------------+----------+----
>-------+-------------------+-----------------+-----------------+
>
> | UniqueId     | Name     | Description              | SysAdminContact   |
> | UserSupportContact | SecurityContact   | Location           | Latitude |
> | Longitude | Web               | MeasurementDate | MeasurementTime |
>
> +--------------+----------+--------------------------+-------------------+-
>-------------------+-------------------+--------------------+----------+----
>-------+-------------------+-----------------+-----------------+
>
> | lcg01.gsi.de | GSI-LCG2 | No description available | [log in to unmask] |
> | [log in to unmask]  | [log in to unmask] | Darmstadt, Germany | 49.51    |
> | 8.39      | http://www.gsi.de | 2008-04-21      | 08:01:05        |
>
> +--------------+----------+--------------------------+-------------------+-
>-------------------+-------------------+--------------------+----------+----
>-------+-------------------+-----------------+-----------------+ 1 rows
>
> This works fine.
>
> Publishing data via RGMA command line works. The data are published correct
> (we do this via the RGMA on the CE).
>
> So it seems thta I have a problem with the python code itself.
>
> One point in the code that is not clear to me is :
>
>          predicate = "WHERE (ExecutingSite='GSI-LCG2')"
>
> I'm not sure, if this is the right statement for this variable.
>
>
> Cheers,
> Carsten.
>
> -----------------------------------------
> Carsten Preuss
> Gesellschaft fuer Schwerionenforschung mbH
> IT
> Planckstr. 1, D-64291 Darmstadt, Germany
> phone: +49-6159-71-1339
>
> -----------------------------------------
>
>
>
> -----Original Message-----
> From: LHC Computer Grid - Rollout on behalf of Jeff Templon
> Sent: Mon 21.04.2008 09:53
> To: [log in to unmask]
> Subject: Re: [LCG-ROLLOUT] Publishing local accounted data
>
> Hi,
>
> Do you have basic RGMA connectivity?  If you use the rgma command line
> tool, on the same node from which you are trying to publish, and you say
>
>     show tables
>
> and e.g.
>
>     select * from GlueSite
>
> what do you see?
>
> It could be either that your MON box is not working right and hence data
> never makes it out of your site, OR it could be that the archiver (or
> whatever they call it these days) is not eating the RGMA tuples and putting
> them into the database.
>
> If the commands above work, you could try publishing a tuple by hand, using
> the command line, and verifying that it actually got published.
>
> 					JT
>
> --On 21 April 2008 08:03:29 +0200 "Preuss, Carsten" <[log in to unmask]> wrote:
> > Hello all,
> >
> > currently we are trying to publish local accounted jobs via RGMA.
> >
> > The first step was to do this via building LcgRecords and writing them to
> > the DB on the MON node.
> > The entrys were builded correctly but were ignored/not published by APEL.
> >
> > The next step, to publish the data directly via the RGMA-PYTHON-API was
> > also unsuccessfull.
> > I followed the example from the
> >
> > "R-GMA User Guide for Python Programmers"
> >
> > as described in the chapter
> >
> > "4. PRIMARY PRODUCER EXAMPLES"
> >
> > ...
> >     try:
> >         storage = rgma.Storage(rgma.StorageType.MEMORY)
> >         properties = rgma.ProducerProperties(storage)
> >         terminationInterval = rgma.TimeInterval(60, rgma.Units.MINUTES)
> >         producer = rgma.PrimaryProducer(terminationInterval, properties)
> >         predicate = "WHERE (ExecutingSite='GSI-LCG2')"
> >         latestRetentionPeriod = rgma.TimeInterval(60, rgma.Units.MINUTES)
> >         historyRetentionPeriod = rgma.TimeInterval(60,
> > rgma.Units.MINUTES) producer.declareTable("LcgRecords", predicate,
> > latestRetentionPeriod, historyRetentionPeriod)
> >         producer.insert(insert)
> >         producer.close()
> >     except (rgma.RGMAException, rgma.RemoteException,
> > rgma.UnknownResourceException), e:
> >         sys.stderr.write("RGMA Error: %s\n" % e)
> >         sys.exit(1)
> >
> >     except:
> >         sys.stderr.write("Unexpected error: %s\n" % sys.exc_info()[0])
> >         sys.exit(1)
> > ....
> >
> >
> > No Records appeared in the remote DB under
> > https://rgma20.pp.rl.ac.uk:8443/R-GMA/
> >
> > Unfortunately I got also no error messages from SQL, RGMA or PHYTON.
> >
> > Has anybody already experiences with this stuff?
> >
> >
> > Thanks in advantage,
> >
> > Carsten.
> >
> > -----------------------------------------
> > Carsten Preuss
> > Gesellschaft fuer Schwerionenforschung mbH
> > IT
> > Planckstr. 1, D-64291 Darmstadt, Germany
> > phone: +49-6159-71-1339
> >
> > -----------------------------------------

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
November 2023
June 2023
May 2023
April 2023
March 2023
February 2023
September 2022
June 2022
May 2022
April 2022
February 2022
December 2021
November 2021
October 2021
September 2021
July 2021
June 2021
May 2021
February 2021
January 2021
November 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
February 2018
January 2018
November 2017
October 2017
September 2017
July 2017
June 2017
May 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager