--- Day changed Mon Aug 13 2018 00:06 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 00:06 < rusty> CubicEarth: wait, 5000-400000 is a very round number?! Are you overriding fee levels? 00:07 < CubicEarth> rusty: Did you mean to ping molz ? 00:11 < rusty> molz: oops... Thanks CubicEarth 00:12 < rusty> molz: that is the default fee rate. But why is it using that? Is your bitcoind unable to estimate fees for some reason? 00:26 < rusty> molz: though if we're using the default rate, IMHO we shouldn't enforce fees on the peer. 00:28 < rusty> molz: do you have messages about "no fee estimate" in your logs? 00:33 < rusty> https://github.com/ElementsProject/lightning/issues/1836 00:40 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Ping timeout: 244 seconds] 00:44 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #c-lightning 03:58 < molz> rusty, sorry, i was asleep, just woke up, let me look 04:09 < molz> both nodes crashed because the server ran out of space which i didn't know, so the nodes were offline for a while not sure how many hours, then when i got them back up, i found all channels were closed, not sure if they were closed before the crash 04:21 < molz> im trying to get the crash.log from this server to my laptop so i can see if "no fee estimate" is there, but my bitcoind is on the latest version 0.6.2 (commit 2848aa808fde462c27bc36de982d7ed74e882a7b) 04:39 < molz> hm the crash.log file is huge 04:42 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 04:48 < rusty> molz: ah, I suspect bitcoind refuses to give fee estimates when it's behind, hence the fallback to defaults? 04:50 < rusty> molz: hard to know what the Right Thing to do in that case is, but dropping all channels isn't it! On the bright side, your pain gives us a great bug report. Will fix tomorrow, and def. before 0.6.1-rc1 04:54 < molz> rusty, im unable to get this crash.log but is there a way to get c-lightning to produce a normal debug log as it goes along? 04:55 < rusty> molz: log-file=filename log-level=debug (or info, the default) 04:59 < rusty> molz: just grep for 'Unable to estimate ' 05:00 < rusty> (on the server) 05:06 < molz> rusty, there's none 05:07 < molz> ~/.lightning$ tail crash.log | grep 'unable to estimate' 06:45 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 06:46 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 06:53 < jouke_> molz: with tail you are just looking at the last 10 lines and grep is case sensitive. 06:59 < molz> jouke_, how do you look at the log the last 24 hours? this log has 74 GB in size 07:12 -!- jouke_ [~jouke@a80-100-203-151.adsl.xs4all.nl] has quit [Changing host] 07:12 -!- jouke_ [~jouke@unaffiliated/komkommer] has joined #c-lightning 07:40 -!- RubenSomsen [uid301948@gateway/web/irccloud.com/x-xywgrzggmjhncptf] has quit [Quit: Connection closed for inactivity] 07:50 -!- tumi [tumi@u.nix.is] has joined #c-lightning 07:58 -!- qubenix [~qubenix@199.66.90.113] has quit [Quit: qubenix] 08:31 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 08:32 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 09:04 < blockstream_bot> [MattK, Blockstream] Is anyone here familair with the details of the HTLC transaction output scripts? Why the requirement for separate success and timeout transactions? Why not build the revocation delay into the main HTLC script? Thanks. 09:21 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds] 09:33 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 09:34 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 09:44 -!- qubenix [~qubenix@177.67.80.187] has joined #c-lightning 10:40 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 10:41 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 10:42 -!- rotarydialer [~rotarydia@unaffiliated/rotarydialer] has quit [Ping timeout: 240 seconds] 10:46 -!- rotarydialer [~rotarydia@unaffiliated/rotarydialer] has joined #c-lightning 10:57 -!- qubenix [~qubenix@177.67.80.187] has quit [Ping timeout: 244 seconds] 11:46 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 12:25 -!- Netsplit *.net <-> *.split quits: harding 13:32 -!- jonasschnelli_ [~jonasschn@unaffiliated/jonasschnelli] has joined #c-lightning 13:38 -!- qubenix [~qubenix@193.148.18.237] has joined #c-lightning 14:54 < rusty> molz: grep 'Unable to estimate' crash.log | tail 14:54 < rusty> blockstream_bot: we originally did, but it means that your HTLC timeout must be greater than your penalty timeout. This makes HTLC delays across the network larger. 14:57 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 14:59 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 15:46 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Quit: WeeChat 2.1] 15:46 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds] 16:01 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 16:11 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Read error: Connection reset by peer] 16:35 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds] 16:40 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 16:52 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 16:53 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 17:00 < molz> rusty, it's still searching, not sure how long it takes 17:01 < rusty> molz: I just noticed that we *append* to crash.log, which is how it got so big... 17:02 < rusty> molz: after this you should delete it... but grepping through GB can take a while. 17:13 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 17:25 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds] 17:33 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 17:48 -!- ken2812221_ [~ken281222@1.200.219.221] has joined #c-lightning 17:52 -!- drgrid [~TheCharla@109.236.87.57] has joined #c-lightning 17:57 -!- Netsplit *.net <-> *.split quits: ken2812221 18:04 -!- booyah [~bb@193.25.1.157] has joined #c-lightning 18:04 -!- jouke_ [~jouke@unaffiliated/komkommer] has joined #c-lightning 18:29 < molz> rusty, it found none 18:30 < rusty> molz: ... that is deeply weird. I'm working on your bug now, however: if we can't get a fee estimate we'll just allow anything. I'll also add a method to manually insert a fee estimate, which it will use until bitcoind gets its act together. 18:36 < rusty> molz: OK, the log can't get much over 20MB. Can you 'tail -c 40M crash.log > crash.log.tail' and send me crash.log.tail (should be v. quick!) 18:37 * rusty realizes he should keep a list of people he owes beers to, it's getting v. long... 18:45 < molz> ok got it, i can pastebin for you 18:45 < rusty> Sure, if pastebin doesn't barf on 40MB? 18:49 < molz> lol it does 18:50 < molz> how can i send to you? 18:50 < rusty> molz: do you have a Github acct? If not, you can mail it (I mean, email, not postal :) 18:50 < molz> oh you can paste this much on github? 18:51 < rusty> molz: zip and add attachment to https://github.com/ElementsProject/lightning/issues/1836 makes sense? 18:52 < rusty> Oh, they support gzip now apparently. Anyway, should get it under the 25MB limit. 18:53 < molz> 4.8MB 18:53 < rusty> molz: nice :) Please attach to PR above? 18:53 < molz> ok 18:55 < molz> rusty, sent 19:02 < rusty> molz: hmm, not as useful as I'd hoped. But weird, weird stuff in here, too.... you should delete that file so next crash is clean :) 19:03 < molz> ok rusty, i'm thinking of withdrawing my coin and start a new node 19:03 < rusty> molz: you certainly could. Though 0.6.1-rc1 should be next week, so maybe wait for that. OTOH, you seem to have a talent for hitting bugs, so don't let me stop you :) 19:04 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds] 19:04 < molz> haha thanks :D ok i'll wait for the RC :D 19:27 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 21:01 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 21:02 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 22:16 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection]