[Svxlink-devel] Error on Echolink client connect - terminate called after throwing an instance of 'std::logic_error'

[<ju...@po...>]

Good day,

I trust everyone is well.

 

I have a running svxlink server, and decided to compile the latest version
on a separate raspberry pi.

The service starts up, but when I connect to it via an echolink client, it
crashes.

 

The logs don't show the detail, but if I run it from the command line, I see
the error.

 

Firewall on router setup correctly (other pi works using same IP), checked
incoming traffic using tcpdump, packets are received.

 

See below for an example:

 

pi@raspberrypi:~ $ sudo svxlink --config=/etc/svxlink/svxlink.conf
--pidfile=/var/run/svxlink.pid --runasuser=svxlink

SvxLink v1.6.99.15 Copyright (C) 2003-2019 Tobias Blomberg / SM0SVX

 

SvxLink comes with ABSOLUTELY NO WARRANTY. This is free software, and you
are

welcome to redistribute it in accordance with the terms and conditions in
the

GNU GPL (General Public License) version 2 or later.

 

Using configuration file: /etc/svxlink/svxlink.conf

--- Using sample rate 48000Hz

 

Starting logic: SimplexLogic

Loading RX: Rx1

Loading TX: Tx1

Loading module "ModuleMetarInfo" into logic "SimplexLogic"

        Found /usr/lib/arm-linux-gnueabihf/svxlink/ModuleMetarInfo.so

        Module MetarInfo v1.2.0 starting...

Loading module "ModuleEchoLink" into logic "SimplexLogic"

        Found /usr/lib/arm-linux-gnueabihf/svxlink/ModuleEchoLink.so

        Module EchoLink v1.4.99.0 starting...

SimplexLogic: Event handler script successfully loaded.

EchoLink directory status changed to ON

--- EchoLink directory server message: ---

EchoLink Server v2.5.9997

 

ECHOEC2-3: Herndon, VA USA

 

Spurious audio packet received from 44.137.75.245

Incoming EchoLink connection from ZS6JGP (Justin) at 44.137.75.245

terminate called after throwing an instance of 'std::logic_error'

  what():  basic_string::_M_construct null not valid

Aborted

 

Warm regards,

Justin