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 (JIRA)" <ji...@apache.org> on 2011/08/15 04:50:27 UTC
[jira] [Created] (WHIRR-365) Too verbose command line interface
logging
Too verbose command line interface logging
------------------------------------------
Key: WHIRR-365
URL: https://issues.apache.org/jira/browse/WHIRR-365
Project: Whirr
Issue Type: Bug
Components: cli
Affects Versions: 0.6.0
Reporter: Andrei Savu
Priority: Blocker
Fix For: 0.6.0
When starting services using the command line interface I see a lot of messages like this:
{noformat}
Attaching `session` channel (#31)
Initialized - < session channel: id=31, recipient=1, localWin=[winSize=2097152], remoteWin=[winSize=0] >
Sending channel request for `pty-req`
Will request to exec `./jclouds-script-1313376230348 tailerr`
Sending channel request for `exec`
Received window adjustment for 2097152 bytes
Got chan request for `exit-status`
Got EOF
Got close
Sending EOF
Sending close
Forgetting `session` channel (#31)
{noformat}
I guess they are generated by sshj.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (WHIRR-365) Too verbose command line interface
logging
Posted by "Andrei Savu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Savu resolved WHIRR-365.
-------------------------------
Resolution: Fixed
Assignee: Andrei Savu
I've just committed this trivial change. I will now cut the branch and prepare the release artifacts.
> Too verbose command line interface logging
> ------------------------------------------
>
> Key: WHIRR-365
> URL: https://issues.apache.org/jira/browse/WHIRR-365
> Project: Whirr
> Issue Type: Bug
> Components: cli
> Affects Versions: 0.6.0
> Reporter: Andrei Savu
> Assignee: Andrei Savu
> Priority: Blocker
> Fix For: 0.6.0
>
> Attachments: WHIRR-365.patch
>
>
> When starting services using the command line interface I see a lot of messages like this:
> {noformat}
> Attaching `session` channel (#31)
> Initialized - < session channel: id=31, recipient=1, localWin=[winSize=2097152], remoteWin=[winSize=0] >
> Sending channel request for `pty-req`
> Will request to exec `./jclouds-script-1313376230348 tailerr`
> Sending channel request for `exec`
> Received window adjustment for 2097152 bytes
> Got chan request for `exit-status`
> Got EOF
> Got close
> Sending EOF
> Sending close
> Forgetting `session` channel (#31)
> {noformat}
> I guess they are generated by sshj.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (WHIRR-365) Too verbose command line interface
logging
Posted by "Andrei Savu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Savu updated WHIRR-365:
------------------------------
Attachment: WHIRR-365.patch
It seems like the previous google groups thread is outdated - there are no root level loggers in sshj. In this patch I've changed log4j.xml for the CLI so that only error log messages will be displayed on the console. I've also changed in ComputeCache the log level from a message from info to debug (created new ComputeServiceContext ...)
> Too verbose command line interface logging
> ------------------------------------------
>
> Key: WHIRR-365
> URL: https://issues.apache.org/jira/browse/WHIRR-365
> Project: Whirr
> Issue Type: Bug
> Components: cli
> Affects Versions: 0.6.0
> Reporter: Andrei Savu
> Priority: Blocker
> Fix For: 0.6.0
>
> Attachments: WHIRR-365.patch
>
>
> When starting services using the command line interface I see a lot of messages like this:
> {noformat}
> Attaching `session` channel (#31)
> Initialized - < session channel: id=31, recipient=1, localWin=[winSize=2097152], remoteWin=[winSize=0] >
> Sending channel request for `pty-req`
> Will request to exec `./jclouds-script-1313376230348 tailerr`
> Sending channel request for `exec`
> Received window adjustment for 2097152 bytes
> Got chan request for `exit-status`
> Got EOF
> Got close
> Sending EOF
> Sending close
> Forgetting `session` channel (#31)
> {noformat}
> I guess they are generated by sshj.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (WHIRR-365) Too verbose command line interface
logging
Posted by "Andrei Savu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Savu updated WHIRR-365:
------------------------------
Attachment: WHIRR-365-2.patch
Updated patch and I've done more testing. It looks like it's working as expected now. I've extracted the log4j.xml files outside src/ in a conf/ dir. Can someone check this? Thanks.
> Too verbose command line interface logging
> ------------------------------------------
>
> Key: WHIRR-365
> URL: https://issues.apache.org/jira/browse/WHIRR-365
> Project: Whirr
> Issue Type: Bug
> Components: cli
> Affects Versions: 0.6.0
> Reporter: Andrei Savu
> Assignee: Andrei Savu
> Priority: Blocker
> Fix For: 0.6.0
>
> Attachments: WHIRR-365-2.patch, WHIRR-365-2.patch, WHIRR-365.patch
>
>
> When starting services using the command line interface I see a lot of messages like this:
> {noformat}
> Attaching `session` channel (#31)
> Initialized - < session channel: id=31, recipient=1, localWin=[winSize=2097152], remoteWin=[winSize=0] >
> Sending channel request for `pty-req`
> Will request to exec `./jclouds-script-1313376230348 tailerr`
> Sending channel request for `exec`
> Received window adjustment for 2097152 bytes
> Got chan request for `exit-status`
> Got EOF
> Got close
> Sending EOF
> Sending close
> Forgetting `session` channel (#31)
> {noformat}
> I guess they are generated by sshj.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WHIRR-365) Too verbose command line interface
logging
Posted by "Andrei Savu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088141#comment-13088141 ]
Andrei Savu commented on WHIRR-365:
-----------------------------------
It looks like we have many log4j.xml files in the project:
{noformat}
./cli/src/main/resources/log4j.xml
./core/src/test/resources/log4j.xml
./core/log4j.xml
./services/cdh/src/test/resources/log4j.xml
./services/hbase/src/test/resources/log4j.xml
./services/voldemort/src/test/resources/log4j.xml
./services/hadoop/src/test/resources/log4j.xml
./services/cassandra/src/test/resources/log4j.xml
./services/zookeeper/src/test/resources/log4j.xml
./examples/src/main/resources/log4j.xml
{noformat}
I guess that outside the testing code we should probably have only one in cli? I will do some checking.
> Too verbose command line interface logging
> ------------------------------------------
>
> Key: WHIRR-365
> URL: https://issues.apache.org/jira/browse/WHIRR-365
> Project: Whirr
> Issue Type: Bug
> Components: cli
> Affects Versions: 0.6.0
> Reporter: Andrei Savu
> Assignee: Andrei Savu
> Priority: Blocker
> Fix For: 0.6.0
>
> Attachments: WHIRR-365.patch
>
>
> When starting services using the command line interface I see a lot of messages like this:
> {noformat}
> Attaching `session` channel (#31)
> Initialized - < session channel: id=31, recipient=1, localWin=[winSize=2097152], remoteWin=[winSize=0] >
> Sending channel request for `pty-req`
> Will request to exec `./jclouds-script-1313376230348 tailerr`
> Sending channel request for `exec`
> Received window adjustment for 2097152 bytes
> Got chan request for `exit-status`
> Got EOF
> Got close
> Sending EOF
> Sending close
> Forgetting `session` channel (#31)
> {noformat}
> I guess they are generated by sshj.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WHIRR-365) Too verbose command line interface
logging
Posted by "Andrei Savu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086789#comment-13086789 ]
Andrei Savu commented on WHIRR-365:
-----------------------------------
I've found a page explaining the problem: http://bit.ly/n0VMdd (Google Cache). It seems like some loggers used by SSHJ are root level loggers. I would look into how to change the logging settings to filter all these messages.
> Too verbose command line interface logging
> ------------------------------------------
>
> Key: WHIRR-365
> URL: https://issues.apache.org/jira/browse/WHIRR-365
> Project: Whirr
> Issue Type: Bug
> Components: cli
> Affects Versions: 0.6.0
> Reporter: Andrei Savu
> Priority: Blocker
> Fix For: 0.6.0
>
>
> When starting services using the command line interface I see a lot of messages like this:
> {noformat}
> Attaching `session` channel (#31)
> Initialized - < session channel: id=31, recipient=1, localWin=[winSize=2097152], remoteWin=[winSize=0] >
> Sending channel request for `pty-req`
> Will request to exec `./jclouds-script-1313376230348 tailerr`
> Sending channel request for `exec`
> Received window adjustment for 2097152 bytes
> Got chan request for `exit-status`
> Got EOF
> Got close
> Sending EOF
> Sending close
> Forgetting `session` channel (#31)
> {noformat}
> I guess they are generated by sshj.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (WHIRR-365) Too verbose command line interface
logging
Posted by "Andrei Savu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Savu reopened WHIRR-365:
-------------------------------
I'm reopening this because it seems like the patch only works for the development build but I still see a long list of log messages on the binary release.
My guess is this is a classpath ordering issue generated by the fact that we have many log4j.xml files in the project. Should I update them all or are am I doing something wrong?
> Too verbose command line interface logging
> ------------------------------------------
>
> Key: WHIRR-365
> URL: https://issues.apache.org/jira/browse/WHIRR-365
> Project: Whirr
> Issue Type: Bug
> Components: cli
> Affects Versions: 0.6.0
> Reporter: Andrei Savu
> Assignee: Andrei Savu
> Priority: Blocker
> Fix For: 0.6.0
>
> Attachments: WHIRR-365.patch
>
>
> When starting services using the command line interface I see a lot of messages like this:
> {noformat}
> Attaching `session` channel (#31)
> Initialized - < session channel: id=31, recipient=1, localWin=[winSize=2097152], remoteWin=[winSize=0] >
> Sending channel request for `pty-req`
> Will request to exec `./jclouds-script-1313376230348 tailerr`
> Sending channel request for `exec`
> Received window adjustment for 2097152 bytes
> Got chan request for `exit-status`
> Got EOF
> Got close
> Sending EOF
> Sending close
> Forgetting `session` channel (#31)
> {noformat}
> I guess they are generated by sshj.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (WHIRR-365) Too verbose command line interface
logging
Posted by "Andrei Savu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Savu resolved WHIRR-365.
-------------------------------
Resolution: Fixed
I've committed the latest patch to trunk and 0.6.0 branch. I will prepare the artifacts for the RC tonight. Hopefully everything should be ok for a release.
> Too verbose command line interface logging
> ------------------------------------------
>
> Key: WHIRR-365
> URL: https://issues.apache.org/jira/browse/WHIRR-365
> Project: Whirr
> Issue Type: Bug
> Components: cli
> Affects Versions: 0.6.0
> Reporter: Andrei Savu
> Assignee: Andrei Savu
> Priority: Blocker
> Fix For: 0.6.0
>
> Attachments: WHIRR-365-2.patch, WHIRR-365-2.patch, WHIRR-365.patch
>
>
> When starting services using the command line interface I see a lot of messages like this:
> {noformat}
> Attaching `session` channel (#31)
> Initialized - < session channel: id=31, recipient=1, localWin=[winSize=2097152], remoteWin=[winSize=0] >
> Sending channel request for `pty-req`
> Will request to exec `./jclouds-script-1313376230348 tailerr`
> Sending channel request for `exec`
> Received window adjustment for 2097152 bytes
> Got chan request for `exit-status`
> Got EOF
> Got close
> Sending EOF
> Sending close
> Forgetting `session` channel (#31)
> {noformat}
> I guess they are generated by sshj.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WHIRR-365) Too verbose command line interface
logging
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088525#comment-13088525 ]
Tom White commented on WHIRR-365:
---------------------------------
+1 Looks good.
> Too verbose command line interface logging
> ------------------------------------------
>
> Key: WHIRR-365
> URL: https://issues.apache.org/jira/browse/WHIRR-365
> Project: Whirr
> Issue Type: Bug
> Components: cli
> Affects Versions: 0.6.0
> Reporter: Andrei Savu
> Assignee: Andrei Savu
> Priority: Blocker
> Fix For: 0.6.0
>
> Attachments: WHIRR-365-2.patch, WHIRR-365-2.patch, WHIRR-365.patch
>
>
> When starting services using the command line interface I see a lot of messages like this:
> {noformat}
> Attaching `session` channel (#31)
> Initialized - < session channel: id=31, recipient=1, localWin=[winSize=2097152], remoteWin=[winSize=0] >
> Sending channel request for `pty-req`
> Will request to exec `./jclouds-script-1313376230348 tailerr`
> Sending channel request for `exec`
> Received window adjustment for 2097152 bytes
> Got chan request for `exit-status`
> Got EOF
> Got close
> Sending EOF
> Sending close
> Forgetting `session` channel (#31)
> {noformat}
> I guess they are generated by sshj.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WHIRR-365) Too verbose command line interface
logging
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086814#comment-13086814 ]
Tom White commented on WHIRR-365:
---------------------------------
bq. I will now cut the branch and prepare the release artifacts.
Great! Note that the "incubating" tag is no longer needed in the release version.
> Too verbose command line interface logging
> ------------------------------------------
>
> Key: WHIRR-365
> URL: https://issues.apache.org/jira/browse/WHIRR-365
> Project: Whirr
> Issue Type: Bug
> Components: cli
> Affects Versions: 0.6.0
> Reporter: Andrei Savu
> Assignee: Andrei Savu
> Priority: Blocker
> Fix For: 0.6.0
>
> Attachments: WHIRR-365.patch
>
>
> When starting services using the command line interface I see a lot of messages like this:
> {noformat}
> Attaching `session` channel (#31)
> Initialized - < session channel: id=31, recipient=1, localWin=[winSize=2097152], remoteWin=[winSize=0] >
> Sending channel request for `pty-req`
> Will request to exec `./jclouds-script-1313376230348 tailerr`
> Sending channel request for `exec`
> Received window adjustment for 2097152 bytes
> Got chan request for `exit-status`
> Got EOF
> Got close
> Sending EOF
> Sending close
> Forgetting `session` channel (#31)
> {noformat}
> I guess they are generated by sshj.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (WHIRR-365) Too verbose command line interface
logging
Posted by "Andrei Savu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Savu updated WHIRR-365:
------------------------------
Attachment: WHIRR-365-2.patch
In this patch I've removed core/log4j.xml and added a filter for sshj messages to the log4j file in examples.
It looks like the release binary build has the desired behavior now and the same is true when building from the source release.
Was core/log4j.xml actually used? (I don't think so)
> Too verbose command line interface logging
> ------------------------------------------
>
> Key: WHIRR-365
> URL: https://issues.apache.org/jira/browse/WHIRR-365
> Project: Whirr
> Issue Type: Bug
> Components: cli
> Affects Versions: 0.6.0
> Reporter: Andrei Savu
> Assignee: Andrei Savu
> Priority: Blocker
> Fix For: 0.6.0
>
> Attachments: WHIRR-365-2.patch, WHIRR-365.patch
>
>
> When starting services using the command line interface I see a lot of messages like this:
> {noformat}
> Attaching `session` channel (#31)
> Initialized - < session channel: id=31, recipient=1, localWin=[winSize=2097152], remoteWin=[winSize=0] >
> Sending channel request for `pty-req`
> Will request to exec `./jclouds-script-1313376230348 tailerr`
> Sending channel request for `exec`
> Received window adjustment for 2097152 bytes
> Got chan request for `exit-status`
> Got EOF
> Got close
> Sending EOF
> Sending close
> Forgetting `session` channel (#31)
> {noformat}
> I guess they are generated by sshj.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira