Hi Imesh, I think jclouds uses this call to pass the customization script that we pass at instance start-up. We use that script since we cannot pass a payload like in other IaaSes.
Found following in code, which supports my guess, <CustomizationScript>#regenerate keys /bin/rm /etc/ssh/ssh_host_* /usr/sbin/dpkg-reconfigure openssh-server</CustomizationScript> IsuruP might confirm. Thanks. On Sat, Oct 4, 2014 at 10:55 PM, Imesh Gunaratne <im...@apache.org> wrote: > Hi Lahiru, > > I'm just curious, what's the purpose of using SSH here? > > Thanks > > On Fri, Oct 3, 2014 at 11:39 PM, Lahiru Sandaruwan <lahi...@wso2.com> > wrote: > >> Hi Vinod, >> >> It seems the cloud controller(jclouds) client has timed out due a failure >> of SSH call. >> Did the instance get created despite this error? >> >> Could you please check if these values(6.7.13.20:22) reachable from the >> machine which runs Stratos server? >> >> Thanks. >> >> On Fri, Oct 3, 2014 at 11:21 PM, Vinod Kamble <vinod.kam...@icloud.com> >> wrote: >> >>> On vcloud when the cartridge is launched getting following exception: >>> >>> TID: [0] [STRATOS] [2014-10-03 17:36:54,074] INFO {jclouds.ssh} - << >>> (root:pw[f31fe67651d63e8c4ba8704ef999ae1b]@6.7.13.20:22) error >>> acquiring {hostAndPort=6.7.13.20:22, loginUser=root, ssh=null, >>> connectTimeout=60000, sessionTimeout=60000} (attempt 3 of 5): Read timed >>> out {jclouds.ssh} >>> TID: [0] [STRATOS] [2014-10-03 17:36:55,876] WARN >>> {net.schmizz.sshj.DefaultConfig} - Disabling high-strength ciphers: cipher >>> strengths apparently limited by JCE policy {net.schmizz.sshj.DefaultConfig} >>> TID: [0] [STRATOS] [2014-10-03 17:36:55,877] INFO >>> {net.schmizz.sshj.transport.TransportImpl} - Client identity string: >>> SSH-2.0-SSHJ_0_8 {net.schmizz.sshj.transport.TransportImpl} >>> TID: [0] [STRATOS] [2014-10-03 17:37:36,412] INFO >>> {org.apache.axis2.transport.http.HTTPSender} - Unable to sendViaPost to >>> url[https://octl.qmog.cisco.com:9443/services/CloudControllerService] >>> {org.apache.axis2.transport.http.HTTPSender} >>> java.net.SocketTimeoutException: Read timed out >>> at java.net.SocketInputStream.socketRead0(Native Method) >>> at java.net.SocketInputStream.read(SocketInputStream.java:152) >>> at java.net.SocketInputStream.read(SocketInputStream.java:122) >>> at sun.security.ssl.InputRecord.readFully(InputRecord.java:442) >>> at sun.security.ssl.InputRecord.read(InputRecord.java:480) >>> at >>> sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:927) >>> at >>> sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:884) >>> at sun.security.ssl.AppInputStream.read(AppInputStream.java:102) >>> at java.io.BufferedInputStream.fill(BufferedInputStream.java:235) >>> at java.io.BufferedInputStream.read(BufferedInputStream.java:254) >>> at >>> org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:78) >>> at >>> org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:106) >>> >>> What could be the probable cause for this? >>> Any solution to fix it? >>> >>> The cartridge was pushed all the launch params. >>> >>> Thanks, >>> Vinod. >>> >> >> >> >> -- >> -- >> Lahiru Sandaruwan >> Committer and PMC member, Apache Stratos, >> Senior Software Engineer, >> WSO2 Inc., http://wso2.com >> lean.enterprise.middleware >> >> email: lahi...@wso2.com cell: (+94) 773 325 954 >> blog: http://lahiruwrites.blogspot.com/ >> twitter: http://twitter.com/lahirus >> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 >> >> > > > -- > Imesh Gunaratne > > Technical Lead, WSO2 > Committer & PMC Member, Apache Stratos > -- -- Lahiru Sandaruwan Committer and PMC member, Apache Stratos, Senior Software Engineer, WSO2 Inc., http://wso2.com lean.enterprise.middleware email: lahi...@wso2.com cell: (+94) 773 325 954 blog: http://lahiruwrites.blogspot.com/ twitter: http://twitter.com/lahirus linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146