[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#698802: marked as done (release-notes: NSCA compatibility problems should be described)

Your message dated Mon, 17 Apr 2017 09:27:05 -0400
with message-id <20170417132705.qks5dminfzzsty7n@curie.anarc.at>
and subject line Re: Bug#698802: release-notes: NSCA compatibility problems should be described
has caused the Debian Bug report #698802,
regarding release-notes: NSCA compatibility problems should be described
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 owner@bugs.debian.org

698802: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698802
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release-notes
Severity: wishlist
Tags: patch

There are a few issues with upgrading from nsca 2.7 to 2.9 that IMO
should be documented in the release notes:

- #670373: nsca 2.7.2 / nsca-client 2.9.1: do not communicate
- #662642: Daemon fails to handle packets with more than five reports
- #685457: nsca: Incompatibility between munin and nsca-2.9.1

Here's a suggestion:


Both the command line interface to nsca-client and the network protocol
spoken between nsca-client and nsca have been changed from version
2.7.2+nmu2 (squeeze) to version 2.9.1-2 (wheezy) in incompatible ways:

- nsca 2.7.2 (server) is not able to receive messages from
  nsca-client 2.9.1-2 at all.

- Whereas nsca-client 2.7.2 expected multiple status messages passed to
  it via STDIN to be separated by newline (0x0a) characters, the record
  separator has been changed to a ETB / (0x17) character by 2.9.1.

- It is impossible to transmit more than five status messages during one
  network connection.

To keep a working monitoring setup from breaking over these
incompatibilities, the following steps should be taken before any
systems are upgraded to wheezy:

- All nsca servers should be upgraded to 2.9.1 before any clients are
  upgraded. Squeeze backports of the nsca and nsca-client packages are
  available via backports.debian.org to ease the transition.

- Care should be taken that external programs feeding multiple service
  status records through nsca-client are adapted to use the ETB
  character as a record separator.

  A wrapper script that calls » tr '\n' '\027' « should be sufficient.

  Affected packages are: munin [ FIXME: insert others here ].

- Care should be taken that external programs transmit no more than five
  status records per nsca-client invocation.


-- System Information:
Debian Release: 7.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

--- End Message ---
--- Begin Message ---
On Sun, Apr 07, 2013 at 09:11:34PM +0200, Julien Cristau wrote:
> On Sat, Apr  6, 2013 at 02:54:42 +0200, Joost van Baal-Ilić wrote:
> > Hi Hilko,
> > 
> > On Mon, Feb 18, 2013 at 11:38:53PM +0100, Hilko Bengen wrote:
> > > * Hilko Bengen:
> > > 
> > > > * Joost van Baal-Ilić:
> > > >> Could you please do a
> > > >>
> > > >>  svn co svn://svn.debian.org/svn/ddp/manuals/trunk/release-notes/en
> > > >>
> > > >> and hack up some DocBook XML code to get your text in? That'd allow me
> > > >> to fix this issue even more soon.
> > > >
> > > > Will do once I know whether the nsca and nsca-client packages are going
> > > > to be updated with a NEWS.Debian file.
> > > 
> > > It's not clear whether nsca will get that NEWS.Debian file. What should
> > > we do?
> > 
> > If there's no action from nsca-maintainers in some days, fall back to update
> > release notes.  We do have a draft text for that, don't we?
> > 
> If it's not important enough to be documented in the package, then it
> probably doesn't warrant a release notes entry either...

Alright, closing then, after a 4 year timeout.


L'adversaire d'une vraie liberté est un désir excessif de sécurité.
                        - Jean de la Fontaine

Attachment: signature.asc
Description: PGP signature

--- End Message ---

Reply to: