grisu / gricli

Grisu commandline client
7 stars 2 forks source link

Minor Non-reproducible bugs on RC with default backend #131

Closed sina-masoud-ansari closed 13 years ago

sina-masoud-ansari commented 13 years ago

This is really just an 'FYI' as I can't reproduce the issues:

Just tried submitting a job, first time using the new release on the default backend

Logged in to backend: BeSTGRID gricli> set group /nz/nesi gricli> set application UnixCommands gricli> submit "sleep 100" job name is gricli command failed. Either connection to server failed, or this is gricli bug. Please send /home/smas036/.grisu.be ta/gricli.debug to eresearch-admin@auckland.ac.nz together with description of what triggered the problem gricli> set debug true gricli> submit "sleep 100" job name is gricli gricli>

Not sure why that may have happened, here is the debug file:

0 [main] DEBUG grisu.frontend.control.login.LoginManager - BouncyCastle library not loaded.... 2 [main] DEBUG grisu.frontend.control.login.LoginManager - Loading bouncy castle... 1649 [main] DEBUG grisu.frontend.control.login.LoginHelpers - gssCredential login... 1656 [main] DEBUG grisu.settings.MyProxyServerParams - Problem with config file: null 1704 [main] DEBUG grisu.frontend.control.login.LoginHelpers - Using myProxyServer: 202.158.218.205 / 7512 1714 [main] DEBUG grisu.jcommons.utils.HttpProxyManager - Using default myproxy... 1714 [main] DEBUG grisu.jcommons.utils.HttpProxyManager - Creating default MyProxy object: myproxy.arcs.org.au / 7512 2138 [main] DEBUG grisu.jcommons.utils.HttpProxyManager - actual host: 202.158.218.205 2565 [main] DEBUG grisu.frontend.control.login.ServiceInterfaceFactory - LocalServiceInterfaceCreator doesn't handle url: https://compute.services.bestgrid.org/soap/GrisuServ$ 3789 [main] INFO grisu.frontend.control.login.ServiceInterfaceFactory - Successfully created serviceInterface using creator: JaxWsServiceInterfaceCreator 4326 [main] INFO grisu.frontend.control.login.ServiceInterfaceFactory - Successfully logged in.

I tried to reproduce by destroying proxy and clearing cache but then I got this:

Logged in to backend: BeSTGRID gricli> Exception in thread "Thread-5" com.sun.xml.ws.client.ClientTransportException: The server sent HTTP status code 413: Request Entity Too Large at com.sun.xml.ws.transport.http.client.HttpTransportPipe.checkStatusCode(HttpTransportPipe.java:203) at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:179) at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:94) at com.sun.xml.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:89) at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:598) at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:557) at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:542) at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:439) at com.sun.xml.ws.client.Stub.process(Stub.java:222) at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:135) at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:109) at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89) at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118) at $Proxy48.getFqans(Unknown Source) at grisu.model.UserEnvironmentManagerImpl.getAllAvailableFqans(UserEnvironmentManagerImpl.java:156) at grisu.model.UserEnvironmentManagerImpl.getAllAvailableFqans(UserEnvironmentManagerImpl.java:147) at grisu.model.UserEnvironmentManagerImpl.getAllAvailableSubmissionLocations(UserEnvironmentManagerImpl.java:223) at grisu.gricli.completors.CompletionCacheImpl.getAllQueues(CompletionCacheImpl.java:96) at grisu.gricli.completors.CompletionCacheImpl$1.run(CompletionCacheImpl.java:37)

gricli>

I repeated the the destroy proxy, clear cache and logged in again but it got stuck after choosing my login method:

Login method: 1 Loading / (keeps spinning)

I killed it and started griclish again, everything was fine and submission was fine. Debug file didn't show anything different from above. I can't seem to reproduce any of this

sina-masoud-ansari commented 13 years ago

129

yuriyh commented 13 years ago

413 error is fixed now.