dev setup other than thread
> which
> >>> is cleaning up expired async-jobs.
> >>> >>
> >>> >> You can safely change CONSOLE appender's threshold to INFO in hyperv
> >>> plugin if you think that is causing the problem.
> >>&g
t;>> >>
>>> >> You can safely change CONSOLE appender's threshold to INFO in hyperv
>>> plugin if you think that is causing the problem.
>>> >> We will not lose much info which we want to show to user by this
>>> change. And in any
problem.
>> >> We will not lose much info which we want to show to user by this
>> change. And in any case it will be available in vmops.log.
>> >> CONSOLE appender's threshold is set to TRACE since the start of plugin.
>> >>
>> >> -Origin
nfo which we want to show to user by this
> change. And in any case it will be available in vmops.log.
> >> CONSOLE appender's threshold is set to TRACE since the start of plugin.
> >>
> >> -Original Message-----
> >> From: Mike Tutkowski [mailto:mike.
gt; -Original Message-
>> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>> Sent: Tuesday, December 30, 2014 11:10 PM
>> To: dev@cloudstack.apache.org
>> Subject: Re: CS MS Logging Level
>>
>> No, vmops.log does not seem to be getting spammed...jus
e the start of plugin.
>
> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Tuesday, December 30, 2014 11:10 PM
> To: dev@cloudstack.apache.org
> Subject: Re: CS MS Logging Level
>
> No, vmops.log does not seem to be getting spamm
apache.org
Subject: Re: CS MS Logging Level
No, vmops.log does not seem to be getting spammed...just the console.
On Tue, Dec 30, 2014 at 1:44 AM, Daan Hoogland
wrote:
> Mike,
>
> It doesn't spew to vmops.log anymore, right? It seems that the new
> jetty version interprets all the
No, vmops.log does not seem to be getting spammed...just the console.
On Tue, Dec 30, 2014 at 1:44 AM, Daan Hoogland
wrote:
> Mike,
>
> It doesn't spew to vmops.log anymore, right? It seems that the new
> jetty version interprets all the log4j/classpath differently and the
> one from the hyperv
Mike,
It doesn't spew to vmops.log anymore, right? It seems that the new
jetty version interprets all the log4j/classpath differently and the
one from the hyperv plugin takes precedence. I have been looking for a
solution but haven't found one yet.
On Mon, Dec 29, 2014 at 10:02 PM, Mike Tutkowski
Hi,
Does anyone know if the logging level or something like that changed on the
management server in 4.6?
It seems like it's spewing out tons of information to the console these
days.
Thanks!
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 3
10 matches
Mail list logo
