Skip to content

Owning subdaemon lightning_openingd died #1829

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jogc opened this issue Aug 12, 2018 · 7 comments
Closed

Owning subdaemon lightning_openingd died #1829

jogc opened this issue Aug 12, 2018 · 7 comments

Comments

@jogc
Copy link

jogc commented Aug 12, 2018

Repeatedly get this error message when I'm trying to open a channel to a certain node

$ lightning-cli connect 024655b768ef40951b20053a5c4b951606d4d86085d51238f2c67c7dec29c792ca@88.98.213.235:9735
{
  "id": "024655b768ef40951b20053a5c4b951606d4d86085d51238f2c67c7dec29c792ca"
}
$ lightning-cli fundchannel 024655b768ef40951b20053a5c4b951606d4d86085d51238f2c67c7dec29c792ca 500000
{ "code" : -1, "message" : "Owning subdaemon lightning_openingd died (62208)" }

Log snippets:

Aug 12 16:03:47 x lightningd[14204]: 2018-08-12T08:03:47.996Z lightning_gossipd(14228): Received channel_update for channel 525199:804:0(0) now ACTIVE was ACTIVE (from subdaemon)
Aug 12 16:03:54 x lightningd[14204]: 2018-08-12T08:03:54.647Z lightning_gossipd(14228): Received channel_update for channel 532792:100:1(1) now ACTIVE was DISABLED (from subdaemon)
Aug 12 16:03:57 x lightningd[14204]: 2018-08-12T08:03:57.286Z lightningd(14204): lightning_openingd-024655b768ef40951b20053a5c4b951606d4d86085d51238f2c67c7dec29c792ca chan #27: Failed reading header: Connection reset by peer
Aug 12 16:03:57 x lightningd[14204]: 2018-08-12T08:03:57.286Z lightningd(14204): lightning_openingd-024655b768ef40951b20053a5c4b951606d4d86085d51238f2c67c7dec29c792ca chan #27: Peer connection lost
Aug 12 16:03:57 x lightningd[14204]: 2018-08-12T08:03:57.286Z lightningd(14204): lightning_openingd-024655b768ef40951b20053a5c4b951606d4d86085d51238f2c67c7dec29c792ca chan #27: Status closed, but not exited. Killing
Aug 12 16:03:57 x lightningd[14204]: 2018-08-12T08:03:57.287Z lightningd(14204): 024655b768ef40951b20053a5c4b951606d4d86085d51238f2c67c7dec29c792ca chan #27: Owning subdaemon lightning_openingd died (62208)
Aug 12 16:03:57 x lightningd[14204]: 2018-08-12T08:03:57.287Z lightningd(14204):jcon fd 19: Failing fundchannel: Owning subdaemon lightning_openingd died (62208)
Aug 12 16:03:57 x lightningd[14204]: 2018-08-12T08:03:57.330Z lightning_connectd(14227): Forgetting remote peer 024655b768ef40951b20053a5c4b951606d4d86085d51238f2c67c7dec29c792ca
Aug 12 16:04:10 x lightningd[14204]: 2018-08-12T08:04:10.959Z lightningd(14204): ... feerate estimate for Normal hit floor 253
Aug 12 16:04:10 x lightningd[14204]: 2018-08-12T08:04:10.959Z lightningd(14204): ... feerate estimate for Slow hit floor 253
Aug 12 16:04:14 x lightningd[14204]: 2018-08-12T08:04:14.471Z lightning_gossipd(14228): Received channel_update for channel 525199:804:0(0) now ACTIVE was ACTIVE (from subdaemon)
Aug 12 16:04:28 x lightningd[14204]: 2018-08-12T08:04:28.587Z lightning_gossipd(14228): Received channel_update for channel 525199:804:0(0) now ACTIVE was ACTIVE (from subdaemon)

...

Aug 12 16:08:47 x lightningd[14204]: 2018-08-12T08:08:47.994Z lightning_gossipd(14228): Received channel_update for channel 525199:804:0(0) now ACTIVE was ACTIVE (from subdaemon)
Aug 12 16:08:47 x lightningd[14204]: 2018-08-12T08:08:47.997Z lightning_gossipd(14228): Received channel_update for channel 534504:453:0(0) now ACTIVE was ACTIVE (from subdaemon)
Aug 12 16:08:48 x lightningd[14204]: 2018-08-12T08:08:48.000Z lightning_gossipd(14228): Received channel_update for channel 534505:741:0(0) now ACTIVE was ACTIVE (from subdaemon)
Aug 12 16:08:48 x lightningd[14204]: 2018-08-12T08:08:48.001Z lightning_gossipd(14228): Received channel_update for channel 535591:1722:1(0) now ACTIVE was ACTIVE (from subdaemon)
Aug 12 16:08:48 x lightningd[14204]: 2018-08-12T08:08:48.002Z lightning_gossipd(14228): Bad gossip repeated timestamp for 534826:1197:0(0): 010269735937e8cf4e42700ec9048c35331fe23c004d7879da76b938025482f083f40af00145a14f02b0edc64bbff5da8b4194d24087fa763d9c9694152c0e4888ad6fe28c0ab6f1b372c1a6a246ae63f74f931e8365e15a089c68d619000000000008292a0004ad00005b6feae000000080000000000000ced200001a8d00000040 then 01020f1219889f243be813b681858de928af3dc6aba20fc071d83a603e0c6c9b582e33c7fed3536271325c8980f0282850ee421be8b1368c3d206e0e5bed3fc396cb6fe28c0ab6f1b372c1a6a246ae63f74f931e8365e15a089c68d619000000000008292a0004ad00005b6feae000000118000000000000c2d700001b340000003f
Aug 12 16:08:50 x lightningd[14204]: 2018-08-12T08:08:50.303Z lightningd(14204): lightning_openingd-024655b768ef40951b20053a5c4b951606d4d86085d51238f2c67c7dec29c792ca chan #28: Failed reading header: Connection reset by peer
Aug 12 16:08:50 x lightningd[14204]: 2018-08-12T08:08:50.304Z lightningd(14204): lightning_openingd-024655b768ef40951b20053a5c4b951606d4d86085d51238f2c67c7dec29c792ca chan #28: Peer connection lost
Aug 12 16:08:50 x lightningd[14204]: 2018-08-12T08:08:50.304Z lightningd(14204): lightning_openingd-024655b768ef40951b20053a5c4b951606d4d86085d51238f2c67c7dec29c792ca chan #28: Status closed, but not exited. Killing
Aug 12 16:08:50 x lightningd[14204]: 2018-08-12T08:08:50.304Z lightningd(14204): 024655b768ef40951b20053a5c4b951606d4d86085d51238f2c67c7dec29c792ca chan #28: Owning subdaemon lightning_openingd died (62208)
Aug 12 16:08:50 x lightningd[14204]: 2018-08-12T08:08:50.304Z lightningd(14204):jcon fd 19: Failing fundchannel: Owning subdaemon lightning_openingd died (62208)
Aug 12 16:08:50 x lightningd[14204]: 2018-08-12T08:08:50.355Z lightning_connectd(14227): Forgetting remote peer 024655b768ef40951b20053a5c4b951606d4d86085d51238f2c67c7dec29c792ca
Aug 12 16:08:51 x lightningd[14204]: 2018-08-12T08:08:51.861Z lightning_gossipd(14228): Received channel_update for channel 531994:918:0(1) now ACTIVE was ACTIVE (from subdaemon)
@rustyrussell
Copy link
Contributor

They are dropping the connection with you. It would be nicer if they sent an error, and yes, we should print a more informative message anyway!

@cdecker
Copy link
Member

cdecker commented Aug 21, 2018

The remote end is satoshis.place, so we could potentially ask for their log entries relating to your node. Could you share the output of getinfo?

@jogc
Copy link
Author

jogc commented Aug 21, 2018

Yeah no problem

{
"id": "032b98bbdd48ca00300a627355900521c9302e6df363186a74e43213bcd3f781b2",
"alias": "lnsms.world",
"color": "e95420",
"address": [
{
"type": "ipv4",
"address": "37.59.50.48",
"port": 19248
}
],
"binding": [
{
"type": "ipv4",
"address": "37.59.50.48",
"port": 19248
}
],
"version": "v0.6-195-gfbbc589",
"blockheight": 537863,
"network": "bitcoin"
}

@LightningK0ala
Copy link

Hi @jogc, my node (satoshis.place) was unstable around about that time (10th - 14th August).
It should be working now, could you try again?

@jogc
Copy link
Author

jogc commented Aug 23, 2018

Yep worked much better now. Just opened a 500000 sat channel. I'll close this issue, but yeah it would be nice if the error message was less scary. I thought c-lightning had crashed somehow.

@jogc jogc closed this as completed Aug 23, 2018
@cdecker
Copy link
Member

cdecker commented Aug 24, 2018

Agreed on the scary nature of the message, will do a pass to fix the wording on some of these messages.

@mloop1
Copy link

mloop1 commented Jul 6, 2019

Agreed on the scary nature of the message, will do a pass to fix the wording on some of these messages.

It seems this message is still there, I see it in my logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants