On Wed, Dec 02, 2020 at 05:34:52PM +0000, Stuart Henderson wrote:
> I didn't manage to track down a fix but I've set nsca-ng back to using
> openssl/1.0.2 for now, my glasses do not permit looking at BIO_* for
> more than a few moments.
Seems reasonable.
Turns out this is also broken client side where I use a literal hostname in
send_nsca.cfg:
send_nsca: [FATAL] Socket error (xxx.yyy.xyz): Broken pipe
Putting in an ip address fixes things.
>
>
> On 2020/12/02 17:23, Florian Obser wrote:
> > Looks like this thing might be legacy IP only.
> > I work around the problem by adding:
> > listen = "0.0.0.0"
> > to /etc/nsca-ng.cfg
> >
> > Having glanced at the code in src/common/tls.c could this be an
> > openssl update?
> >
> > Don't think I'll have a lot of time digging into this though.
> >
> > On Wed, Dec 02, 2020 at 04:44:27PM +0100, Florian Obser wrote:
> > > After the recent nsca-ng update it no longer starts:
> > >
> > > nsca-ng: [FATAL] Cannot bind to *:5668: Invalid argument
> > >
> > > My nsca-ng config is fairly simple:
> > >
> > > # cat /etc/nsca-ng.cfg
> > > command_file = "/var/icinga/rw/icinga.cmd"
> > >
> > > authorize "*" {
> > > password = "XXX"
> > > hosts = ".*"
> > > services = ".*"
> > > }
> > >
> > > I don't recall if the previous version was listening on v4, v6 or
> > > both.
> > > It starts for example with:
> > > nsca-ng -b 127.0.0.1
> > >
> > > Thanks,
> > > Florian
> > >
> > > --
> > > I'm not entirely sure you are real.
> > >
> >
> > --
> > I'm not entirely sure you are real.
> >
>
--
I'm not entirely sure you are real.
