On 01/16/2014 12:47 PM, Matt RB wrote:
> On 16/01/14 11:37, Ewan MacMahon wrote:
>>> -----Original Message-----
>>> From: Testbed Support for GridPP member institutes [mailto:TB-
>>> [log in to unmask]] On Behalf Of Matt RB
>>>
>>> Since the weekend though another problem cropped up that I found
>>> yesterday
>>> was the host certificate on our argus box had expired
>>>
>> That might be the problem then. I'd rather assume that glexec wouldn't
>> talk to an ARGUS server with a duff certificate.
>
> I dearly hope that happens, but our glexec issue has been very long
> running, pre-dating me starting this job, so I'm not expecting it to
> be resolved.
>
I guess the first thing to do is to decide if it's the server or the
client that is flaky (or both!) Let's kick off with this test. On some
UI, in your own account, run this command:
# voms-proxy-init --voms dteam
Then this:
# voms-proxy-info
That will show the file you made. Next, be on test worker node, as root.
Copy in the proxy with scp
from the location shown in voms-proxy-init to /tmp/x509up_u460 on the
WN. Change the ownership of proxy to a pilot account.
# chown pilatl01:atlas /tmp/x509up_u460
Fix the permissions.
# chmod 600 /tmp/x509up_u460
Switch to the pilot user.
# su - pilatl01
Run these commands to setup for the test.
# export GLEXEC_CLIENT_CERT=/tmp/x509up_u460
# export GLEXEC_SOURCE_PROXY=/tmp/x509up_u460
# export X509_USER_PROXY=/tmp/x509up_u460
Now do the test:
# /opt/glite/sbin/glexec /usr/bin/id
# (or in EMI etc., use /usr/sbin/glexec)
If all is well, you will see something like this:
uid=24683(dteam184) gid=2028(dteam) groups=2028(dteam)
Let me know what happens at your site.
Steve
--
Steve Jones [log in to unmask]
System Administrator office: 220
High Energy Physics Division tel (int): 42334
Oliver Lodge Laboratory tel (ext): +44 (0)151 794 2334
University of Liverpool http://www.liv.ac.uk/physics/hep/
|