Hey, any thoughts why this happened? Almost one month everything was OK, yesterday I updated software to v0.0.6 and this morning I found this error in the log. Do I understand right, that when wallet restarted this morning, it became locked again? Any suggestions how to handle such errors? Maybe it worth to parse log file each minute and execute Code: dcrctl --wallet walletpassphrase pass 0 if new errors were found in the log file. Code: 05:56:38 2016-03-06 [ERR] RPCS: Websocket receive error from [::1]:55505: websocket: close 1006 unexpected EOF 05:56:38 2016-03-06 [ERR] CHNS: Timeout waiting for session RPC 05:56:38 2016-03-06 [INF] RPCS: Disconnected websocket client [::1]:55505 05:56:38 2016-03-06 [ERR] WLLT: Failed to get next to use address for address pool external: the client has been shutdown 05:56:38 2016-03-06 [INF] RPCS: New websocket client [::1]:45541 05:56:38 2016-03-06 [INF] DCRW: Attempting RPC client connection to localhost:9109 05:56:38 2016-03-06 [INF] CHNS: Established connection to RPC server localhost:9109 05:56:38 2016-03-06 [INF] WLLT: Beginning a rescan of active addresses using the daemon. This may take a while. 05:56:38 2016-03-06 [INF] WLLT: Stake mining is enabled. Votebits: 1, minimum wallet balance 0.001 05:56:38 2016-03-06 [INF] WLLT: PLEASE ENSURE YOUR WALLET IS UNLOCKED SO IT MAY VOTE ON BLOCKS AND RECEIVE STAKE REWARDS
Wallet is laways locked when it shuts down. That is what i have seen with every wallet i have used. People are using task schedular & bash scripts to unlock it everytime they start the wallet.
Yes, but there is difference between situations when you restart wallet yourself and when wallet restarted because some error in decred software occurred. I don't want to leave my wallet for 5 months of stake mining, and then discover that it's been restarted and locked 3 months ago.
In any case unlocking on restart is the thing to do. Right? More worrisome will be corruption of data if wallet was closed with error. I am sure you have backups for that.
This was a bug introduced after the syncing of code to btcwallet for the gRPC introduction. It should be patched in the next release.
version 0.0.7, linux x64 binary - only one error : ==daemon.log=== 23:00:26 2016-03-12 [INF] BMGR: Processed 1 block in the last 1m9s (1 transaction, height 9840, 2016-03-12 23:00:18 +0000 UTC) 23:03:26 2016-03-12 [INF] BMGR: Processed 1 block in the last 3m0.11s (1 transaction, height 9841, 2016-03-12 23:02:37 +0000 UTC) 23:04:26 2016-03-12 [ERR] RPCS: Websocket receive error from 127.0.0.1:56142: read tcp4 127.0.0.1:9109->127.0.0.1:56142: read: connection reset by peer 23:04:26 2016-03-12 [INF] RPCS: Disconnected websocket client 127.0.0.1:56142 23:04:26 2016-03-12 [INF] RPCS: New websocket client 127.0.0.1:60370 23:04:27 2016-03-12 [INF] RPCS: Beginning rescan for xxxxx addresses 23:04:27 2016-03-12 [INF] RPCS: Finished rescan 23:10:07 2016-03-12 [INF] BMGR: Processed 1 block in the last 6m40.88s (12 transactions, height 9842, 2016-03-12 23:10:03 +0000 UTC) ===wallet.log=== 22:59:17 2016-03-12 [INF] WLLT: Connecting block 0000000000002710b458ddfdaab63c053662eb907226da69d03ac326b5055341, height 9839 23:00:26 2016-03-12 [INF] WLLT: Connecting block 00000000000017adfccddd10d8782f015005a0246de2c0772b12717fb2b7906c, height 9840 23:04:26 2016-03-12 [ERR] CHNS: Timeout waiting for session RPC 23:04:26 2016-03-12 [ERR] WLLT: Failed to get next to use address for address pool external: the client has been shutdown 23:04:26 2016-03-12 [INF] DCRW: Attempting RPC client connection to localhost:9109 23:04:26 2016-03-12 [INF] CHNS: Established connection to RPC server localhost:9109 23:04:26 2016-03-12 [INF] WLLT: Beginning a rescan of active addresses using the daemon. This may take a while. 23:04:26 2016-03-12 [INF] WLLT: Stake mining is enabled. Votebits: 1, minimum wallet balance 0 23:04:26 2016-03-12 [INF] WLLT: PLEASE ENSURE YOUR WALLET IS UNLOCKED SO IT MAY VOTE ON BLOCKS AND RECEIVE STAKE REWARDS