You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Andrei Savu (Updated) (JIRA)" <ji...@apache.org> on 2012/02/23 07:15:50 UTC
[jira] [Updated] (WHIRR-526) Don't log harmless sshj errors to
console
[ https://issues.apache.org/jira/browse/WHIRR-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Savu updated WHIRR-526:
------------------------------
Fix Version/s: 0.8.0
0.7.1
> 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
>
>
> 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