Segfaults on connection loss
zorun
zorun at polyno.me
Mon Jun 16 09:57:23 CEST 2014
Hi,
I got a new Tinc segfault, again in a condition of bad network connectivity:
Old connection_t for mejis (XX.XX.XX.XX port 656) status 0010 still lingering, deleting...
Segmentation fault (core dumped)
This is tinc version 1.0.24 on Archlinux x86_64:
# tincd --version
tinc version 1.0.24 (built May 12 2014 09:24:12, protocol 17)
I have a core dump, but I doubt it's very useful, as it doesn't have
any debug symbols.
On Sun, Mar 16, 2014 at 11:47:58AM +0100, zorun wrote:
> On Fri, Nov 08, 2013 at 12:36:57AM +0200, Tuomas Silen wrote:
> > Hi there,
> >
> > I'm seeing quite frequent segfaults around check_dead_connections()
> > and terminate_connection() when the tcp meta connection to a node
> > times out (or is e.g. firewalled), usually it happens when there's
> > heavy packet loss:
>
> I ran into a similar issue. The underlying network was experiencing
> troubles (ARP storm, heavy packet loss, blackholes), which led Tinc
> 1.0.19 to segfault. Here are all the logs I've got:
>
> http://paste.aliens-lyon.fr/EID
>
> This happened on Debian stable, tinc 1.0.19-3.
>
> Thanks!
> _______________________________________________
> tinc-devel mailing list
> tinc-devel at tinc-vpn.org
> http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc-devel
More information about the tinc-devel
mailing list