** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655153
Title:
long-running stunnel leaks memory
To manage notifications about this bug go to:
https://bugs.launch
Great, Thank you Brian!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655153
Title:
long-running stunnel leaks memory
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubunt
This bug was fixed in the package stunnel4 - 3:5.30-1ubuntu0.1
---
stunnel4 (3:5.30-1ubuntu0.1) xenial; urgency=medium
* Backport fix for TLS session leak introduced in stunnel4 5.27 from
stunnel4 5.33: "Fixed a memory leak in the TLS session caching code
(thx to Richard Kra
While it isn't ideal for the author / fixer to verify the fix it is
better than nothing.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
It certainly fixes the bug for me - stunnel4 process was up until the
server was rebooted (several months) versus crashing after a day or two.
However, as the author of the patch I'm not sure that I should be the
one to verify it...
--
You received this bug notification because you are a member
The server we were observing the problem on was upgraded to Yakkety,
which is running stunnel4 5.35, so I can no longer test this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655153
Title:
long-r
Hello Bruce, or anyone else affected,
Accepted stunnel4 into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/stunnel4/3:5.30-1ubuntu0.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
Thank you very much Simon, I do appreciate your time and help in getting
my patch correct.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655153
Title:
long-running stunnel leaks memory
To manage n
Hey Scott! There's a couple of things that are not correct with your patch:
1. "Fixes launchpad bug 1655153." - this is not enough to automatically close
the bug report, it should be like this, preferably at the end of the changelog
entry: "(LP: #1655153)".
2. Ubuntu is different than Debian in
** Description changed:
We are running a long-running stunnel4 daemon to proxy TLS connections
to another set of servers. After leaving it running for a few weeks, its
memory usage had grown to 1.5GB. Restarting it reduced its memory usage
to expected levels (VSZ and RSS) but while I've be
Attached is an updated debdiff. I have attempted to fill out the header
per recommendations (somewhat tricky for stunnel4, as there is no bug
tracking system and granularity of commits is by release - official
source repository is an rsync of tarballs, but the maintainer does have
a github mirror w
Thanks Simon, I didn't expect my current patch to be the final one -
just a demonstration of the fix. I am more than happy to contribute a
compliant patch, if this one-off fix for Xenial is the best way to go.
Unfortunately, upstream debian closed the bug without fixing jessie-
backports and the ma
Hello Scott! Apologies for the delay on a review.
In the changelog, please change unstable (a Debian codename) to xenial
(the Ubuntu codename you are targeting it to) and change the version
from 3:5.30-1.1 to an Ubuntu version (I think 3:5.30-1ubuntu0.1 would be
best).
Also, please add a DEP-3 pa
@Bryan: Done.
** Also affects: stunnel4 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: stunnel4 (Ubuntu Xenial)
Status: New => Fix Released
** Changed in: stunnel4 (Ubuntu Xenial)
Status: Fix Released => Confirmed
** Changed in: stunnel4 (Ubuntu)
(oops, leaving the Xenial task open of course)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655153
Title:
long-running stunnel leaks memory
To manage notifications about this bug go to:
https://b
This is fixed in all releases above 16.04 so should be marked Fix
Released once the Xenial task is approved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655153
Title:
long-running stunnel leaks m
** Changed in: stunnel4 (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655153
Title:
long-running stunnel leaks memory
To manage notifications about this
** Changed in: stunnel4 (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655153
Title:
long-running stunnel leaks memory
To manage notifications about this bug
Fix confirmed to solve the SSL session leak for me - under constant
load, the RSS for stunnel would continue to grow - seeing an RSS of
50+ was common after a few hours. Now, after running overnight the
RSS is still at 13348 and I was able to remove a cron job to restart
stunnel.
--
You recei
** Also affects: stunnel4 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864391
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655153
Ti
A couple of additional comments:
To make testing easy, feel free to try this PPA with the patch:
https://launchpad.net/~lscotte/+archive/ubuntu/stunnel4/
Also, I discovered that this bug is present in the version provided in
jessie-backports, so I've also opened this bug in upstream Jessie:
https
The attachment "stunnel4_5.30-1.1.debdiff" seems to be a debdiff. The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag,
I have a possible patch for this by backporting a specific fix related
to a SSL session leak from upstream stunnel4. It seems to be working
well for me.
With 5.30-1 (the current version in Xenial), the RSS keeps growing. With
this patch applied, RSS grows to around ~13000 and stays there.
It's so
** Changed in: stunnel4 (Ubuntu)
Importance: Undecided => Medium
** Changed in: stunnel4 (Ubuntu)
Importance: Medium => High
** Changed in: stunnel4 (Ubuntu)
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
It is quite likely that this is a bug which was introduced in stunnel
5.27[1] and subsequently fixed in 5.33[2]:
- Fixed a TLS session caching memory leak (thx to Richard Kraemer).
Before stunnel 5.27 this leak only emerged with sessiond enabled.
[1] https://www.stunnel.org/pipermail/stunne
We are seeing the same issue, but only since upgrading from trusty to
xenial.
After about 1 day:
F UID PID PPID PRI NIVSZ RSS WCHAN STAT TTYTIME COMMAND
1 116 1512 1 20 0 711992 512324 - Ss ? 1:46
/usr/bin/stunnel4 /etc/stunnel/stunnel.conf
After re
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: stunnel4 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655153
Title:
l
27 matches
Mail list logo
