[
https://issues.apache.org/jira/browse/WHIRR-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215034#comment-13215034
]
Andrei Savu commented on WHIRR-526:
-----------------------------------
Thanks Tom for reviewing. You can get a long list of ssh errors by trying to
start a zookeeper cluster on t1.micro using 0.7.1 due to some bugs in jclouds
(flooding the instance with too many script status requests).
> Don't log harmless sshj errors to console
> -----------------------------------------
>
> Key: WHIRR-526
> URL: https://issues.apache.org/jira/browse/WHIRR-526
> Project: Whirr
> Issue Type: Improvement
> Components: core
> Reporter: Tom White
> Assignee: Andrei Savu
> Fix For: 0.7.1, 0.8.0
>
> Attachments: log4j-cli.xml, log4j-cli.xml
>
>
> It's quite common to see sshj errors in the console during launch.
> {noformat}
> Dying because - net.schmizz.sshj.transport.TransportException: Broken
> transport; encountered EOF
> {noformat}
> They seem to be harmless since the service starts fine. Let's log them to
> whirr.log, but not to the console.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
