Usually dont respond. But you have been waiting. And it seems simple. According to your vpn log. A computer is "in the future". Insure your 2 nodes are on the correct time.
Honestly. One node being to far in the future... breaks things. Try that. On Wed, Mar 6, 2019, 1:42 PM Håvard Rabbe <[email protected]> wrote: > Hi > I have not tried systemd-coredump yet but I found something strange in my > syslog file. > > Like this message in the en of the log file: > tincd[10322]: segfault at 7fffb3180000 ip 00007ff7937f11c2 sp > 00007fffb317dd68 error 4 in libc-2.23.so[7ff7936a3000+1c0000] > > There is more in the attached syslog file. Any clues? > > > Best Regards, > > Håvard Rabbe > > > On 14 Feb 2019, at 02:27, Hamish Moffatt <[email protected]> wrote: > > On 13/2/19 12:28 am, Tomasz Chmielewski wrote: > > On 2019-02-12 22:12, Håvard Rabbe wrote: > > Hi > Im running tinc 1.1pre17. My problem is that my tinc nodes > occasionally crashes. When it crashes the tinc node is not running > anymore. Time between failure can be sometimes days or weeks. > > Do anyone here have a proposal for how to debug and get this problem > solved? > > > I assume it doesn't produce anything in the log? > > Try strace? > > > > A coredump would be more interesting and wouldn't affect performance. If > you're running tinc from systemd, you can install systemd-coredump. > > > Hamish > > _______________________________________________ > tinc mailing list > [email protected] > https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc > > > _______________________________________________ > tinc mailing list > [email protected] > https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc >
_______________________________________________ tinc mailing list [email protected] https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
