All,
I've verified that the upstream patch, on top of the patch we've
provided, is both functional and does not exhibit the memory leak
problem; the test was to run the CC/NC against patched rampart/c for
approximately 18 hours, watching the memory footprint of the associated
apache2 processes.
Thierry-
Can you verify this package?
We need other fixes associated with this update here onsite at a
partner.
--
memory leak; rampart_context not freed (memory leaked per connection)
https://bugs.launchpad.net/bugs/460085
You received this bug notification because you are a member of Ubuntu
Dustin,
We can't verify this fix without the associated Rampart fix, which is pending
some tests on Dan/Eucalyptus side.
--
memory leak; rampart_context not freed (memory leaked per connection)
https://bugs.launchpad.net/bugs/460085
You received this bug notification because you are a member of
Accepted eucalyptus 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!
** Tags added: verification-needed
** Branch linked: lp:ubuntu/karmic-proposed/eucalyptus
--
memory leak; rampart_context not freed (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.
Dan/Thierry-
I just uploaded a package to karmic-proposed containing the eucalyptus
r946 fix.
Could one of you guys help draft the SRU testing notes and put that into
the bug description? Thanks.
** Changed in: eucalyptus (Ubuntu Karmic)
Status: Triaged = Fix Committed
--
memory leak;
Eucalyptus part of the fix now committed to lp:~ubuntu-core-
dev/eucalyptus/ubuntu-karmic
--
memory leak; rampart_context not freed (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
** Changed in: rampart (Ubuntu)
Status: Triaged = In Progress
** Changed in: rampart (Ubuntu)
Status: In Progress = Triaged
** Changed in: rampart (Ubuntu)
Assignee: Thierry Carrez (ttx) = Dustin Kirkland (kirkland)
** Changed in: rampart (Ubuntu)
Assignee: Dustin
** Branch linked: lp:~ubuntu-core-dev/eucalyptus/ubuntu
--
memory leak; rampart_context not freed (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.
This bug was fixed in the package eucalyptus - 1.6.1~bzr1083-0ubuntu1
---
eucalyptus (1.6.1~bzr1083-0ubuntu1) lucid; urgency=low
[ Dustin Kirkland ]
* Merge upstream bzr revision 1082; the following bugs have been fixed
upstream since the last merge:
- LP: #378969 -
** Branch linked: lp:ubuntu/eucalyptus
--
memory leak; rampart_context not freed (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.
--
@Dan:
Any news about how did your long term test go ?
Please also answer to question in comment 9, so that I know what you exactly
tested :)
--
memory leak; rampart_context not freed (memory leaked per connection)
https://bugs.launchpad.net/bugs/460085
You received this bug notification because
** Branch linked: lp:~ttx/eucalyptus/karmic-sru2
--
memory leak; rampart_context not freed (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.
--
** Changed in: eucalyptus (Ubuntu Karmic)
Milestone: None = karmic-updates
** Changed in: rampart (Ubuntu Karmic)
Milestone: None = karmic-updates
** Changed in: rampart (Ubuntu Karmic)
Assignee: (unassigned) = Thierry Carrez (ttx)
** Changed in: eucalyptus (Ubuntu)
Assignee:
Thierry, Shankar,
Thank you both for following up on this issue and finding a potential
patch to the memory leak issue in rampart; I'm testing the
rampartc-1.3.0 with the above patch now with a long term eucalyptus
test, and will report back when the test completes (we usually run for
.5 day to
Comments on the patch from Rampart upstream (shankar):
The patch is having several problems. First of all, if the
rampart_context is freed in in_handler, server side functionalities
will be broken. rampart_context is actually freed when msg_ctx is
freed. So no need to free it.
Uncommenting the
Rampart upstream is looking at the patch.
** Changed in: eucalyptus (Ubuntu)
Status: Invalid = Confirmed
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = Medium
** Changed in: eucalyptus (Ubuntu)
Importance: Medium = High
** Changed in: rampart (Ubuntu)
Status:
Not a bug in eucalyptus
** Changed in: eucalyptus (Ubuntu)
Status: New = Invalid
--
memory leak; rampart_context not freed (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
About other rampart configurations, we added rampart for eucalyptus so
if the patch is needed to work properly with the way eucalyptus uses
rampart, I'd say it takes precedence over other unknown ways that may
rely on the buggy behavior.
But knowing *why* this was commented out would certainly
Asked upstream, since they explicitly commented this out in a memory leak fix
revision:
http://svn.apache.org/viewvc?view=revisionrevision=709349
--
memory leak; rampart_context not freed (memory leaked per connection)
https://bugs.launchpad.net/bugs/460085
You received this bug notification
** Changed in: eucalyptus
Importance: Undecided = High
--
memory leak; rampart_context not freed (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
the patch required a small patch to eucalyptus that initializes axis2c
in the CC for each NC client connection (most already were handled this
way, except to StartNetwork/RunInstances).
in r946
--
memory leak; rampart_context not freed (memory leaked per connection)
** Attachment added: rampartc-1.3.0-euca.patch
http://launchpadlibrarian.net/34337608/rampartc-1.3.0-euca.patch
** Also affects: eucalyptus
Importance: Undecided
Status: New
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
--
memory leak;
23 matches
Mail list logo
