[Bug 460085] Re: Memory leaked per connection
** Changed in: eucalyptus Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in Ubuntu. https://bugs.launchpad.net/bugs/460085 Title: Memory leaked per connection To manage notifications about this bug go to: https://bugs.launchpad.net/eucalyptus/+bug/460085/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 460085] Re: Memory leaked per connection
This bug was fixed in the package rampart - 1.3.0-0ubuntu5.1 --- rampart (1.3.0-0ubuntu5.1) karmic-proposed; urgency=low * debian/patches/rampart-memleak.patch: Fix memory leak in rampart where for every connection receiver_cert is not freed (LP: #460085) -- Thierry CarrezMon, 14 Dec 2009 08:43:06 +0100 ** Changed in: rampart (Ubuntu Karmic) Status: Fix Committed => Fix Released -- Memory leaked per connection https://bugs.launchpad.net/bugs/460085 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 460085] Re: Memory leaked per connection
This bug was fixed in the package eucalyptus - 1.6~bzr931-0ubuntu7.4 --- eucalyptus (1.6~bzr931-0ubuntu7.4) karmic-proposed; urgency=low [ Thierry Carrez ] * cluster/handlers.c: Cherrypick upstream r946: initialize axis2c in the CC for each NC client connection, to avoid rampart memory leak (LP: #460085) * clc/modules/wsstack/src/main/java/com/eucalyptus/ws/handlers/HmacV2Handler.java: Cherrypick upstream r1079: Fix authentication issue when using a euca2ools that doesn't double base64encode userdata (LP: #461156) [ Dustin Kirkland ] * debian/eucalyptus-cc.upstart, debian/eucalyptus-common.eucalyptus.upstart: support CLEAN=1 on start/stop/restart of eucalyptus/euclayptus-cc; export the CLEAN env variable in eucalyptus.init, and handle it in both the pre-start and post-stop sections of eucalyptus-cc, (LP: #491254) -- Dustin KirklandWed, 02 Dec 2009 17:58:18 -0600 ** Changed in: eucalyptus (Ubuntu Karmic) Status: Fix Committed => Fix Released -- Memory leaked per connection https://bugs.launchpad.net/bugs/460085 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 460085] Re: Memory leaked per connection
** Tags added: verification-done ** Tags removed: verification-needed -- Memory leaked per connection https://bugs.launchpad.net/bugs/460085 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 460085] Re: Memory leaked per connection
All, I've been able to confirm that the newest euca/rampart packages, from proposed, are both functional and do not exhibit the memory leak. To be specific, i'm running with: eucalyptus-cc: 1.6~bzr931-0ubuntu7.4 librampart0: 1.3.0-0ubuntu5.1 Thanks! -Dan -- Memory leaked per connection https://bugs.launchpad.net/bugs/460085 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 460085] Re: Memory leaked per connection
** Branch linked: lp:ubuntu/karmic-proposed/rampart -- Memory leaked per connection https://bugs.launchpad.net/bugs/460085 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 460085] Re: Memory leaked per connection
Accepted rampart into karmic-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance! ** Changed in: rampart (Ubuntu Karmic) Status: In Progress => Fix Committed -- Memory leaked per connection https://bugs.launchpad.net/bugs/460085 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 460085] Re: Memory leaked per connection
** Branch linked: lp:ubuntu/rampart -- Memory leaked per connection https://bugs.launchpad.net/bugs/460085 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 460085] Re: Memory leaked per connection
This bug was fixed in the package rampart - 1.3.0-0ubuntu7 --- rampart (1.3.0-0ubuntu7) lucid; urgency=low * debian/patches/rampart-memleak.patch: Fix memory leak in rampart where for every connection receiver_cert is not freed (LP: #460085) -- Thierry CarrezMon, 14 Dec 2009 09:09:58 +0100 ** Changed in: rampart (Ubuntu) Status: In Progress => Fix Released -- Memory leaked per connection https://bugs.launchpad.net/bugs/460085 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 460085] Re: Memory leaked per connection
** Description changed: It looks like the rampart_context structure is not freed after processing (in rampart_in_handler.c), and in the rampart_context_free function, the section for freeing the receiver_cert is commented out (in rampart_token_processor.c). In our application (eucalyptus), this is causing the back-end components (axis2c/rampartc web services) to leak memory on every connection, which adds up quickly under load (30-50MB/day). I've attached a patch for review, but since the free section was commented out, it may be that there are other rampart configurations that will fail using this patch (this problem could certainly use some upstream guidance!) == SRU Report == Impact: A small amount of memory is not freed for every connection to an Eucalyptus web service. Under load, this can add up to 50Mb of RAM per day. Fix in development branch: This needs to be fixed in two places: Eucalyptus and Rampart. The Eucalyptus patch is applied to 1.6.1 in - Lucid. The Rampart fix will be shipped asap as 1.3.0-0ubuntu7, same - patch applied. + Lucid. The Rampart fix has been shipped as 1.3.0-0ubuntu7, same patch + applied. Minimal patches: Eucalyptus: http://bazaar.launchpad.net/~eucalyptus-maintainers/eucalyptus/1.6/revision/946 Rampart: debian/patches/rampart-memleak.patch (see comment 18 below) TEST CASE: Run a UEC CC/NC setup under load and watch the memory footprint of the associated apache2 processes. Without the patch, the memory used grows, with the patch it should remain stable. Regression potential: The patch affects memory management of Rampart structures and therefore has some potential for regression. However it was tested and accepted upstream (comment 7) and tested on real setups at Eucalyptus Systems. The only package in archive that uses rampart is eucalyptus. The regression tests are therefore quite limited. -- Memory leaked per connection https://bugs.launchpad.net/bugs/460085 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 460085] Re: Memory leaked per connection
Minimal patch for rampart ** Description changed: It looks like the rampart_context structure is not freed after processing (in rampart_in_handler.c), and in the rampart_context_free function, the section for freeing the receiver_cert is commented out (in rampart_token_processor.c). In our application (eucalyptus), this is causing the back-end components (axis2c/rampartc web services) to leak memory on every connection, which adds up quickly under load (30-50MB/day). I've attached a patch for review, but since the free section was commented out, it may be that there are other rampart configurations that will fail using this patch (this problem could certainly use some upstream guidance!) - -Dan + == SRU Report == + + Impact: A small amount of memory is not freed for every connection to an + Eucalyptus web service. Under load, this can add up to 50Mb of RAM per + day. + + Fix in development branch: This needs to be fixed in two places: + Eucalyptus and Rampart. The Eucalyptus patch is applied to 1.6.1 in + Lucid. The Rampart fix will be shipped asap as 1.3.0-0ubuntu7, same + patch applied. + + Minimal patches: + Eucalyptus: http://bazaar.launchpad.net/~eucalyptus-maintainers/eucalyptus/1.6/revision/946 + Rampart: debian/patches/rampart-memleak.patch (see attachment below) + + TEST CASE: + Run a UEC CC/NC setup under load and watch the memory footprint of the associated apache2 processes. Without the patch, the memory used grows, with the patch it should remain stable. + + Regression potential: The patch affects memory management of Rampart + structures and therefore has some potential for regression. However it + was tested and accepted upstream (comment 7) and tested on real setups + at Eucalyptus Systems. The only package in archive that uses rampart is + eucalyptus. The regression tests are therefore quite limited. ** Attachment added: "debian/patches/rampart-memleak.patch" http://launchpadlibrarian.net/36761797/rampart-memleak.patch ** Changed in: rampart (Ubuntu) Status: Triaged => In Progress ** Changed in: rampart (Ubuntu Karmic) Status: Triaged => In Progress ** Description changed: It looks like the rampart_context structure is not freed after processing (in rampart_in_handler.c), and in the rampart_context_free function, the section for freeing the receiver_cert is commented out (in rampart_token_processor.c). In our application (eucalyptus), this is causing the back-end components (axis2c/rampartc web services) to leak memory on every connection, which adds up quickly under load (30-50MB/day). I've attached a patch for review, but since the free section was commented out, it may be that there are other rampart configurations that will fail using this patch (this problem could certainly use some upstream guidance!) == SRU Report == Impact: A small amount of memory is not freed for every connection to an Eucalyptus web service. Under load, this can add up to 50Mb of RAM per day. Fix in development branch: This needs to be fixed in two places: Eucalyptus and Rampart. The Eucalyptus patch is applied to 1.6.1 in Lucid. The Rampart fix will be shipped asap as 1.3.0-0ubuntu7, same patch applied. Minimal patches: Eucalyptus: http://bazaar.launchpad.net/~eucalyptus-maintainers/eucalyptus/1.6/revision/946 - Rampart: debian/patches/rampart-memleak.patch (see attachment below) + Rampart: debian/patches/rampart-memleak.patch (see comment 18 below) TEST CASE: Run a UEC CC/NC setup under load and watch the memory footprint of the associated apache2 processes. Without the patch, the memory used grows, with the patch it should remain stable. Regression potential: The patch affects memory management of Rampart structures and therefore has some potential for regression. However it was tested and accepted upstream (comment 7) and tested on real setups at Eucalyptus Systems. The only package in archive that uses rampart is eucalyptus. The regression tests are therefore quite limited. -- Memory leaked per connection https://bugs.launchpad.net/bugs/460085 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 460085] Re: Memory leaked per connection
** Summary changed: - memory leak; rampart_context not freed (memory leaked per connection) + Memory leaked per connection -- Memory leaked per connection https://bugs.launchpad.net/bugs/460085 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
