Your message dated Wed, 29 Sep 2010 14:33:49 +0000
with message-id <[email protected]>
and subject line Bug#598387: fixed in dtc-xen 0.5.13-1
has caused the Debian Bug report #598387,
regarding dtc-xen statslogger breaks and dtc-xen leaks memory after a xm 
start/stop
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
598387: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598387
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dtc-xen
Version: 0.5.11-1
Severity: grave

We have discovered that when a xm start/stop/shutdown is requested using
the dtc-xen SOAP daemon, dtc-xen tries to trap the stdout/stderr in
order to be able to forward it to the SOAP client that connects to it.
The issue is that after it did so, it didn't release stderr/stdout,
so that they are going into an internal variable of dtc-xen instead.

The result is that, after a xm start/stop/shutdown:
- dtc-xen leaks memory, with a variable that takes the output of
xm list every minutes
- the dataCollector thread that does xm list cannot get the CPU
statistics as it was designed for, because the output is redirected
to a variable.

Version 0.5.12-1 that I just uploaded in SID should correct the above
issue, but I think it was important to open a RC bug so that this can
be tracked by the RT. Sorry that I didn't open the bug first, and closed
it in the package, but as it stands, I don't think it deserves a new
upload just to fix that fact. I will tag and close this bug
appropriately as dtc-xen migrates from SID to Testing. Let me know if
you a new upload with a Close: #X is needed.

Cheers,

Thomas Goirand (Zigo)

-- System Information:
Debian Release: 5.0.5
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-4-xen-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash



--- End Message ---
--- Begin Message ---
Source: dtc-xen
Source-Version: 0.5.13-1

We believe that the bug you reported is fixed in the latest version of
dtc-xen, which is due to be installed in the Debian FTP archive:

dtc-xen-firewall_0.5.13-1_all.deb
  to main/d/dtc-xen/dtc-xen-firewall_0.5.13-1_all.deb
dtc-xen_0.5.13-1.diff.gz
  to main/d/dtc-xen/dtc-xen_0.5.13-1.diff.gz
dtc-xen_0.5.13-1.dsc
  to main/d/dtc-xen/dtc-xen_0.5.13-1.dsc
dtc-xen_0.5.13-1_all.deb
  to main/d/dtc-xen/dtc-xen_0.5.13-1_all.deb
dtc-xen_0.5.13.orig.tar.gz
  to main/d/dtc-xen/dtc-xen_0.5.13.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand <[email protected]> (supplier of updated dtc-xen package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Wed, 29 Sep 2010 21:50:02 +0800
Source: dtc-xen
Binary: dtc-xen dtc-xen-firewall
Architecture: source all
Version: 0.5.13-1
Distribution: unstable
Urgency: low
Maintainer: Thomas Goirand <[email protected]>
Changed-By: Thomas Goirand <[email protected]>
Description: 
 dtc-xen    - SOAP daemon and scripts to allow control panel management for Xen
 dtc-xen-firewall - A small firewall script for your dom0
Closes: 598387
Changes: 
 dtc-xen (0.5.13-1) unstable; urgency=low
 .
   * New upstream version fixing:
     - The last upgrade made xm start/stop/shutdown not working at all,
     so we now remove completely the stdout/stderr trick. It wont be
     reporting issues, but at least it will work (Closes: #598387).
Checksums-Sha1: 
 a16e084ab450170abb74f80ba9326c79dd7c4f66 1158 dtc-xen_0.5.13-1.dsc
 4869a25919f61b4352f72937e80c8cb304f19426 57923 dtc-xen_0.5.13.orig.tar.gz
 f88f6517027289526db1f9a9f91eb0876a859ca8 51206 dtc-xen_0.5.13-1.diff.gz
 005de8f80f4d0ee68ab58ded4c4cd76218ec2295 89312 dtc-xen_0.5.13-1_all.deb
 d2371675632925d8ad07a9cab6a3473a6047e13e 11724 
dtc-xen-firewall_0.5.13-1_all.deb
Checksums-Sha256: 
 9ea37ec8b238114a6b34bddc1588c769fc5fe6b7a801f67a4506222b61224ed8 1158 
dtc-xen_0.5.13-1.dsc
 76dc6698409eb8d56b3d9dfc5d6c69f8e9b4c5acd22f64bc566265e4ce68d312 57923 
dtc-xen_0.5.13.orig.tar.gz
 52e5455d262d863f6a3caab16936128030c6419149adc51f66af5105b593cd5e 51206 
dtc-xen_0.5.13-1.diff.gz
 2bcefa67c06f7d93578646fa68068e836365799cd65b179500e9df924277b3b4 89312 
dtc-xen_0.5.13-1_all.deb
 62bb047f16645987b01a27bc7f908c897ab7e013e271d496feabbe0d16383f93 11724 
dtc-xen-firewall_0.5.13-1_all.deb
Files: 
 11838ff81304447e7deae70c88751386 1158 web extra dtc-xen_0.5.13-1.dsc
 1d279ffd4452553bc325e676b16a32d1 57923 web extra dtc-xen_0.5.13.orig.tar.gz
 48fe419171a481ad0df81afe1dd69717 51206 web extra dtc-xen_0.5.13-1.diff.gz
 9898b4ba949cd3a2f8476c9b7a0c8576 89312 web extra dtc-xen_0.5.13-1_all.deb
 5ed753df91c6e9c2c07e4f61aa96f10a 11724 web extra 
dtc-xen-firewall_0.5.13-1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkyjR9UACgkQl4M9yZjvmkn3IACgvWuMXPlX4vajo1dkrHtuvOmx
7msAoIMCbFb7qVzAip1J5GlL8vvrimLr
=bEOf
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to