[01:41:11] I guess I'll try bootstrapping again using the daemon and see what happens when I get home [01:47:21] I don't think I had set zram on mine [03:23:18] @pclark36 If you installed it, it produces a swap = 50% of native RAM by default. No setup required. [03:24:19] Use the command 'free -m' in a terminal window to check. [04:25:49] @aguycalled if you have a moment, do you mind checking if you can replicate this https://github.com/NAVCoin/navcoin-core/issues/415 [06:16:59] @BuckoNZ you're right, I got swap. I'm gonna try the bootstrap again [06:20:54] sorry for late response, been a shit of a day, sunroof in my car exploded while I was going down the highway [06:21:18] gotta love that in the middle of winter in alaska [06:42:28] Sounds exciting, @pclark36 ! [07:38:50] So still stuck on 2783023 [07:39:21] complete .navcoin directory delete, wallet.dat included, still stuck [08:20:37] Is that with or without swap [08:35:02] having a look @mc290 [08:37:06] I'm running a similar test now. [16:40:16] Mine was with swap [17:21:15] So, I uninstalled Zram, deleted the block and chainstate folders and rebooted the XU4. After I logged back in, I fired up NavCore, boot strapped the blockchain and let it catch up over night. On checking this morning, there was some sort of NavCore non-responsive error. I rebooted XU4 again and started up NavCore. It's still several weeks behind, so I let it catch up again... watch this space... [18:31:52] Ok, now I'm getting an 'Error reading from database' message at block 2782098. I think I'm going to have to do a fresh XU4 build. [20:43:09] @pclark36 If you want to, you can remember be Zram and try again, use this command: [20:43:12] apt-get remove --purge zram-config [22:19:16] @aguycalled @Matt (Dev) https://github.com/NAVCoin/navcoin-core/pull/413 can we get another review here if you have a moment? One of the new rpc tests failed randomly and I have logged it in a separate isuse [22:19:58] I will look at this after the meeting [23:29:41] @BuckoNZ I'll try that tonight, don't have remote access to my odroid [23:39:37] Neither do I