cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-1267) KVM's cloudstack-agent service doesn't log (log4j)
Date Tue, 12 Mar 2013 13:37:13 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13600034#comment-13600034
] 

ASF subversion and git services commented on CLOUDSTACK-1267:
-------------------------------------------------------------

Commit d813a7ba98682c03342044c4ddde08bf23470a86 in branch refs/heads/4.1 from Chip Childers
<chip.childers@gmail.com>
[ https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;h=d813a7b ]

CLOUDSTACK-1267: Configure log4j in proper place so that it can be initialized correctly in
KVM and system VM environment

                
> KVM's cloudstack-agent service doesn't log (log4j)
> --------------------------------------------------
>
>                 Key: CLOUDSTACK-1267
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1267
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM
>    Affects Versions: 4.1.0
>         Environment: KVM centos 6.3
>            Reporter: Marcus Sorensen
>            Assignee: Kelven Yang
>            Priority: Blocker
>             Fix For: 4.1.0
>
>
> cloudstack-agent jsvc service doesn't log anymore. If I move /etc/cloudstack/agent/log4j-cloud.xml
to /etc/cloudstack/agent/log4j.xml it works.  Obviously, I have no logs to show, but if I
run jsvc manually in debug I see:
> log4j:WARN No appenders could be found for logger (org.apache.commons.httpclient.params.DefaultHttpParams).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message