Contracts and accounts are disappeared

[ValeryDubrava]

Before filing a new issue, please provide the following information.

I'm running:

• Which Parity version?: 1.8.6 beta-2d051e4-20180109
• Which operating system?: Linux Debian 7
• How installed?: via deb package
• Are you fully synchronized?: yes
• Which network are you connected to?: ropsten
• Did you try to restart the node?: yes

Contracts and Accounts are disappeared after restart the node. In web3 there is all accounts (web3.eth.accounts = [{...},...]).
I've use ssh port forwarding: ssh -L 8545:127.0.0.1:8545 -L 8546:127.0.0.1:8546 -L 8180:127.0.0.1:8180 user@host
I've specified command line arguments: parity daemon ./parity.pid --db-compaction ssd --cache-size 1024 --force-ui --jsonrpc-cors all --identity myid --allow-ips public --log-file parity.log --nat extip:1.2.3.4 --chain ropsten --jsonrpc-apis all --pruning=archive --reserved-peers ropstenpeers.txt

Also, I've checked the directory with keys - all keys still there. It looks like some UI bug.

[ValeryDubrava]

Screencast from the network tab of the dev tool.

[ValeryDubrava]

Startup log:

2018-01-19 12:07:30  Starting Parity/v1.8.6-beta-2d051e4-20180109/x86_64-linux-gnu/rustc1.22.1
2018-01-19 12:07:30  Keys path /root/.local/share/io.parity.ethereum/keys/Ropsten
2018-01-19 12:07:30  DB path /root/.local/share/io.parity.ethereum/chains/test/db/ae90623718e47d66
2018-01-19 12:07:30  Path to dapps /root/.local/share/io.parity.ethereum/dapps
2018-01-19 12:07:30  State DB configuration: archive
2018-01-19 12:07:30  Operating mode: active
2018-01-19 12:07:30  Warning: Warp Sync is disabled because of non-default pruning mode.
2018-01-19 12:07:30  Configured for Ropsten using Ethash engine
2018-01-19 12:07:30  Updated conversion rate to Ξ1 = US$1058.32 (112487350 wei/gas)
2018-01-19 12:07:35  Public node URL: enode://<removed>:30303
2018-01-19 12:08:06     0/25 peers    715 KiB chain  222 KiB db  0 bytes queue 448 bytes sync  RPC:  2 conn,  4 req/s, 18489 µs
2018-01-19 12:08:21  Imported #2483679 0cef…df68 (6 txs, 0.22 Mgas, 628.58 ms, 1.40 KiB) + another 1 block(s) containing 26 tx(s)
2018-01-19 12:08:26  Error sending a subscription update: ConnectionClosed
2018-01-19 12:08:27  Cannot send notification: SendError("...")

[ValeryDubrava]

Looks like I've found the right error:

[ValeryDubrava]

I've found the root of the problem. File with key contains meta json as string. And that json was corrupted somehow... I do not know, how it happend. But it became corrupted after parity restart. Please, check it twice, because it looks like very critical issue, if parity corrupts key files on shutdown.

[butterstuff]

i have seen this issue as well - i wasnt sure it was a bug, so i just reimported a backed up key... but that is the same issue I had

[beaugunderson]

Same issue here; diffed a backup of my keys to see which was the issue, here's the corruption in the "meta" key:

"meta":"{\"description\":\"\",\"passwordHi\",\"passwordHint\":\"\",\"tags\":[],\"timestamp\":1516865678141}"

I changed the name of this key recently.