On Tue, 8 Mar 2005, Maarten Litmaath, CERN wrote:
> On Tue, 8 Mar 2005, Rod Walker wrote:
>
> > Hi,
> > Same problem as last time
> > $ myproxy-info -s myproxy.cern.ch -d
> > Failed reading length 0
> > Error authenticating: GSS Major Status: Some Other GSS failure
> > GSS Minor Status Error Chain:
> > (null)Error reading token
>
> It got itself into a deadlock. This is becoming quite a nuisance.
> I will consult the MyProxy mailing list and try and come up with
> a work-around for the time being. I have restarted the service.
Jim Basney, the author of MyProxy, recommends us to recompile MyProxy
on SL3 instead of taking the RH9 version from VDT; I will try that.
Meanwhile I have implemented a watchdog cron job on the myproxy server:
-----------------------------------------------------------------------------
* * * * * /root/chk-myproxy.sh >> /root/chk-myproxy.log 2>&1
-----------------------------------------------------------------------------
The chk-myproxy.sh script:
-----------------------------------------------------------------------------
#!/bin/sh
/opt/globus/bin/myproxy-info -s localhost &
pid=$!
sleep 15
kill -9 $pid || exit 0
/etc/init.d/myproxy stop # will not stop deadlocked process
pids=`ps xwww | awk '/[m]yproxy-server/ { print $1 }'`
kill -9 $pids
/etc/init.d/myproxy start
-----------------------------------------------------------------------------
|