-
Notifications
You must be signed in to change notification settings - Fork 216
Unable to start server: unable to refresh backup file: unable to update multi backup: Access Denied #3591
Comments
👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. |
Hi, can you tell me what version of Zap you were upgrading from please? Thanks. Also, if you quit and restart the app do you get the same problem? Thanks |
Hi! Yes - Upgraded from the previous version 0.6.2-Beta and I still get the same message when I quit and restart the app. |
Interesting. Well, this error is coming directly from lnd (which was upgraded from 0.8 to 0.10 in this release). My first thought is that lnd's upgrade process didn't fully complete for some reason though I've not seen it happen before. Can you try downloading 0.6.2 again and see if that still runs? |
Going back to ver 0.6.2-Beta gives this error - Lnd has unexpectedly quit! |
Re-installed 0.7.0 and still getting the same fail message. |
Could you update to 0.7.0 again, start zap, and then review your lnd logs which you can find at |
OK - This is the latest log entry - 2020-07-11 23:10:05.545 [INF] CNCT: ChannelArbitrator(d2e3373182d1f8f33aa8b7c56aad3999f367eff29edf570ec2cf6f6baef2afae:0): starting state=StateDefault, trigger=chainTrigger, triggerHeight=638831 2020-07-11 23:10:05.545 [DBG] CNCT: ChannelArbitrator(d2e3373182d1f8f33aa8b7c56aad3999f367eff29edf570ec2cf6f6baef2afae:0): new block (height=638831) examining active HTLC's 2020-07-11 23:10:05.821 [DBG] LNWL: ChannelPoint(d13d5701ec25430274c77b8ad0cd8f1aca1fcf0997197cd6256958a673c205cc:0): starting local commitment: (*lnwallet.commitment)(0xc0039c0000)({ 2020-07-11 23:10:05.822 [INF] CHFT: Adding 2 channels to event store 2020-07-11 23:10:05.823 [DBG] LNWL: ChannelPoint(d2e3373182d1f8f33aa8b7c56aad3999f367eff29edf570ec2cf6f6baef2afae:0): Restoring 0 dangling remote updates 2020-07-11 23:10:05.823 [DBG] FNDG: ChannelPoint(d2e3373182d1f8f33aa8b7c56aad3999f367eff29edf570ec2cf6f6baef2afae:0) with chan_id=aeaff2ae6b6fcfc20e57df9ef2ef67f39939ad6ac5b7a83af3f8d1823137e3d2 not found in opening database, assuming already announced to the network |
Hmm, I thought that Windows file locking problem was fixed in lnd.
|
What Windows file locking problem are you referring to? I've not heard of this before. I'm not so familiar with Windows but from the logs it looks like a file permissions issue. Can you check the permissions on that file and ensure that it is readable by lnd? It sounds related to this recent lnd change lightningnetwork/lnd#4379 |
I seem to remember Lightning Labs Lightning App having a similar issue. |
Any fix or workaround for this issue yet? |
To me this sounds like either a file permissions issue on your machine, or a bug in lnd. Did you check the file permissions? You could try moving that |
I was running ver 0.6.2 with no problem. I didn't change any permissions on my system (why would I?). I just upgraded to ver 0.7.0 and I got this error. |
The path to the file that lnd is having trouble reading is detailed in your error message:
|
OK - found it and moved it. |
Great!
After moving the file and starting up lnd again I expect lnd will have recreated the file for you. Can you check if the file has been recreated at its original location?
It's unlikely. I've actually never seen a case of this needing to be done. I think it relates to the change in lnd that I referenced earlier in this thread. |
Yes - the backup file has been recreated. Thanks for your help. |
Good stuff. Thanks for confirming. |
Fix in LND merged. |
Description
<Just!--- Provide a more detailed introduction to the issue itself, and why you consider it to be a bug -->
Just upgraded to Ver 0.7.0-Beta
Got this error on startup:-
Lnd has unexpectedly quit!
Error code:
1
Error signal:
Unknown
Error message:
Unknown
Expected Behavior
Zap wallet to start normally.
Actual Behavior
Zap wallet failed to start.
Possible Fix
Steps to Reproduce
Context
Your Environment
The text was updated successfully, but these errors were encountered: