You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Tom White (Created) (JIRA)" <ji...@apache.org> on 2012/02/23 06:05:49 UTC
[jira] [Created] (WHIRR-526) Don't log harmless sshj errors to
console
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
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
[jira] [Commented] (WHIRR-526) Don't log harmless sshj errors to
console
Posted by "Andrei Savu (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214421#comment-13214421 ]
Andrei Savu commented on WHIRR-526:
-----------------------------------
What we need to do is redirect both jclouds.ssh & net.schmizz.sshj.transport.TransportImpl to the log file.
> 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
[jira] [Commented] (WHIRR-526) Don't log harmless sshj errors to
console
Posted by "Andrei Savu (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (WHIRR-526) Don't log harmless sshj errors to
console
Posted by "Andrei Savu (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Savu updated WHIRR-526:
------------------------------
Attachment: log4j-cli.xml
Update log4j settings for cli to display message on the console only for org.apache.whirr and everything else should go into the whirr.log file.
> 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
>
>
> 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
[jira] [Commented] (WHIRR-526) Don't log harmless sshj errors to
console
Posted by "Tom White (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215014#comment-13215014 ]
Tom White commented on WHIRR-526:
---------------------------------
+1 it looks good. I tried using it, but didn't get any ssh exceptions on that particular run. Have you seen the ssh exceptions go into the log file?
> 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
[jira] [Assigned] (WHIRR-526) Don't log harmless sshj errors to
console
Posted by "Andrei Savu (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Savu reassigned WHIRR-526:
---------------------------------
Assignee: Andrei Savu
> 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
>
> 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
[jira] [Commented] (WHIRR-526) Don't log harmless sshj errors to
console
Posted by "Andrei Savu (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214973#comment-13214973 ]
Andrei Savu commented on WHIRR-526:
-----------------------------------
Please review! The same file should work both with trunk and branch 0.7
> 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
[jira] [Updated] (WHIRR-526) Don't log harmless sshj errors to
console
Posted by "Andrei Savu (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Savu updated WHIRR-526:
------------------------------
Attachment: log4j-cli.xml
This one seems to be even better. All DEBUG messages from org.apache.whirr go to whirr.log as expected.
> 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
[jira] [Updated] (WHIRR-526) Don't log harmless sshj errors to
console
Posted by "Andrei Savu (Updated) (JIRA)" <ji...@apache.org>.
[ 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