On Wed, Aug 31, 2016 at 9:06 PM, Nir Soffer wrote:
> On Wed, Aug 31, 2016 at 8:06 PM, Federico Alberto Sayd
> wrote:
>
>> Hello Nir:
>>
>>
>> I followed your instructions , added the config file, restarted vdsm, and
>> today I have the vdsm logs from a host:
>>
>> https://drive.google.com/file/d
On Wed, Aug 31, 2016 at 8:06 PM, Federico Alberto Sayd
wrote:
> Hello Nir:
>
>
> I followed your instructions , added the config file, restarted vdsm, and
> today I have the vdsm logs from a host:
>
> https://drive.google.com/file/d/0ByrwZ1AkYuyeR1hmRm90a1R6MEk/
> view?usp=sharing
>
> Please tell
Hello Nir:
I followed your instructions , added the config file, restarted vdsm,
and today I have the vdsm logs from a host:
https://drive.google.com/file/d/0ByrwZ1AkYuyeR1hmRm90a1R6MEk/view?usp=sharing
Please tell me if you see anything related to the memory issue.
Thanks
Federico
El 3
On Tue, Aug 30, 2016 at 1:30 AM, Federico Alberto Sayd
wrote:
> I have issues with my ovirt setup related to memory consumption. After
> upgrading to 4.0 I noted a considerable grow in vdsm memory consumption.
> I suspect that the grow is related to a memory leak.
>
We need more details, see bel
Finally got a chance to implement this, so testing this on my centos7 hosts,
and it looks good. I’ll keep eye on it for a couple days, but after a couple of
hours, there’s no evidence of any leakage.
> On Mar 30, 2015, at 4:14 PM, John Taylor wrote:
>
> Dan Kenigsberg writes:
>
>> On Sat, M
Dan Kenigsberg writes:
> On Sat, Mar 28, 2015 at 10:20:25AM -0400, John Taylor wrote:
>> Daniel Helgenberger writes:
>>
>> > Hello Everyone,
>> >
>> > I did create the original BZ on this. In the mean time, lab system I
>> > used is dismantled and the production system is yet to deploy.
>> >
>>
Just to precise that I'm also concerned whatever is the host (el7 or
el6) and I have many vms running on a single host (up to 15) and many
networks ( up to 10)
It is always the same : when vdsmd finished to take the totality of
memory, the host becomes unreacheable and vms begin to migrate. The
On 26/03/15 18:12, Darrell Budic wrote:
Yes, this script leaks quickly. Started out at a RSS of 21000ish, already at
26744 a minute in, about 5 minutes later it’s at 39384 and climbing.
Been abusing a production server for those simple tests, but didn’t want to run
valgrind against it right th
On Sat, Mar 28, 2015 at 10:20:25AM -0400, John Taylor wrote:
> Daniel Helgenberger writes:
>
> > Hello Everyone,
> >
> > I did create the original BZ on this. In the mean time, lab system I
> > used is dismantled and the production system is yet to deploy.
> >
> > As I wrote in BZ1147148 [1], I e
Daniel Helgenberger writes:
> Hello Everyone,
>
> I did create the original BZ on this. In the mean time, lab system I
> used is dismantled and the production system is yet to deploy.
>
> As I wrote in BZ1147148 [1], I experienced two different issues. One,
> one big mem leak of about 15MiB/h and
> On Mar 26, 2015, at 6:42 AM, Dan Kenigsberg wrote:
>
> On Wed, Mar 25, 2015 at 01:29:25PM -0500, Darrell Budic wrote:
>>
>>> On Mar 25, 2015, at 5:34 AM, Dan Kenigsberg wrote:
>>>
>>> On Tue, Mar 24, 2015 at 02:01:40PM -0500, Darrell Budic wrote:
> On Mar 24, 2015, at 4:33 AM, Dan
On 26/03/15 09:43, Matt . wrote:
Hi Daniel,
Great! Thanks.
I only see this issue happening on CentOS 7, Joop van de Wege also
confirmed he didn't see it on CentOS 6.
Cheers,
Matt
I have experienced the same issue on Centos 6.6 and Centos 7 both
managed by the same engine.
Cheers
Federico
Hi Daniel,
Great! Thanks.
I only see this issue happening on CentOS 7, Joop van de Wege also
confirmed he didn't see it on CentOS 6.
Cheers,
Matt
2015-03-26 13:33 GMT+01:00 Daniel Helgenberger :
> Hello Everyone,
>
> I did create the original BZ on this. In the mean time, lab system I
> used i
Hello Everyone,
I did create the original BZ on this. In the mean time, lab system I
used is dismantled and the production system is yet to deploy.
As I wrote in BZ1147148 [1], I experienced two different issues. One,
one big mem leak of about 15MiB/h and a smaller one, ~300KiB. These seem
unrela
On Wed, Mar 25, 2015 at 01:29:25PM -0500, Darrell Budic wrote:
>
> > On Mar 25, 2015, at 5:34 AM, Dan Kenigsberg wrote:
> >
> > On Tue, Mar 24, 2015 at 02:01:40PM -0500, Darrell Budic wrote:
> >>
> >>> On Mar 24, 2015, at 4:33 AM, Dan Kenigsberg wrote:
> >>>
> >>> On Mon, Mar 23, 2015 at 04:0
> On Mar 25, 2015, at 5:34 AM, Dan Kenigsberg wrote:
>
> On Tue, Mar 24, 2015 at 02:01:40PM -0500, Darrell Budic wrote:
>>
>>> On Mar 24, 2015, at 4:33 AM, Dan Kenigsberg wrote:
>>>
>>> On Mon, Mar 23, 2015 at 04:00:14PM -0400, John Taylor wrote:
Chris Adams writes:
> Once upo
On Tue, Mar 24, 2015 at 02:01:40PM -0500, Darrell Budic wrote:
>
> > On Mar 24, 2015, at 4:33 AM, Dan Kenigsberg wrote:
> >
> > On Mon, Mar 23, 2015 at 04:00:14PM -0400, John Taylor wrote:
> >> Chris Adams writes:
> >>
> >>> Once upon a time, Sven Kieske said:
> On 13/03/15 12:29, Kapeta
> On Mar 24, 2015, at 4:33 AM, Dan Kenigsberg wrote:
>
> On Mon, Mar 23, 2015 at 04:00:14PM -0400, John Taylor wrote:
>> Chris Adams writes:
>>
>>> Once upon a time, Sven Kieske said:
On 13/03/15 12:29, Kapetanakis Giannis wrote:
> We also face this problem since 3.5 in two different
On Mon, Mar 23, 2015 at 04:00:14PM -0400, John Taylor wrote:
> Chris Adams writes:
>
> > Once upon a time, Sven Kieske said:
> >> On 13/03/15 12:29, Kapetanakis Giannis wrote:
> >> > We also face this problem since 3.5 in two different installations...
> >> > Hope it's fixed soon
> >>
> >> Noth
Chris Adams writes:
> Once upon a time, Sven Kieske said:
>> On 13/03/15 12:29, Kapetanakis Giannis wrote:
>> > We also face this problem since 3.5 in two different installations...
>> > Hope it's fixed soon
>>
>> Nothing will get fixed if no one bothers to
>> open BZs and send relevants log fi
Once upon a time, Sven Kieske said:
> On 13/03/15 12:29, Kapetanakis Giannis wrote:
> > We also face this problem since 3.5 in two different installations...
> > Hope it's fixed soon
>
> Nothing will get fixed if no one bothers to
> open BZs and send relevants log files to help
> track down the p
On 13/03/15 12:29, Kapetanakis Giannis wrote:
> We also face this problem since 3.5 in two different installations...
> Hope it's fixed soon
Nothing will get fixed if no one bothers to
open BZs and send relevants log files to help
track down the problems.
--
Mit freundlichen Grüßen / Regards
On 06/03/15 18:12, Federico Alberto Sayd wrote:
Hello:
I am experiencing troubles with VDSM memory consuption.
I am running
Engine: ovirt 3.5.1
Nodes:
Centos 6.6
VDSM 4.16.10-8
Libvirt: libvirt-0.10.2-46
Kernel: 2.6.32
When the host boots, memory consuption is normal, but after 2 or 3
days
NO!
The fix that should have fixed it didn't change a thing... we lost
track there as some devs were going to look at it.
2015-03-10 11:47 GMT+01:00 Dan Kenigsberg :
> On Mon, Mar 09, 2015 at 11:49:01PM +0100, Matt . wrote:
>> Hi,
>>
>> I also see this on the latest 3.5 version, I'm thinking abou
On 03/10/2015 12:19 AM, Dan Kenigsberg wrote:
On Mon, Mar 09, 2015 at 12:17:00PM -0500, Chris Adams wrote:
Once upon a time, Dan Kenigsberg said:
I'm afraid that we are yet to find a solution for this issue, which is
completly different from the horrible leak of supervdsm < 4.16.7.
Could you
On Mon, Mar 09, 2015 at 11:49:01PM +0100, Matt . wrote:
> Hi,
>
> I also see this on the latest 3.5 version, I'm thinking about setting
> up a cronjob to restart vdsm every night.
>
> I cannot believe that people say they don't have this issue.
>
> Can someone of the devs dive in maybe ?
> >> 1
Hi,
I also see this on the latest 3.5 version, I'm thinking about setting
up a cronjob to restart vdsm every night.
I cannot believe that people say they don't have this issue.
Can someone of the devs dive in maybe ?
Thanks!
Matt
2015-03-09 23:29 GMT+01:00 Dan Kenigsberg :
> On Mon, Mar 09,
Oh Sorry Dan, you are one of them ;)
Nice to have you on this :)
2015-03-09 23:49 GMT+01:00 Matt . :
> Hi,
>
> I also see this on the latest 3.5 version, I'm thinking about setting
> up a cronjob to restart vdsm every night.
>
> I cannot believe that people say they don't have this issue.
>
> Can
On Mon, Mar 09, 2015 at 12:17:00PM -0500, Chris Adams wrote:
> Once upon a time, Dan Kenigsberg said:
> > I'm afraid that we are yet to find a solution for this issue, which is
> > completly different from the horrible leak of supervdsm < 4.16.7.
> >
> > Could you corroborate the claim of
> >
On Mon, Mar 09, 2015 at 10:40:51AM -0500, Darrell Budic wrote:
> > On Mar 9, 2015, at 4:51 AM, Dan Kenigsberg wrote:
> >
> > On Fri, Mar 06, 2015 at 10:58:53AM -0600, Darrell Budic wrote:
> >> I believe the supervdsm leak was fixed, but 3.5.1 versions of vdsmd still
> >> leaks slowly, ~300k/hr,
Once upon a time, Dan Kenigsberg said:
> I'm afraid that we are yet to find a solution for this issue, which is
> completly different from the horrible leak of supervdsm < 4.16.7.
>
> Could you corroborate the claim of
> Bug 1147148 - M2Crypto usage in vdsm leaks memory
> ? Does the leak disa
> On Mar 9, 2015, at 4:51 AM, Dan Kenigsberg wrote:
>
> On Fri, Mar 06, 2015 at 10:58:53AM -0600, Darrell Budic wrote:
>> I believe the supervdsm leak was fixed, but 3.5.1 versions of vdsmd still
>> leaks slowly, ~300k/hr, yes.
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1158108
>>
>>
>
On Fri, Mar 06, 2015 at 10:58:53AM -0600, Darrell Budic wrote:
> I believe the supervdsm leak was fixed, but 3.5.1 versions of vdsmd still
> leaks slowly, ~300k/hr, yes.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1158108
>
>
> > On Mar 6, 2015, at 10:23 AM, Chris Adams wrote:
> >
> > Onc
I believe the supervdsm leak was fixed, but 3.5.1 versions of vdsmd still leaks
slowly, ~300k/hr, yes.
https://bugzilla.redhat.com/show_bug.cgi?id=1158108
> On Mar 6, 2015, at 10:23 AM, Chris Adams wrote:
>
> Once upon a time, Federico Alberto Sayd said:
>> I am experiencing troubles with VD
Once upon a time, Federico Alberto Sayd said:
> I am experiencing troubles with VDSM memory consuption.
>
> I am running
>
> Engine: ovirt 3.5.1
>
> Nodes:
>
> Centos 6.6
> VDSM 4.16.10-8
> Libvirt: libvirt-0.10.2-46
> Kernel: 2.6.32
>
> When the host boots, memory consuption is normal, but a
35 matches
Mail list logo
