Mailing-List: contact cloudstack-issues-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Date: Mon, 11 Mar 2013 23:51:12 +0000 (UTC)
From: "Kelven Yang (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12632305.1360799221352.422177.1363045872686@arcas>
In-Reply-To: <JIRA.12632305.1360799221352@arcas>
References: <JIRA.12632305.1360799221352@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-1267) KVM's cloudstack-agent service
 doesn't log (log4j)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kelven Yang commented on CLOUDSTACK-1267:
-----------------------------------------

Marcus, can you check if your agent is updated. 
I checked in 4.1, it contains the same fix from master. I don't have a KVM environment to verify it
                
> 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