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

Help for GRIDPP-STORAGE Archives


GRIDPP-STORAGE Archives

GRIDPP-STORAGE Archives


GRIDPP-STORAGE@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

GRIDPP-STORAGE Home

GRIDPP-STORAGE Home

GRIDPP-STORAGE  November 2005

GRIDPP-STORAGE November 2005

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: FTS error messages

From:

brian davies <[log in to unmask]>

Reply-To:

brian davies <[log in to unmask]>

Date:

Fri, 18 Nov 2005 15:13:48 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (127 lines)

thanks for the info andrew. wed do not have a tape storage. think the
problem is just high load of dcache and/or fts at ral. thing which
seems stanege is that i started with having the fts channel to allow
six concurrent file transfers at once.
i then also saw that the first six files of any submit were fine but
the following were broken.( though the odd one here and there get
through  eoither first time rouind or on the retry)
regards
brian

On 18/11/05, Andrew C. Smith <[log in to unmask]> wrote:
> Hi Brian,
>
> I have been working with FTS for the last three months or so
> integrating it with
> LHCb's grid software so I can appreciate the confusion with the errors it
> returns. The one you mention is a particularly special though as it does
> finally insist that the error was a success(?!)...
>
> Failed on SRM put: Failed To Put SURL. Error in srm__put: SOAP-ENV:Client -
> CGSI-gSOAP: Error reading token data: Success
>
> There are a few other errors that I have come across regularly since using the
> FTS:
>
> 'Failed on SRM get: SRM getRequestStatus timed out on get'
>
> This error is often occurs when trying to transfer a file that is not already
> staged in disk cache. When the FTS goes to the SRM it performs an SRM Get and
> will wait for 1 minute for the SRM to return the tURL. If the file is on tape
> the SRM will retrieve the file to disk before returning the tURL. The problem
> is that the file retrieval from tape will most likely take longer than the 1
> minute the FTS Agent waits for.  There is no state in the FTS state machine to
> allow it to deal with a non-blocking 'stage-in'. To overcome this problem LHCb
> staged the data to be transferred for SC3 in CERN Castor. The staging problem
> is known by the developers and changes to the state machine to support
> asyncronous staging in is on the list of things to be added.
>
> There are also a few similar errors to the one you mentioned this
> morning which
> result from the FTS service not being able to contact the endpoint, possibly
> due to a large load:
>
> Failed on SRM get: Cannot Contact SRM Service. Error in srm__ping:
> SOAP-ENV:Client - CGSI-gSOAP: Error reading token data: Success
>
> Failed on SRM put: Failed To Put SURL. Error in srm__put: SOAP-ENV:Client -
> CGSI-gSOAP: Error reading token data: Success
>
> SRMPUT Operation Timed out.
>
> TRANSFER - Transfer time out
>
> Failed on SRM put: SRM getRequestStatus timed out on put
>
> If all the files in your transfer are getting similar errors to this
> the machine
> is probably down or the service misconfigured. Although usually it is
> only a few
> files (if any) that experience this. Resubmitting the transfer will usually
> result in success.
>
> There are a couple of errors which can cause a little bit of trouble:
>
> Failed on SRM put: SRM getRequestStatus timed out on put; also failing to do
> 'advisoryDelete' on target
>
> Can occur when the load on the target machine is high. The problem being that
> when the FTS fails to do the advDel you are left with a (corrupted) file entry
> in the SE filesystem. For Castor systems this is not a problem because castor
> allows files to be overwritten by default. But, with dCache this is not the
> case and if the transfer is retried you get the following:
>
> Failed on SRM put: Failed SRM put  on
> httpg://srm.grid.sara.nl:8443/srm/managerv1 ; id=-2147372632 call. Error is
> RequestFileStatus#-2147372631 failed with error:[ GetStorageInfoFailed : file
> exists, cannot write ]
>
> Which means you have to delete the file by hand before resubmitting, which can
> be annoying if you are transferring 1000s of files. This problem was raised at
> a recent FTS workshop and the developers are working to make the differing
> behaviour of Castor/dCache/DPM SRMs transparent to the users of FTS.
>
> It was also mentioned at the workshop that some of the experiments
> would like to
> see more instructive error messages so after a while these might dissapear.
> Until then you will have to put up with 'Error: Success' ;)
>
> Cheers,
> Andrew.
>
> Quoting Derek Ross <[log in to unmask]>:
>
> > Fraser Speirs wrote:
> >> On 18 Nov 2005, at 11:54, Brian Davies wrote:
> >>
> >>> Failed on SRM get: Failed To Get SURL. Error in srm__get: SOAP-
> >>> ENV:Client - CGSI-gSOAP: Error reading token data: Success
> >>> Also get them with
> >>> Failed on SRM get: Cannot Contact SRM Service. Error in srm__ping:
> >>> SOAP-ENV:Client - CGSI-gSOAP: Error reading token data: Success
> >>
> >>
> >> Hi Brian,
> >>
> >> Yes, I've seen that today as well:
> >>
> >>> Failed on SRM get: Cannot Contact SRM Service. Error in srm__ping:
> >>> SOAP-ENV:Client - CGSI-gSOAP: Error reading token data: Success
> >>
> >>
> >> This is a transfer on the RAL-GLA channel from
> >> dcache.gridpp.rl.ac.uk  to our DPM on se2-gla.scotgrid.ac.uk.
> >>
> >> I know Jamie's seen the same thing under his DN.
> >>
> >
> > Hi,
> >
> > They're due to the FTS timing out talking to the SRM at
> > dcache.gridpp.rl.ac.uk due to that system being heavily loaded. We're
> > looking at how to improve this.
> >
> > Derek
> >
>

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 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
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 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
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004


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