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  July 2007

LCG-ROLLOUT July 2007

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Problems with gCE after latest updates

From:

Nuno Orestes Vaz Da Silva <[log in to unmask]>

Reply-To:

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

Date:

Wed, 11 Jul 2007 17:07:44 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (109 lines)

Can you please check if qsub from a pool account on the gCe is working?

And please make a job-logging-info -v 2 on the UI to know exactly the reason issued for failure.

Nuno

-----Original Message-----
From: LHC Computer Grid - Rollout on behalf of Antun Balaz
Sent: Wed 7/11/2007 5:03 PM
To: [log in to unmask]
Subject: [LCG-ROLLOUT] Problems with gCE after latest updates
 
Hi,

After applying all the latest updates yesterday on all nodes, and
reconfiguring them, we are experiencing significant problems with gCE, and
just with this node.

The setup of our site assumes that lcg-CE and gCE share the same TORQUE server
installed on lcg-CE. After the update and reconfiguring all nodes, jobs sent
to lcg_CE are successfully executed, while those sent to gCE fail. They
actually reach batch system, where they are apparently sen to some WN (the
same as the jobs sent to lcg-CE which pass), but on WN there are no any traces
of gCE jobs arriving in pbs_mom logs (while lcg-CE jobs are logged correctly).

On TORQUE server I see the following traces of such a job sent to gCE (I am
mapped to dteam004):

[root@ce root]# showq -r| grep dteam004
             29138+ R DEF ------      1.0 qo  dteam004    dteam     wn02     1
 2:02:00:00  Wed Jul 11 15:50:00


[root@ce root]# tracejob 29138
/var/spool/pbs/mom_logs/20070711: No such file or directory
/var/spool/pbs/sched_logs/20070711: No such file or directory

Job: 29138.ce.phy.bg.ac.yu

07/11/2007 15:49:59  S    enqueuing into dteam, state 1 hop 1
07/11/2007 15:49:59  S    Job Queued at request of [log in to unmask],
owner = [log in to unmask], job name = blahjob_fm2961, queue = dteam
07/11/2007 15:49:59  A    queue=dteam
07/11/2007 15:50:00  S    Job Modified at request of [log in to unmask]
07/11/2007 15:50:00  S    Job Run at request of [log in to unmask]

After some time, the job is put to Hold state:

[root@ce root]# showq | grep 29138
29138              dteam004       Hold     1  2:02:00:00  Wed Jul 11 15:49:59

No additional information is logged to pbs_server logs, nor there are any
traces on wn02 (where this job supposedly went) about the job 29138.

In gram_job_mgr_2420.log I see the series of messages identical (apart from
time stamps) to the ones below, which seems fairly usual to me.

Wed Jul 11 16:14:45 2007 JM_SCRIPT: New Perl JobManager created.
Wed Jul 11 16:14:45 2007 JM_SCRIPT: polling job 2479
7/11 16:14:45 JMI: while return_buf = GRAM_SCRIPT_JOB_STATE = 2
7/11 16:14:45 Job Manager State Machine (entering):
GLOBUS_GRAM_JOB_MANAGER_STATE_POLL1
7/11 16:14:55 Job Manager State Machine (entering):
GLOBUS_GRAM_JOB_MANAGER_STATE_POLL2
7/11 16:14:55 JMI: testing job manager scripts for type fork exist and
permissions are ok.
7/11 16:14:55 JMI: completed script validation: job manager type is fork.
7/11 16:14:55 JMI: in globus_gram_job_manager_poll()
7/11 16:14:55 JMI: local stdout filename =
/home/dteam004/.globus/.gass_cache/local/md5/4a/058426fba8e47fb45d3e95957ff6ea/md5/94/7c4fdd29d7104121ad40f4b6d4a524/data.
7/11 16:14:55 JMI: local stderr filename = /dev/null.
7/11 16:14:55 JMI: poll: seeking: https://gce.phy.bg.ac.yu:20046/2420/1184161703/
7/11 16:14:55 JMI: poll_fast: ******** Failed to find
https://gce.phy.bg.ac.yu/2420/1184161703/
7/11 16:14:55 JMI: poll_fast: returning -1 = GLOBUS_FAILURE (try Perl scripts)
7/11 16:14:55 JMI: cmd = poll
7/11 16:14:55 JMI: returning with success

Other files in /home/dteam004 look OK, e.g. SchedLog and MasterLog does not
reveal anything. Mapping is OK etc.

What is strange is the following: we have a bunch of SL4 gLite-3.0 WNs
installed in compatibility mode, and another bunch of native SL4 gLite-3.1
WNs. We first updated and reconfigured (as requested in the release notes)
lcg-CE, gCE, and gLite-3.0 WNs, and ran into these problems with gCE. Then we
verified that there are no problems if gCE jobs end up on gLite-3.1 WNs (which
were not updated). After these nodes are updated, they stopped working as well
for gCE jobs.

What I see is that there are no gahp processes on gCE, which are supposed to
be there when everything works. So maybe this is after all condor conf problem?

Any help would be appreciated.

Thanks, Antun

-----
Antun Balaz
Research Assistant
E-mail: [log in to unmask]
Web: http://scl.phy.bg.ac.yu/

Phone: +381 11 3713152
Fax: +381 11 3162190

Scientific Computing Laboratory
Institute of Physics, Belgrade, Serbia
-----

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

May 2024
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