[16:41:49] <navcoin-bot> <salmonskinroll> i ran several verifychain 4 XXX on mainnet with the PR and everything seems fine, I will jump back to testing DAO this week. Last time everything was good, I think it can use some stress testing like what we are doing now on testnet as well
[16:43:34] <navcoin-bot> <aguycalled> the stress test during the weekend ran fine, no forks or major issues besides some nodes lagging behind in blocks during the test because of network congestion (blocks were taking too long to propagate) or a node requiring manual intervention to recover service (restart)
[16:44:37] <navcoin-bot> <salmonskinroll> why would block take long to propagate?
[16:45:35] <navcoin-bot> <aguycalled> https://cdn.discordapp.com/attachments/416000318149754881/651086568274264074/NavCoin_Development_Report_-_Week_2.pdf
[16:46:13] <navcoin-bot> <aguycalled> there were blocks with ~5000 votes, which require time to validate
[16:49:00] <navcoin-bot> <salmonskinroll> wow, lol, we're stress testing it not breaking it man 😉 i was using the gitian build on the testnet but im doing a self build now and will get online soon
[18:18:28] <navcoin-bot> <aguycalled> @salmonskinroll could you add your verifychain tests in the pull request as a comment?
[18:33:30] <navcoin-bot> <salmonskinroll> Sure
[20:41:17] <navcoin-bot> <salmonskinroll> @aguycalled have you ever tried running verifychain 4 0 on mainnet?
[20:41:25] <navcoin-bot> <salmonskinroll> just wondering how long it took you
[20:41:59] <navcoin-bot> <aguycalled> yes took quite some time
[20:42:18] <navcoin-bot> <aguycalled> i cant remember how long
[20:42:24] <navcoin-bot> <aguycalled> but was slow
[20:54:46] <navcoin-bot> <salmonskinroll> i have 6 nodes that can be set up to run DAO none stop, maybe we can use the script you're running on testnet now to stress test DAO? what do you think?
[20:55:21] <navcoin-bot> <salmonskinroll> but i guess the priority now is to get current PRs merged and released
[22:20:47] <navcoin-bot> <salmonskinroll> just did and verifychain 4 0 and it's saying error: couldn't connect to server, but i think it's still running. is it normal?
[22:34:11] <navcoin-bot> <aguycalled> yes i also need to merge the new patches in the dao branch
[22:35:07] <navcoin-bot> <aguycalled> if you mean it does not answer to rpc commands while verifychain runs, i think its normal but havent tried it myself
[22:43:45] <navcoin-bot> <salmonskinroll> well, it's right after i entered verifychain 4 0, and a couple of minutes later the error shows up. but i think it's still running. we will find out tomorrow.
[22:44:33] <navcoin-bot> <aguycalled> does the log say anything?
[22:45:18] <navcoin-bot> <salmonskinroll> a lot of these
[22:45:20] <navcoin-bot> <salmonskinroll> 2019-12-02 21:44:49 DisconnectBlock: Updated proposal 4a6b14238d851f710429ac5656c424f3778263322c039d98e95b91ec06be2257 votes at height 3152972: yes(2443) no(734) 2019-12-02 21:44:49 DisconnectBlock: Updated proposal 8a658654a858bb43a0048d96b5c84a5b0a454f683f1db31b63eacffdac698fcd votes at height 3152972: yes(4782) no(202) 2019-12-02 21:44:49 ERROR: GetAllPaymentRequests() : failed to read value 2019-12-02 21:44:49 ERROR:
[22:45:20] <navcoin-bot> GetAllProposals() : failed to read value 2019-12-02 21:44:49 ERROR: GetAllPaymentRequests() : failed to read value 2019-12-02 21:44:49 ERROR: GetAllProposals() : failed to read value 2019-12-02 21:44:49 DisconnectBlock: Updated proposal 4a6b14238d851f710429ac5656c424f3778263322c039d98e95b91ec06be2257 votes at height 3152970: yes(2442) no(734) 2019-12-02 21:44:49 DisconnectBlock: Updated proposal
[22:45:21] <navcoin-bot> 8a658654a858bb43a0048d96b5c84a5b0a454f683f1db31b63eacffdac698fcd votes at height 3152970: yes(4781) no(202) 2019-12-02 21:44:49 ERROR: GetAllPaymentRequests() : failed to read value 2019-12-02 21:44:49 ERROR: GetAllProposals() : failed to read value 2019-12-02 21:44:49 ERROR: GetAllPaymentRequests() : failed to read value 2019-12-02 21:44:49 ERROR: GetAllProposals() : failed to read value
[22:46:20] <navcoin-bot> <aguycalled> if it keeps printing those it means verifychain is still running
[22:46:24] <navcoin-bot> <aguycalled> did you bootstrap?
[22:46:28] <navcoin-bot> <salmonskinroll> yup
[22:46:59] <navcoin-bot> <aguycalled> did it reindex at launch?
[22:47:00] <navcoin-bot> <salmonskinroll> bootstrap and then verifychain 4 10000 with a success, then verifychain 4 0
[22:47:06] <navcoin-bot> <salmonskinroll> i don't believe so
[22:47:07] <navcoin-bot> <salmonskinroll> no
[22:47:23] <navcoin-bot> <salmonskinroll> i think the bootstrap is already on new database no?
[22:47:34] <navcoin-bot> <aguycalled> i dont think so
[22:47:42] <navcoin-bot> <salmonskinroll> hmm
[22:47:45] <navcoin-bot> <aguycalled> what commit are u on?
[22:48:05] <navcoin-bot> <salmonskinroll> should be the last commit of pr 634
[22:48:10] <navcoin-bot> <salmonskinroll> wait
[22:48:12] <navcoin-bot> <salmonskinroll> damn it
[22:48:18] <navcoin-bot> <salmonskinroll> i might not have git pull
[22:49:23] <navcoin-bot> <salmonskinroll> okay i did, so im on the latest commit
[22:49:33] <navcoin-bot> <aguycalled> using gui or headless?
[22:49:59] <navcoin-bot> <salmonskinroll> headless, how do i check the commit version in commnad line?
[22:50:28] <navcoin-bot> <salmonskinroll> but i launched a node with GUI as well and it didn't reindex
[22:50:30] <navcoin-bot> <salmonskinroll> with bootstrap
[22:50:37] <navcoin-bot> <aguycalled> git log -n1
[22:51:00] <navcoin-bot> <salmonskinroll> okay cool im on latest commit for sure
[22:51:28] <navcoin-bot> <salmonskinroll> but i did see it askign for reindex when i didn't use bootstrap on another node
[22:51:44] <navcoin-bot> <salmonskinroll> therefore i thought bootstrap is already good
[22:51:50] <navcoin-bot> <salmonskinroll> with new structure etc
[22:52:14] <navcoin-bot> <aguycalled> @prole did you update the bootstrap node ?