You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2008/04/20 17:18:22 UTC
[jira] Created: (HBASE-598) Loggging, no .log file; all goes into
.out
Loggging, no .log file; all goes into .out
------------------------------------------
Key: HBASE-598
URL: https://issues.apache.org/jira/browse/HBASE-598
Project: Hadoop HBase
Issue Type: Bug
Reporter: stack
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HBASE-598) Loggging, no .log file; all goes into
.out
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack resolved HBASE-598.
-------------------------
Resolution: Fixed
Fix Version/s: 0.2.0
Tested locally and on cluster. .log is back.
> Loggging, no .log file; all goes into .out
> ------------------------------------------
>
> Key: HBASE-598
> URL: https://issues.apache.org/jira/browse/HBASE-598
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: stack
> Fix For: 0.2.0
>
> Attachments: 598.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-598) Loggging, no .log file; all goes into
.out
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-598:
------------------------
Attachment: 598.patch
First thing on CLASSPATH should be hbase/conf. It wasn't. We were finding the log4j.properties that is in the hadoop core jar.
> Loggging, no .log file; all goes into .out
> ------------------------------------------
>
> Key: HBASE-598
> URL: https://issues.apache.org/jira/browse/HBASE-598
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: stack
> Attachments: 598.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.