search

lightninglabs / lightning-terminal

Lightning Terminal: Your Home for Lightning Liquidity
MIT License
508 stars 90 forks source link

unable to start account manager: unable to resume account #379

Closed diegokolling closed 2 years ago

diegokolling commented 2 years ago

Hey guys!

I have a Pool account open already with some loans made. I use the Umbrel 4.18 Lightning Terminal app to manage it.

Once more, I cant access it due to what seem to be a fragil scheme that cant handle some internet glitches.

Last time I lost access to it was through a Tor glitch, reported and solved here: https://github.com/lightninglabs/lightning-terminal/issues/372

Now I had an unfurtunate restart due my Node being taken out of energy by my painter.

And boom: no more access to LiT.

Here are the Logs:

lightning-terminal

web_1 | 2022-06-14 05:55:34.026 [INF] STORE: Checking for schema update: latest_version=4, db_version=4 web_1 | 2022-06-14 05:55:34.218 [INF] POOL: Version: 0.5.6-alpha commit=v0.5.6-alpha-lnd-14 web_1 | 2022-06-14 05:55:34.218 [INF] LOOPD: Waiting for updates web_1 | 2022-06-14 05:55:34.218 [INF] LOOPD: Starting liquidity manager web_1 | 2022-06-14 05:55:34.218 [INF] LOOPD: Starting swap client web_1 | 2022-06-14 05:55:34.219 [INF] LOOP: Connected to lnd node 'dbnk' with pubkey 03d76e15709c57225560af75576b71c4d72dbac0dffaaba5ab8cc94e17ff8e708f (version v0.14.2-beta, build tags 'autopilotrpc,signrpc,walletrpc,chainrpc,invoicesrpc,watchtowerrpc,monitoring,kvdb_postgres,kvdb_etcd') web_1 | 2022-06-14 05:55:34.220 [INF] LOOP: Wait for first block ntfn web_1 | 2022-06-14 05:55:34.224 [INF] LOOP: Starting event loop at height 740717 web_1 | 2022-06-14 05:55:34.420 [INF] POOL: Auction server address: pool.lightning.finance:12010 web_1 | 2022-06-14 05:55:34.424 [INF] CLDB: Checking for schema update: latest_version=1, db_version=1 web_1 | 2022-06-14 05:55:34.425 [INF] RPCS: Starting trader server web_1 | 2022-06-14 05:55:34.553 [INF] RPCS: Connected to lnd node dbnk with pubkey 03d76e15709c57225560af75576b71c4d72dbac0dffaaba5ab8cc94e17ff8e708f web_1 | 2022-06-14 05:55:34.579 [INF] ACCT: Watching spend of 5e595a1dc290e434679f4219da8061e4ab386081a6eecc3a504d2255e390caf1:3 for account 0365a0db0217ac0967309a41d0b8a921d1d9c540b4fc2cd3dbff9429765b23bf14 web_1 | 2022-06-14 05:55:35.642 [INF] AUCT: Successfully connected to auction server web_1 | 2022-06-14 05:55:35.889 [INF] AUCT: Shutting down auctioneer client web_1 | unable to start account manager: unable to resume account 0365a0db0217ac0967309a41d0b8a921d1d9c540b4fc2cd3dbff9429765b23bf14: unable to subscribe for account updates: checking pending batch failed: error removing pending batch artifacts: error abandoning channels from previous pending batch: error locating channel outpoint: no channel output found in batch tx for matched order 770692b0522790204c91c8b667762cea928ef45094a074e83bd04a3780a9eafc web_1 | 2022-06-14 05:55:35.890 [ERR] LITD: Could not start subservers: unable to start account manager: unable to resume account 0365a0db0217ac0967309a41d0b8a921d1d9c540b4fc2cd3dbff9429765b23bf14: unable to subscribe for account updates: checking pending batch failed: error removing pending batch artifacts: error abandoning channels from previous pending batch: error locating channel outpoint: no channel output found in batch tx for matched order 770692b0522790204c91c8b667762cea928ef45094a074e83bd04a3780a9eafc web_1 | 2022-06-14 05:55:35.890 [INF] LOOPD: Stopping gRPC server web_1 | 2022-06-14 05:55:35.890 [INF] LOOPD: Stopping REST server web_1 | 2022-06-14 05:55:35.891 [INF] LOOPD: Liquidity manager stopped web_1 | 2022-06-14 05:55:35.891 [ERR] ACCT: Unable to determine spend for account 0365a0db0217ac0967309a41d0b8a921d1d9c540b4fc2cd3dbff9429765b23bf14: rpc error: code = Unavailable desc = error reading from server: read tcp 10.21.21.17:36304->10.21.21.9:10009: use of closed network connection web_1 | 2022-06-14 05:55:35.891 [ERR] ACCT: Unable to receive block notification: rpc error: code = Unavailable desc = error reading from server: read tcp 10.21.21.17:36304->10.21.21.9:10009: use of closed network connection web_1 | 2022-06-14 05:55:35.891 [INF] LOOP: Swap client terminating web_1 | 2022-06-14 05:55:35.891 [INF] LOOP: Swap client terminated web_1 | 2022-06-14 05:55:35.891 [INF] LOOPD: Swap client stopped web_1 | 2022-06-14 05:55:35.891 [INF] LOOPD: Daemon exited web_1 | 2022-06-14 05:55:35.891 [ERR] LNDC: Error closing lnd connection: rpc error: code = Canceled desc = grpc: the client connection is closing web_1 | 2022-06-14 05:55:35.892 [INF] SGNL: Received shutdown request. web_1 | 2022-06-14 05:55:35.892 [INF] SGNL: Shutting down... web_1 | 2022-06-14 05:55:35.892 [INF] SGNL: Gracefully shutting down.

Could you guys help me, please? Thanks!

guggero commented 2 years ago

Not properly shutting down a Lightning node can have very dire consequences. I would place it in a more secure location and think about an UPS if you put serious money on the node.

That said, the recovery process in this case should be the same as in the previous issue you opened.

diegokolling commented 2 years ago

Node is perfectly fine! 100% functional. The only thing not coming back online is LiT app.

levmi commented 2 years ago

Diego, were you able to go through the recovery process mentioned by Jamal in #372 that is likely the best recovery path in this case as well.

diegokolling commented 2 years ago

Oh that would be great! If Jamal confirms that, than it’s done.

Is it just to follow through the beginning?

Em ter., 14 de jun. de 2022 às 12:01, levmi @.***> escreveu:

Diego, were you able to go through the recovery process mentioned by Jamal in #372 https://github.com/lightninglabs/lightning-terminal/issues/372 that is likely the best recovery path in this case as well.

— Reply to this email directly, view it on GitHub https://github.com/lightninglabs/lightning-terminal/issues/379#issuecomment-1155313085, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACSDAYSHFTGOWWDMDJEYADDVPCNC3ANCNFSM5YWOO5QQ . You are receiving this because you authored the thread.Message ID: @.***>

-- Enviado do Gmail para celular

diegokolling commented 2 years ago

Jesus, now that I saw that its you, Michael Levin! I was responding through e-mail! Sorry. So, is just to re-do the steps of 372?

levmi commented 2 years ago

Yep, try to go through the steps from that issue that Jamal recommended that worked for you last time around. Similar issue so the fix should be the same.

diegokolling commented 2 years ago

I have access to Pool again but, Im confused: my 3 accepted orders dont show up there anymore, although the channels are still open.

Questions: are they still up to 2016 blocks contract stablished initially? The remaining, un matched offers went back to my Pool account.

But I dont see my "earnings" anymore, at the top right corner.

Did I loose them? Or they were added to my Pool account?

Or they will be added to at the closing of the channels that were opened?

Thank you one more time guys.

guggero commented 2 years ago

The channels and their contracts remain intact, your earnings are still in your account (that's where they accumulate). It's just the local summary information that is missing because you had to remove your pool.db for the recovery.

So you can just continue normally.

Going to close the issue as there initial problem is solved.

diegokolling commented 2 years ago

Oh, OK Oliver! Is there anywhere else I can retrieve this information?

Em qua., 15 de jun. de 2022 às 04:57, Oliver Gugger < @.***> escreveu:

The channels and their contracts remain intact, your earnings are still in your account (that's where they accumulate). It's just the local summary information that is missing because you had to remove your pool.db for the recovery.

So you can just continue normally.

Going to close the issue as there initial problem is solved.

— Reply to this email directly, view it on GitHub https://github.com/lightninglabs/lightning-terminal/issues/379#issuecomment-1156124342, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACSDAYQ4RPDCYWQFU5BVG6DVPGEEZANCNFSM5YWOO5QQ . You are receiving this because you authored the thread.Message ID: @.***>

-- Enviado do Gmail para celular

diegokolling commented 2 years ago

On that point: I tried to use Web version to submit an ask order, but failed. Heres the print:

RPC error: code = uknown desk = lnd macaroon validation failed : rpc error: code = invalid argument desc = permission denied

2022-06-15

After that, I used the Umbrel app and it all went well. I can see the submitted ask order in both places.

What can it be?

levmi commented 2 years ago

When you created the LNC session to connect to Terminal Web, did you create an Admin session or a Read only session?

diegokolling commented 2 years ago

Hmm I dont really know, I copied the default one, that was already created.

When on read only it gives me this message?

levmi commented 2 years ago

It's a possibility, but it sounds like that isn't the case if you used the default. Can you take other actions throughout the Terminal experience? Changing fees on channels, performing a Loop? Want to see if it's Pool specific.