This is a FAQ. The following google search should help: site:globus.org globus stop container nosec
Bottom line: Even an "insecure" container requires proper credential configuration. Tom On Tue, Jan 20, 2009 at 10:10 AM, Sergei Smolov <[email protected]> wrote: > Hello, List! > I've the problem with using "globus-stop-container". After starting Java WS > Core container with the command "./globus-start-container - nosec" I've > tried to execute the command "./globus-stop-container -s > http://127.0.0.2:8080/wsrf/services/ShutdownService -m 'conv'" but the > answer was: > > Error: ; nested exception is: > javax.xml.rpc.soap.SOAPFaultException: Defective credential detected [Caused > by: [JGLOBUS-5] Proxy file (/tmp/x509up_u1000) not found.] > > Is there a simple way, that is not connected to the security problems, to > use this command? > And, if not, how to get correct credential? > > Thanks in advance. > > -- > Sergey Smolov
