--- Log opened Fri Oct 02 00:00:35 2020 00:01 -!- jasan [~jasan@tunnel509499-pt.tunnel.tserv27.prg1.ipv6.he.net] has joined #c-lightning 00:02 -!- ctrlbreak_MAD [~ctrlbreak@159.2.182.106] has quit [Ping timeout: 258 seconds] 00:09 < jasan> Next Monday is meeting. 00:09 < jasan> @8PM UTC 00:10 < jasan> 5 Oct 00:32 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Remote host closed the connection] 01:00 -!- netopso [~user@cloud608804.fastpipe.io] has joined #c-lightning 01:00 < netopso> Hi everyone 01:02 < netopso> working on a weird problem where a) I have 3 channels open, b) all of them are CHANNELD_NORMAL, c) `listpeers` shows `"connected": false` for *all* of them, and d) even *after* doing `connect` for every node ID (which doesn't fix the issue) `ping NODEID` returns `"message": "Unknown peer"` 01:03 < netopso> Haven't found any github issues related to this, and I'm using 0.9.1 01:03 < netopso> Any ideas? 01:04 < liberliver> az0re: darosior: thanks. regarding mainnet-testnet problem I have a clue that my plugin may return mainnet fees that's why LN node reports inconsistency. Thank you for help, I will try to resolve this issue 01:11 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning 01:13 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 240 seconds] 01:18 < jasan> netopso: Are those three channels open to hosts you can verify they are running? 01:35 -!- Ed0 [~edouard@2001:41d0:401:3100::4897] has joined #c-lightning 01:37 < netopso> jasan: well I can do `connect NODEID` and it returns the usual (non-error) response with feature code 01:37 < jasan> I see. 01:38 < netopso> I did just try restarting lightningd and it seems to be looping, restarting over and over again 01:39 < netopso> Oct 02 08:13:45 2800-019 systemd[1]: Started C-Lightning daemon. 01:39 < netopso> Oct 02 08:13:46 2800-019 lightningd[21359]: pay: Failed to parse RPC JSON response '2020-10-02T08:13:46.185Z DEBUG lightningd: Adding block 650729' 01:39 < netopso> Oct 02 08:13:56 2800-019 systemd[1]: lightningd.service: Main process exited, code=exited, status=1/FAILURE 01:42 < netopso> Haven't been able to find any more detailed logging information 01:43 < darosior> liberliver: actually your plugin should return "test" to getchaininfo, more about it here https://lightning.readthedocs.io/PLUGINS.html#bitcoin-backend 01:45 < jasan> netopso: so then your node is not online 01:45 < jasan> netopso: Do you use any special settings? Or is it rather default? What version? 01:46 < netopso> jasan: default. 0.9.1 01:46 < netopso> just upgraded via `apt` to lastest version as part of troubleshooting 01:46 < jasan> netopso: What happens when you run "bitcoin-cli getblockchaininfo" ? 01:49 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds] 01:51 -!- jonatack [~jon@37.170.2.30] has joined #c-lightning 02:00 < liberliver> darosior: fantastic. found relevant piece of code. Thank you very much. Missed this thing completely despite it is in main() 02:04 < netopso> jasan: not going to paste the whole output here, but everything looks ok 02:04 < netopso> "verificationprogress": 0.9999971033183431, 02:05 -!- kexkey [~kexkey@89.36.78.198] has quit [Ping timeout: 264 seconds] 03:10 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 03:12 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 03:16 -!- jonatack [~jon@37.170.2.30] has quit [Ping timeout: 256 seconds] 03:26 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 03:26 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 03:28 -!- skme9_ [~skme9@2402:3a80:6a7:461c:7c61:3a3c:6644:2167] has joined #c-lightning 03:31 -!- skme9 [~skme9@2402:3a80:6b1:49a5:8d17:c5ec:1a13:9518] has quit [Ping timeout: 240 seconds] 03:46 -!- skme9__ [~skme9@2402:3a80:6a8:d644:7c61:3a3c:6644:2167] has joined #c-lightning 03:50 -!- skme9_ [~skme9@2402:3a80:6a7:461c:7c61:3a3c:6644:2167] has quit [Ping timeout: 260 seconds] 04:04 < netopso> jasan: well, rebooting the machine fixed it 04:08 < jasan> netopso: congratulations 04:08 < jasan> Have a nice weekend! 04:08 -!- jasan [~jasan@tunnel509499-pt.tunnel.tserv27.prg1.ipv6.he.net] has quit [Quit: Bye!] 04:10 < netopso> Thanks, you too! 04:37 -!- jonatack [~jon@88.124.242.136] has joined #c-lightning 04:42 -!- jonatack [~jon@88.124.242.136] has quit [Ping timeout: 258 seconds] 04:43 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning 04:58 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 06:30 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning 06:33 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 07:40 -!- Netsplit *.net <-> *.split quits: fjahr, felixweis 07:41 -!- Netsplit over, joins: felixweis, fjahr 07:46 -!- fjahr [sid374480@gateway/web/irccloud.com/x-rbbwbtbigjvdlmkh] has quit [Ping timeout: 244 seconds] 07:48 -!- kexkey [~kexkey@37.120.205.214] has joined #c-lightning 07:49 -!- fjahr [sid374480@gateway/web/irccloud.com/x-aziopllegdxggubc] has joined #c-lightning 07:50 -!- felixweis [sid154231@gateway/web/irccloud.com/x-krefugjevbfmhthz] has quit [Ping timeout: 244 seconds] 07:53 -!- felixweis [sid154231@gateway/web/irccloud.com/x-obqpsjwlqqjjaomn] has joined #c-lightning 08:26 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds] 08:31 -!- alko89 [~alko89@unaffiliated/alko89] has quit [Quit: ZNC 1.7.5 - https://znc.in] 08:31 -!- alko89 [~alko89@unaffiliated/alko89] has joined #c-lightning 08:32 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Quit: liberliver] 08:48 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds] 09:52 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection] 10:02 -!- skme9 [~skme9@2402:3a80:6a8:d644:7c61:3a3c:6644:2167] has joined #c-lightning 10:02 -!- skme9__ [~skme9@2402:3a80:6a8:d644:7c61:3a3c:6644:2167] has quit [Ping timeout: 240 seconds] 10:11 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning 10:47 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection] 11:26 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 11:35 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 11:42 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 11:43 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 11:46 -!- skme9 [~skme9@2402:3a80:6a8:d644:7c61:3a3c:6644:2167] has quit [Ping timeout: 244 seconds] 12:36 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning 12:58 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection] 14:00 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning 14:13 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 15:10 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 15:12 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 15:48 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Remote host closed the connection] 15:48 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Read error: Connection reset by peer] 15:48 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning 15:59 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning 16:10 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning 16:10 < az0re> Is there any way to leave a review of a channel peer? 16:10 < az0re> e.g. on 1ml.com 16:11 < zmnscpxj_> well, how would anyone who accepts review know that you are not a sybil leaving bad reviews to harm that node? 16:13 < az0re> Sign it with my node pubkey? 16:13 < az0re> I dunno 16:13 < az0re> 1ml lets you prove node ownership by opening a channel 16:13 < zmnscpxj_> One can argue that the size and age of your channel with a node is sufficient "review" 16:13 < az0re> So they could verify that you did have the channel you're reviewing 16:13 < zmnscpxj_> if you think it is a good node, you will maintain a channel with that node 16:14 < zmnscpxj_> if you think it is a bad node, you close your channel with it and avoid channeling with it 16:14 < zmnscpxj_> that gives you some financial weight, as your funds could be elsewhere 16:14 < zmnscpxj_> instead 16:15 < az0re> My problem is someone I opened a channel to stayed offline for days and days, while my node is online, then he broadcasts a unilateral close for no reason making me pay a gigantic channel close fee while the mempool is 50MB 16:15 < az0re> That goes beyond the age/capacity of the channel; that's just really shitty peer behavior 16:15 < zmnscpxj_> ouch 16:15 < az0re> WTF dude, so uncalled for 16:16 < zmnscpxj_> one thing my (unreleased) auto node manager does is that it runs autopilot algos even while it has no money to put in channels 16:16 < zmnscpxj_> then nodes it finds are put under investigation, i.e. periodically we try to connect to it 16:17 < zmnscpxj_> if it is unreachable, it gets dropped from the pool of potential channeling candidates 16:17 < zmnscpxj_> which at least avoids nodes with flaky onlineness 16:17 < az0re> That's a good idea, but what about nodes without listening addresses? 16:17 < az0re> How do you measure availability there? 16:17 < zmnscpxj_> if they have no listening address, how do you contact them and then make a channel with them later? 16:18 < az0re> They can connect to you or they can temporarily open a listening address 16:18 < az0re> Just needs some out-of-band coordination 16:18 < zmnscpxj_> requires manual intervention, which is out of scope for an "auto" node manager 16:18 < az0re> I suppose 16:18 < zmnscpxj_> maybe when I can start to beat the Turing test and get it on IRC so it can pester node operators itself directly :P 16:19 < az0re> Getting more node operators on IRC would be a start :) 16:46 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 16:48 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 17:00 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 17:01 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 18:02 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection] 18:03 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 18:17 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Quit: Leaving] 18:59 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds] 19:07 -!- skme9 [~skme9@2402:3a80:6a8:d644:e45c:1252:6ad5:a996] has joined #c-lightning 19:26 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 19:47 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 19:47 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 20:14 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 260 seconds] 21:02 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Remote host closed the connection] 21:24 -!- aludra-420 [ad2c22aa@173.44.34.170] has joined #c-lightning 21:42 < aludra-420> Hi 21:42 < aludra-420> 20201003T040641Z: root@aludra-420:~/trustedcoin# makemkdir -p distgox -ldflags="-s -w" -tags="full" -osarch="darwin/amd64 linux/386 linux/amd64 linux/arm freebsd/amd64" -output="dist/trustedcoin_{{.OS}}_{{.Arch}}"Number of parallel builds: 1--> freebsd/amd64: github.com/fiatjaf/trustedcoin--> darwin/amd64: github.com/fiatjaf/trustedcoin--> 21:42 < aludra-420> linux/386: github.com/fiatjaf/trustedcoin--> linux/amd64: github.com/fiatjaf/trustedcoin--> linux/arm: github.com/fiatjaf/trustedcoin20201003T040925Z: root@aludra-420:~/trustedcoin# lightningdlightningd: SQLITE version mismatch: compiled 3022000, now 303100120201003T040932Z: root@aludra-420:~/trustedcoin# 21:43 < aludra-420> anyone have an idea what to do next on this? 22:03 -!- aludra-420 [ad2c22aa@173.44.34.170] has quit [Ping timeout: 245 seconds] 22:16 -!- aludra-420 [cc98d672@204.152.214.114] has joined #c-lightning 22:53 -!- skme9 [~skme9@2402:3a80:6a8:d644:e45c:1252:6ad5:a996] has quit [Ping timeout: 240 seconds] 22:55 -!- skme9 [~skme9@2402:3a80:6a8:d644:e45c:1252:6ad5:a996] has joined #c-lightning 23:04 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection] 23:05 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning --- Log closed Sat Oct 03 00:00:36 2020