Gettxout bad balue
See original GitHub issueI was syncing clightning with spruned, but clighting randomly crashes because received bad value from spruned; this is the stack-trace:
+1060.706053809 lightningd(6109):BROKEN: bitcoin-cli -rpcconnect=127.0.0.1 -rpcport=8339 -rpcuser=test -rpcpassword=test gettxout 4a4d6e40c728ecb9131ee57cbc5b8bc841c27d88348bf30d8c35ebe0d9751038 0: had bad value ({? "value": 0.0002,? "scriptPubKey": {? "asm": "",? "reqSigs": 0,? "type": "",? "addresses": [? ],? "hex": "002023df98f8eada1ba8d57c06f311e33cd5dbb4fd875c8887e04e81688c527d5902"? },? "confirmations": 442,? "bestblock": "00000000000000000025a670c34f912e09f74da0220de84de1e5887373d56652"?}?)?
+1060.719547968 lightningd(6109):BROKEN: FATAL SIGNAL 6 (version v0.7.0-52-g901bd7c)
+1060.719574006 lightningd(6109):BROKEN: backtrace: common/daemon.c:45 (crashdump) 0x55a3a105dbe4
+1060.719625304 lightningd(6109):BROKEN: backtrace: (null):0 ((null)) 0x7fd0a91f105f
+1060.719632710 lightningd(6109):BROKEN: backtrace: (null):0 ((null)) 0x7fd0a91f0fff
+1060.719658079 lightningd(6109):BROKEN: backtrace: (null):0 ((null)) 0x7fd0a91f2429
+1060.719664506 lightningd(6109):BROKEN: backtrace: lightningd/log.c:630 (fatal) 0x55a3a103ed25
+1060.719670709 lightningd(6109):BROKEN: backtrace: lightningd/bitcoind.c:562 (process_gettxout) 0x55a3a102953d
+1060.719676200 lightningd(6109):BROKEN: backtrace: lightningd/bitcoind.c:208 (bcli_finished) 0x55a3a1028568
+1060.719681693 lightningd(6109):BROKEN: backtrace: ccan/ccan/io/poll.c:183 (destroy_conn) 0x55a3a109b475
+1060.719686528 lightningd(6109):BROKEN: backtrace: ccan/ccan/io/poll.c:189 (destroy_conn_close_fd) 0x55a3a109b495
+1060.719720246 lightningd(6109):BROKEN: backtrace: ccan/ccan/tal/tal.c:235 (notify) 0x55a3a10a748b
+1060.719726722 lightningd(6109):BROKEN: backtrace: ccan/ccan/tal/tal.c:397 (del_tree) 0x55a3a10a797a
+1060.719731636 lightningd(6109):BROKEN: backtrace: ccan/ccan/tal/tal.c:481 (tal_free) 0x55a3a10a7d06
+1060.719736542 lightningd(6109):BROKEN: backtrace: ccan/ccan/io/io.c:451 (io_close) 0x55a3a1099e16
+1060.719743927 lightningd(6109):BROKEN: backtrace: ccan/ccan/io/poll.c:314 (io_loop) 0x55a3a109b89c
+1060.719748955 lightningd(6109):BROKEN: backtrace: lightningd/lightningd.c:829 (main) 0x55a3a103cd50
+1060.719754118 lightningd(6109):BROKEN: backtrace: (null):0 ((null)) 0x7fd0a91de2e0
+1060.719789128 lightningd(6109):BROKEN: backtrace: (null):0 ((null)) 0x55a3a10276e9
+1060.719793212 lightningd(6109):BROKEN: backtrace: (null):0 ((null)) 0xffffffffffffffff
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Get rid of "Bad" Value - PI Square - OSIsoft
I am getting "Bad" value for all pi points. I am using interface failover and as seen in attached snap, am getting device...
Read more >How to find information about "bad value" error?
I have some code which generates a report in a huge .csv file. This involves 5k lines of code with various user-def functions...
Read more >BadValues - Discussion of bad value support in PDL
To find out if PDL has been compiled with bad value support, look at the values of either $PDL::Config{WITH_BADVAL} or $PDL::Bad::Status - if...
Read more >What If You Have “Bad” Values? | Psychology Today
"But what if there is not enough love in the world even then?" asks the mind. "Will there be?" "I dunno" comes the...
Read more >Personal Values: How to Know Who You Really Are
What are your most important personal values? Do you actually value what you say you do, or are you lying to yourself? And...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
No crash for this reason since 22 hours, I think you can close this
Test started; if tomorrow
ls ~/.lightning | grep crash | wc -l
is 0, I consider it as fixed from my pov (y)