Hello again,
I think that is a serious regression. If you manage to make it work
correctly, please do get in touch and we can prepare a stable update for
the memory leak.
I think I've done it, looking at the source of chef 11.12.8-2 (from
Jessie). I'm not a programmer and I know Ruby only a litt
On Mon, Jun 15, 2015 at 02:58:39PM +0200, Piotr Pańczyk wrote:
> Hello again,
> I did manage to apply those two commits manually:
> https://github.com/chef/chef/commit/d99e497874e7d08f017376717aa38a4c8d7fecd5
> https://github.com/chef/chef/commit/6c10604f1e8e9b557b69449b484df3aae47ee468
> omitting
Hello again,
I did manage to apply those two commits manually:
https://github.com/chef/chef/commit/d99e497874e7d08f017376717aa38a4c8d7fecd5
https://github.com/chef/chef/commit/6c10604f1e8e9b557b69449b484df3aae47ee468
omitting a few lines related to some intermediate versions.
Forking is working co
Hello Antonio,
I think the simple, ad ad-hoc solution can be changing the default logrotate
period from a week to a day, which would slightly reduce the amount of wasted
memory, as logrotate restarts the daemon.
The problem is quite serious for us, especially on servers running a lot of
virtua
Hello Piotr,
On Fri, Feb 13, 2015 at 03:56:38PM +0100, Piotr Pańczyk wrote:
> Hello Antonio,
>
> On 13.02.2015 14:29, Antonio Terceiro wrote:
> >Would you by any chance be able to identify the upstream commit that
> >introduced the fix? If so, I can try backporting that and releasing a
> >stable
Hello Antonio,
On 13.02.2015 14:29, Antonio Terceiro wrote:
Would you by any chance be able to identify the upstream commit that
introduced the fix? If so, I can try backporting that and releasing a
stable update.
I think this is it:
https://github.com/chef/chef/pull/291
--
Greetings,
Piotr Pa
Hello Piotr, thanks for reporting.
On Fri, Feb 13, 2015 at 12:37:19PM +0100, Piotr Panczyk wrote:
> Package: chef
> Version: 10.12.0-3
> Severity: important
>
> Dear Maintainer,
> Chef Client causes memory leak when run as a daemon. Just after start,
> the process uses about 30 MB of RAM. Then th
Package: chef
Version: 10.12.0-3
Severity: important
Dear Maintainer,
Chef Client causes memory leak when run as a daemon. Just after start,
the process uses about 30 MB of RAM. Then this amount rises with each
client run. After a week (before logrotate restarts the daemon), the
usage is at about
8 matches
Mail list logo