Comment 12 for bug 566793

Revision history for this message
Scott Moser (smoser) wrote :

I think i have to take back my "it worked" statement. the first 'get-console-output' worked fine.

The second has been running for 6 minutes, 30 seconds and has printed out the following:
-------------------------
         4 0 8
path=/services/Eucalyptus/?AWSAccessKeyId=WKy3rMzOWPouVOxK1p3Ar1C2uRBwa2FBXnCw&Action=GetConsoleOutput&InstanceId.1=i-431B08E0&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2010-05-28T14%3A56%3A43&Version=2009-11-30&Signature=oghj8LM8UBrtSz8NP47ZhX2uxDymt0swn1XC1sZ%2Bu0c%3D
Failure: 408 Request Timeout

Top shows eucalyptus-cloud eating all of 1 cpu.

cloud-output.log has things like this:
10:03:13 DEBUG ConsoleOutputCallback | ConsoleOutputCallback.java:110 org.jboss.netty.handler.timeout.ReadTimeoutException
10:03:13 DEBUG NioResponseHandler | NioResponseHandler.java:121 org.jboss.netty.handler.timeout.ReadTimeoutException