Fatal signal 11 received when connecting to node #508
Comments
|
Thanks for reporting this @2pac1, I noticed that the build for that image is really old, so I fixed the Dockerfile and re-built the image, could you try again? |
|
i just did, same thing. will reboot server now and try it once again. i dont know what i am doing wrong |
{ "id" : "0385c62fa5d048f858de8407d4fbaa4e9bd3ec122392663797d9c15eede2b518d1", "port" : 9735, "testnet" : false, "version" : "v0.5.2-2016-11-21-820-g5db4e11", "blockheight" : 502358 }{
"version": 140200,
"subversion": "/Satoshi:0.14.2/",
"protocolversion": 70015,
"localservices": "000000000000000d",
"localrelay": true,
"timeoffset": -1,
"networkactive": true,
"connections": 15,
"networks": [
{
"name": "ipv4",
"limited": false,
"reachable": true,
"proxy": "",
"proxy_randomize_credentials": false
},
{
"name": "ipv6",
"limited": false,
"reachable": true,
"proxy": "",
"proxy_randomize_credentials": false
},
{
"name": "onion",
"limited": true,
"reachable": false,
"proxy": "",
"proxy_randomize_credentials": false
}
],
"relayfee": 0.00001000,
"incrementalfee": 0.00001000,
"localaddresses": [
],
"warnings": ""
}when I try to connect with: ERROR I GET IS: lightning-cli: Non-object response and |
|
any chance you could help?
tnx a ton
…On Wed, Jan 3, 2018 at 1:38 PM, Christian Decker ***@***.***> wrote:
Thanks for reporting this @2pac1 <https://github.com/2pac1>, I noticed
that the build for that image is really old, so I fixed the Dockerfile and
re-built the image, could you try again?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#508 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AhbzMKm1GDEk6kPWJcINCaZIf1SgkiS1ks5tG3SogaJpZM4RRalE>
.
|
|
i can provide VPS info if needed
…On Wed, Jan 3, 2018 at 2:21 PM, MINO ***@***.***> wrote:
any chance you could help?
tnx a ton
On Wed, Jan 3, 2018 at 1:38 PM, Christian Decker ***@***.***
> wrote:
> Thanks for reporting this @2pac1 <https://github.com/2pac1>, I noticed
> that the build for that image is really old, so I fixed the Dockerfile and
> re-built the image, could you try again?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#508 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AhbzMKm1GDEk6kPWJcINCaZIf1SgkiS1ks5tG3SogaJpZM4RRalE>
> .
>
|
You need Bitcoin 0.15 or above. You have 0.14.2. |
|
How to update it?
…On Wed, Jan 3, 2018 at 4:45 PM, Benoît Verret ***@***.***> wrote:
"subversion": "/Satoshi:0.14.2/",
You need Bitcoin 0.15 or above. You have 0.14.2.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#508 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AhbzMNHqiQTt_vV03H9vVrI2qA7EiTrNks5tG6CCgaJpZM4RRalE>
.
|
|
You can download it here https://bitcoin.org/en/download |
|
yes I know that, but I am following https://interfect.github.io/#!/posts/009-Ride-the-Lightning.md guide and I am not sure how to update it if I am pulling it from a docker container |
|
Sorry. I don't know how they make their images. |
|
trying now with forked project that has latest btc wallet
and will verify again in old VPS as I suspect maybe it was down to port not being opened |
|
I fixed it with a fork that gets latest
|
|
i am at the final step when I run this
i get "failed: WIRE_FINAL_INCORRECT_CLTV_EXPIRY (reply from remote)" please help, I am 99% done, I just want to send payment |
|
You could generate an invoice and pay it using the If not, try to increae the delay in the route and see what happens :-) |
|
I figured out pay, and it worked! SUCCESS! Although C implementation is total pain |
|
Glad it worked, let me know if you need anything else. I'll close this issue for now, feel free to reopen should the problem re-emerge. |
|
one more question: how do I access wallet.dat as its within the docker? and how do I withdraw? I tried doing it with and I got transaction that has no change and that got stuck https://blockchain.info/address/17mUogNA1ozaM1y9pYmC94N8E6L7gQAk9h tnx |
|
There are two ways of retrieving the wallet.dat file from a docker image:
As for the withdrawal transaction, it's using testnet fees (we do not encourage running lightning on mainnet just yet), so you'll have to wait for the transaction to confirm. |
|
now I run: docker run --rm --name bitcoind_mainnet -v /scratch/bitcoin/mainnet/bitcoind:/data -p 8333:8333 -p 9735:9735 idiogenes/bitcoin:latest and you suggest I run: docker run --rm --name bitcoind_mainnet -v /scratch/bitcoin/mainnet/bitcoind:/data -v .bitcoin -p 8333:8333 -p 9735:9735 idiogenes/bitcoin:latest Hope you can help regarding fees, I saw it was using: But I see no change address and there is "Unable to decode output address " error showing on blockchain info Tnx in advance |
|
Do not run with I see that you are running a modified |
|
how should I then get to the wallet, I am not sure I understand, as before mounting docker there is nothing, after mounting it I cannot access the command line in the same window as its running p.s. you suggest instead of to run without --rm like this? |
|
was able to access it by running |
|
Great, you had me worried for a second there 😉 |
|
Tnx @cdecker |
|
what I dont get now, the transaction I did with my old node that I had error in the title, I wanted to transfer something out: I now see with -help command |
|
The change address is an address owned by the lightning client, since you are transferring from the lightning wallet to somewhere else, that's the correct way of keeping the change in the builtin wallet.
|
|
tnx so what you are saying when fees drop, and 38.044 sat/B gets into block, this should confirm? If it does not drop out before that can you set fees manually on mainnet currently? |
|
You need to enable the advanced view in bc.i to see bech32 style addresses for p2wpkh outputs which is what lightningd uses internally. |
|
did not even see that advanced mode, tnx |
That is currently not exposed to the end-user, since it's a great way to get your funds stuck. Sadly the automatic way is also not guaranteed to work as exemplified in this case. You could attempt to bump the fee using CPFP, by spending the transaction output and attaching a large enough fee to pay for both transactions though for 0.15 USD I doubt that's a sensible thing to do. |
|
no no I was just asking as an example |
|
any way for auto mode to spit out fees it would use if you want to transfer out of lightning to btc address? so you check if they are all right tnx man! |
|
in this particular example https://blockchain.info/tx/c6bed9d9b61abca39dd6084f02e7922d2d3bc79a6fabff440191eb90a77e5e16?show_adv=true right? |
|
To sweep all funds from the c-lightning daemon into another wallet you can use |
Hello guys,
I am following this guide for LN for mainnet: https://interfect.github.io/#!/posts/009-Ride-the-Lightning.md
And I had it working and was able to connect to a yalls mainnet node, and after that I was changing password for /scratch/bitcoin/mainnet/bitcoind/bitcoin.conf and tomorrow it didnt want to work.
I reverted the pass to default one, and even deleted the file (and it got recreated after that).
I am getting Fatal signal 11 when trying to connect. And I do not any other mainnet not to try.
These are the logs.
What is going on and how do I solve this, as It was able to connect to yalls node before.
Thank you.
The text was updated successfully, but these errors were encountered: