--- Log opened Tue Dec 22 00:00:52 2020
01:12 -!- jonatack [~jon@213.152.162.154] has quit [Quit: jonatack]
01:16 -!- jonatack [~jon@88.124.242.136] has joined #c-lightning
01:21 -!- jonatack [~jon@88.124.242.136] has quit [Ping timeout: 256 seconds]
01:21 -!- jonatack [~jon@213.152.161.30] has joined #c-lightning
01:49 -!- raucao [~raucao@skippe2.nine.ch] has joined #c-lightning
01:49 < raucao> hi there. anyone knows how to best migrate a c-lightning node to a new machine?
01:50 < raucao> i rsynced the lightning dir and adjusted the config, but i get fatal errors on the new one
01:51 < raucao> searched github issues and the web, but nothing useful so far
01:51 < raucao> i do have a backtrace, but no real error message
01:52 < raucao> could be something with the new config as well. i have set a different announce-addr, because the VM isn't on the internet
01:52 < raucao> bind-addr=0.0.0.0                                                                     │
01:52 < raucao> announce-addr=148.251.237.73
01:52 < raucao> (by "isn't on the internet" i mean it doesn't have its own public IP, but gets traffic forwarded from the host via haproxy)
01:53 < raucao> > lightning_connectd: FATAL SIGNAL 6
01:54 < raucao> seems to be hitting this abort:
01:54 < raucao> https://github.com/ElementsProject/lightning/blob/master/common/wireaddr.c#L229
01:59 < raucao> is there something cached about the networking/connections perhaps?
01:59 < raucao> i get a different trace now
01:59 < raucao> https://github.com/ElementsProject/lightning/blob/master/ccan/ccan/tal/tal.c#L699
02:00 < raucao> but all seems to stem from connectd 
02:05 -!- kexkey [~kexkey@static-198-54-132-138.cust.tzulo.com] has quit [Ping timeout: 272 seconds]
02:10 < raucao> (btw, also confirmed that it doesn't break when running without the old node data)
02:31 -!- Jackielove4u [uid43977@gateway/web/irccloud.com/x-jhzugnblbuxavtfw] has joined #c-lightning
03:04 -!- warren [~warren@fedora/wombat/warren] has quit [Ping timeout: 240 seconds]
03:07 -!- warren [~warren@fedora/wombat/warren] has joined #c-lightning
03:19 -!- user____ [~user@mail.deeplinkmedia.com] has quit [Quit: leaving]
03:40 <@cdecker> raucao can you share the backtrace of the abort?
03:41 <@cdecker> Any change in architecture between the two machines?
05:36 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Disconnected by services]
05:36 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
05:36 -!- vasild_ is now known as vasild
05:49 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-grtgkzfemgwjcvcq] has left #c-lightning []
05:50 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-grtgkzfemgwjcvcq] has joined #c-lightning
07:52 -!- kexkey [~kexkey@static-198-54-132-154.cust.tzulo.com] has joined #c-lightning
07:58 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning
08:00 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 260 seconds]
08:02 -!- belcher_ is now known as belcher
08:29 < raucao> cdecker: yes, changed from running on metal to running in a kvm guest
08:30 <@cdecker> On a different CPU architecture?
08:39 < raucao> http://pastie.org/p/07LSLIkYI2AuVImLla42tI/raw
08:39 < raucao> yeah, i think it may have gone from intel to amd
08:39 < raucao> probably xenon to ryzen
08:42 < raucao> yes, intel core i7 to amd ryzen. confirmed
08:53 -!- ghost43_ [~daer@gateway/tor-sasl/daer] has joined #c-lightning
08:54 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 240 seconds]
09:09 <@cdecker> Ok, same exact version of c-lightning?
09:12 <@cdecker> Seems strange though that `connect->errors` seems to not be tal-allocated, if this is arch related
09:12 <@cdecker> I'll file an issue with the details and see if rusty can shed some light into what this might be
09:19 <@cdecker> Ok, filed as https://github.com/ElementsProject/lightning/issues/4297
09:31 -!- csknk [~csknk@unaffiliated/csknk] has joined #c-lightning
09:35 -!- csknk [~csknk@unaffiliated/csknk] has quit [Client Quit]
09:44 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has quit [Ping timeout: 240 seconds]
09:45 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has joined #c-lightning
10:36 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 260 seconds]
10:36 -!- StopAndDecrypt_ [~StopAndDe@82.102.23.218] has joined #c-lightning
10:43 -!- StopAndDecrypt_ [~StopAndDe@82.102.23.218] has quit [Ping timeout: 256 seconds]
11:33 <@niftynei> is there a clean command that gets the autodata gen'd files? 
11:33 <@niftynei> i tried 'maintainer-clean' but wasn't able to repro the same issue travis is having
11:36 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #c-lightning
11:38 < raucao> cdecker: fantastic, thanks!
11:46 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Quit: liberliver]
11:48 <@cdecker> niftynei: maintainer-clean or distclean usually does the trick
11:56 <@cdecker> raucao: one more thing that came to mind, how reproducible is the isue? i.e., does it happen every time you run, or only in some cases? In either case, could you prefix your `lightningd` command line with `valgrind --trace-children=yes -q `? That'd allow us to see if there is some invalid memory access that could explain the issue
14:04 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-grtgkzfemgwjcvcq] has left #c-lightning []
14:04 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-grtgkzfemgwjcvcq] has joined #c-lightning
15:09 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds]
16:14 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
16:15 -!- ghost43_ [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 240 seconds]
16:51 -!- jonatack [~jon@213.152.161.30] has quit [Ping timeout: 264 seconds]
16:53 -!- jonatack [~jon@88.124.242.136] has joined #c-lightning
16:58 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
17:36 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
17:36 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Disconnected by services]
17:36 -!- vasild_ is now known as vasild
17:48 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
18:36 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Remote host closed the connection]
20:48 -!- sr_gi [~sr_gi@80.174.218.168.dyn.user.ono.com] has quit [Read error: Connection reset by peer]
20:48 -!- sr_gi [~sr_gi@80.174.218.168.dyn.user.ono.com] has joined #c-lightning
22:03 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Remote host closed the connection]
22:15 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-grtgkzfemgwjcvcq] has left #c-lightning []
22:15 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-grtgkzfemgwjcvcq] has joined #c-lightning
22:29 -!- fiatjaf1 [~fiatjaf@2804:7f2:2a8a:f273:ea40:f2ff:fe85:d2dc] has joined #c-lightning
22:33 -!- fiatjaf [~fiatjaf@186.213.91.147] has quit [Ping timeout: 260 seconds]
--- Log closed Wed Dec 23 00:00:55 2020