[ https://issues.apache.org/jira/browse/BROOKLYN-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14251319#comment-14251319 ]
Aled Sage commented on BROOKLYN-106: ------------------------------------ Thanks [~andrew.kennedy]. Note that the ssh connection to the VM is going through DNAT in the vcloud-director Edge Gateway. Our customer has also done some more testing and reports: "Just to make sure that vCHS connectivity is working, I have setup Brooklyn in vCHS and try to deploy same blueprints from there and its working fine without any issues. I seems its showing problem when we using subnet tier configuration with public NAT which hold the SSH client to complete existing task." I'll also test with the ``maxPacketSize`` set higher. > Tomcat install fails on CentOS: hangs installing java > ----------------------------------------------------- > > Key: BROOKLYN-106 > URL: https://issues.apache.org/jira/browse/BROOKLYN-106 > Project: Brooklyn > Issue Type: Bug > Affects Versions: 0.7.0-SNAPSHOT > Reporter: Aled Sage > Assignee: Aled Sage > Attachments: debug.log.tgz, jstack.txt, messages.tgz, ssh-stdout.txt > > > When deploying Tomcat to VMware's vcloud-air, to a CentOS 6.4 VM, when > installing Java it hangs! > The Brooklyn web-console shows that it is still waiting for a result from the > ssh command (which executed `sudo -E -n -S -- yum -y --nogpgcheck install > java-1.7.0-openjdk-devel`). > However, when logging into the VM I can see that the `yum` command has > finished, and the /var/log/messages (attached) shows that the install > completed. > This fails repeatedly. It used to pass! > The stdout is at 32040 bytes. The last few lines of the stdout (as shown in > the web-console) are: > {noformat} > Installing : libtasn1-2.3-6.el6_5.x86_64 > 50/56 > Installing : gnutls-2.8.5-14.el6_5.x86_64 > 51/56 > Installing : 1:cups-libs-1.4.2-67.el6.x86_64 > 52/56 > {noformat} > Could there be some buffer set to 32K, so it's stuck not reading the rest of > the stdout (but `SshjToolPerformanceTest.testConsecutiveBigStdoutCommands` > passes)? > Why else would our ssh command be stuck, not returning? -- This message was sent by Atlassian JIRA (v6.3.4#6332)