Hi Maarten
Thanks for looking into the problem. I have update crl manually. Let me
explain some more info about the setup. I have sudo access to the CE
only so I have not created the pool accounts through yaim, it was
created through NIS, I have created only glite, edginfo and edguser
account.
Globus-job-run command is not hanging when I try from my UI as expalined
in gocwiki link.
When I submit a job to ngsce-test it created around 40 folders in
/home/dtm004/.globus/job/ngsce-test.oerc.ox.ac.uk, most of them are
empty but stdout file in one of the folder, it is giving this error
Creating DSA key for ssh
/opt/globus/etc/globus-user-env.sh not found or unreadable
jw exit status = 1
It is a old problem with pbs, but we have already created symlink to all
wn's and its working because I can submit job from other CE using same
set of pool accounts.
Regards
Kashif
-----Original Message-----
From: Maarten Litmaath [mailto:[log in to unmask]]
Sent: 06 October 2009 11:40
To: Kashif Mohammad
Cc: LHC Computer Grid - Rollout
Subject: Re: [LCG-ROLLOUT] Job stay in running state
Hi Kashif,
> Globus-gma.log file is full of this
>
> https://ngsce-test.oerc.ox.ac.uk:64004/6465/1251116035/
> Mon Oct 5 14:24:12 2009:13965:WARN: Poll failed for job
> https://ngsce-test.oerc .ox.ac.uk:64007/15177/1254481706/ Mon Oct 5
> 14:24:12 2009:19030:WARN: Poll process terminated with error for job
> https://ngsce-test.oerc.ox.ac.uk:64007/15177/1254481706/
I started looking into that yesterday evening and found that often a
globus-job-run command to that CE just hangs. I suspect there is some
sort of network issue close to that CE. Either a hardware problem
(NIC/switch/...) or a firewall that does not like the rate at which
ports in the GLOBUS_TCP_PORT_RANGE are getting reused.
Check this Wiki page:
http://goc.grid.sinica.edu.tw/gocwiki/gridftp_works_only_once_within_a_m
inute_or_so
Today your CE has another problem:
$ uberftp ngsce-test.oerc.ox.ac.uk pwd
220 ngsce-test.oerc.ox.ac.uk GridFTP Server 2.3 (gcc32dbg,
1144436882-63) ready.
530-globus_xio: Authentication Error
530-globus_gsi_callback_module: Could not verify credential
530-globus_gsi_callback_module: Could not verify credential
530-globus_gsi_callback_module: Invalid CRL: The available CRL has
expired 530 End.
Is /etc/cron.d/fetch-crl present? Check /var/log/fetch-crl-cron.log.
|