Bible Pay

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - T-Mike

Pages: [1] 2 3 4 5 6 7 8 9
1
Are your nodes synced? mnsync status?

2
Ok cool.  Ill run it that way also if I encounter a crash.

On your nonsyncing sanc you can check to see in coin control if you still have the 500K.  I spent mine today, and it didnt throw any errors and stopped syncing in mnsync also... Reenabling mine now to see if that was it.

I checked my wallet and both of the wallet accounts have at least 500k tBBP. Masternode outputs also still show 2 hashes. Both nodes are still at 1. How does the nodes sync anyways? Does it get the information from the memory pool? Where is the memory pool?

UPDATE:
Node #2 stopped again.

UPDATE#2:
You forgot to add "install" in the apt-get command if you want to update it.

UPDATE#3:
valgrind is using 99% of my cpu and getinfo returns
error code: -28
error message:
Loading block index...

I upgraded to 2GB ram but it's the same. I tried getinfo without valgrind and its fine.

UPDATE #4:
Valgrind gave me something when I left it running:

3
Can you please run it in valgrind if you have more than 2gb of ram?

sudo apt-get valgrind

valgrind ./biblepayd

?

That will give us the line of the error.

The vps only has 0.7gb of ram. I can try that later when I upgrade it but I'll just monitor it for now. Thank you.

4
I was setting up a 2nd node so I had to restart the daemon on my controller wallet. Now the daemon will only run for about a minute then stop.

2018-02-20 02:33:22  GetBlockSubsidy 2673.000000
2018-02-20 02:33:22 init message: Done loading
2018-02-20 02:33:33 P2P peers available. Skipped DNS seeding.
2018-02-20 02:33:33 dnsseed thread exit
2018-02-20 02:33:45 Misbehaving: 206.125.154.17:5719 (0 -> 14)

UPDATE

Not sure what's going on but started it a third time and it's running ok now.....

5
My node was synced but now it's not, is that normal? I do see the blocks going up.

  "AssetID": 1,
  "AssetName": "MASTERNODE_SYNC_SPORKS",
  "Attempt": 0,
  "IsBlockchainSynced": false,
  "IsMasternodeListSynced": false,
  "IsWinnersListSynced": false,
  "IsSynced": false,
  "IsFailed": false,
  "MasternodesEnabled": true

"version": 1000903,
  "protocolversion": 70715,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.3",
  "balance": 3198180.27801030,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 2688,
  "timeoffset": 0,
  "connections": 10,
  "proxy": "",
  "difficulty": 0.07714083926784768,
  "testnet": true,
  "keypoololdest": 1518115544,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""

6
Ok. Now to testing :) After update I've must to start mining to have some tBBP to join Rosetta. Now I'm in, but my magnitude is 0. It all starts from zero after update?

No, whenever it gets the data file from Rosetta it will update your mag.

7

I think you are OK - sometimes new masternodes take a few hours to sync.  Could you please see if your blocks are still moving on that node- past block 2005?  And then type:
mnsync reset

And lets see if it makes it to 999?

Log looks OK.

It's synced now. It took much longer than I was used to so that's why I posted it.

8
Pre-enabled but stuck here:

"AssetID": 3,
  "AssetName": "MASTERNODE_SYNC_MNW",
  "Attempt": 12,
  "IsBlockchainSynced": true,
  "IsMasternodeListSynced": true,
  "IsWinnersListSynced": false,
  "IsSynced": false,
  "IsFailed": false,
  "MasternodesEnabled": true
Code: [Select]

Debug.log:
2018-02-19 20:24:10 Misbehaving: 144.202.17.17:46840 (0 -> 14)
2018-02-19 20:24:14 We have a pending superblock at height 1980.000000  AcceptBlock::ExecuteDistributedComputingSanctuaryQuorumProcess PENDING_SUPERBLOCK UpdateTip: new best=0e4$
2018-02-19 20:24:14 AddToWallet 3ea3e5192c0d5a61091d6537daa5b53e239a58d1d3d1213ba6e46e3cb06ecd83  new
2018-02-19 20:24:14 ProcessNewBlock : ACCEPTED
2018-02-19 20:24:18 Misbehaving: 206.125.154.17:27637 (0 -> 14)
2018-02-19 20:24:36 We have a pending superblock at height 1980.000000  AcceptBlock::ExecuteDistributedComputingSanctuaryQuorumProcess PENDING_SUPERBLOCK UpdateTip: new best=52f$
2018-02-19 20:24:36 ProcessNewBlock : ACCEPTED
2018-02-19 20:24:39 We have a pending superblock at height 1980.000000  AcceptBlock::ExecuteDistributedComputingSanctuaryQuorumProcess PENDING_SUPERBLOCK UpdateTip: new best=911$
2018-02-19 20:24:39 ProcessNewBlock : ACCEPTED
2018-02-19 20:24:43 We have a pending superblock at height 1980.000000  AcceptBlock::ExecuteDistributedComputingSanctuaryQuorumProcess PENDING_SUPERBLOCK UpdateTip: new best=7f0$
2018-02-19 20:24:43 ProcessNewBlock : ACCEPTED
2018-02-19 20:24:54 We have a pending superblock at height 1980.000000  AcceptBlock::ExecuteDistributedComputingSanctuaryQuorumProcess PENDING_SUPERBLOCK UpdateTip: new best=d05$
2018-02-19 20:24:54 ProcessNewBlock : ACCEPTED
2018-02-19 20:25:00 We have a pending superblock at height 1980.000000  AcceptBlock::ExecuteDistributedComputingSanctuaryQuorumProcess PENDING_SUPERBLOCK UpdateTip: new best=e74$
2018-02-19 20:25:00 ProcessNewBlock : ACCEPTED
2018-02-19 20:25:25 We have a pending superblock at height 1980.000000  AcceptBlock::ExecuteDistributedComputingSanctuaryQuorumProcess PENDING_SUPERBLOCK UpdateTip: new best=d4f$
2018-02-19 20:25:25 ProcessNewBlock : ACCEPTED
2018-02-19 20:25:34 We have a pending superblock at height 1980.000000  AcceptBlock::ExecuteDistributedComputingSanctuaryQuorumProcess PENDING_SUPERBLOCK UpdateTip: new best=9f7$
2018-02-19 20:25:34 ProcessNewBlock : ACCEPTED



9
I had to mine a few hundred blocks in order to have enough to start a hot sanc.  Do u need some tBbp?

The peers warning should be gone now; it comes up when all your peers have different block heights.

Yeah, if you have any, thanks. I'm still aiming for 10 nodes.

yZoJUy6JzbPahVW4zq2UWJCgKTMv6SUCjh

10
Rob, how did you send the tBBP to yourself, Before I updated, it gave me that peers warning message when I tried to look up my addresses.

11
both on block: #11978

I think we lost our testnet explorer,
I can spin up another vultr and set one up, I assume we need one still?

cd ~/.biblepaycore
cd testnet3/
tail debug.log


I get the same error.

2018-02-19 03:34:15 Misbehaving: 94.130.53.103:35416 (0 -> 14)
2018-02-19 03:37:20 Misbehaving: 94.130.53.103:40001 (0 -> 14)
2018-02-19 03:38:04 Misbehaving: 195.201.30.231:34442 (0 -> 14)
2018-02-19 03:40:09 Misbehaving: 38.21.22.209:12281 (0 -> 14)
2018-02-19 03:44:50 Misbehaving: 91.219.3.153:53440 (0 -> 14)
2018-02-19 03:48:22 Misbehaving: 195.201.30.231:38404 (0 -> 14)
2018-02-19 03:48:56 Misbehaving: 94.130.53.103:35844 (0 -> 14)
2018-02-19 03:50:13 Misbehaving: 38.21.22.209:12452 (0 -> 14)
2018-02-19 03:54:26 Misbehaving: 94.130.53.103:40001 (0 -> 14)
2018-02-19 03:55:37 Misbehaving: 91.219.3.153:53568 (0 -> 14)
2018-02-18 22:04:45 Misbehaving: 38.21.22.209:4643 (0 -> 14)
2018-02-18 22:07:39 Misbehaving: 195.201.30.231:42166 (0 -> 14)
2018-02-18 22:07:48 Misbehaving: 94.130.53.103:40001 (0 -> 14)
2018-02-18 22:09:50 Misbehaving: 94.130.53.103:40001 (0 -> 14)
2018-02-18 22:12:45 Misbehaving: 95.91.244.91:57302 (0 -> 14)
2018-02-18 22:13:01 Disconnecting unauthorized peer with Network Time off by 548.000000 seconds!
2018-02-18 22:13:01 Misbehaving: 47.189.53.97:54037 (0 -> 12)
2018-02-18 22:14:27 Disconnecting unauthorized peer with Network Time off by 548.000000 seconds!
2018-02-18 22:14:27 Misbehaving: 47.189.53.97:54070 (0 -> 12)
2018-02-18 22:14:48 Misbehaving: 38.21.22.209:4808 (0 -> 14)

12
Im pretty neutral, Id have to think about it more and also check Gridcoin and their pros/cons of the team requirement

I have 2 testnet sanctuaries up!

Honestly, I didn't really want everyone flooding in to take a share of the pie, but that's just being greedy. So if helping with cancer research is our top goal, then it doesn't really matter if people are double dipping or triple dipping. Now if we want to advertise ourselves, we could always use the combined RAC and have a counter on the website. I think there is more to think about here so we should let it churn a little more.

13

Yeah, this version has really shaken things up...

Can you all please upgrade to 1092c now.... and try syncing again please.



Windows is rebuilding now...

Rob, appears to be working good now. Great job!

14
I updated my node but it doesn't appear to be syncing. I ran

rm blocks -R
rm chainstate -R
rm banlist.dat fee_estimates.dat governance.dat mncache.dat mnpayments.dat netfulfilled.dat peers.dat db.log debug.log

before starting the daemon.

"version": 1000902,
  "protocolversion": 70715,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.2",
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 692,
  "timeoffset": 0,
  "connections": 1,
  "proxy": "",
  "difficulty": 0.002553704361813557,
  "testnet": true,
  "keypoololdest": 1518115544,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""

  "AssetID": 1,
  "AssetName": "MASTERNODE_SYNC_SPORKS",
  "Attempt": 0,
  "IsBlockchainSynced": false,
  "IsMasternodeListSynced": false,
  "IsWinnersListSynced": false,
  "IsSynced": false,
  "IsFailed": false,
  "MasternodesEnabled": true

Debug.log:
2018-02-17 21:41:59 26 addresses found from DNS seeds
2018-02-17 21:41:59 dnsseed thread exit
2018-02-17 21:41:59 Misbehaving: 195.201.30.231:60418 (0 -> 10)
2018-02-17 21:44:57 Misbehaving: 94.130.53.103:38154 (0 -> 10)
2018-02-17 21:47:46 Misbehaving: 38.21.22.209:42302 (0 -> 10)

15
Hi, like I said, I had many problems with it. Even when the phone was on charger it still had problem and wanted to plug in the power source. At the end my settings are approx like this: battery as power source, 0% min. battery, 2 CPU cores (2 of 4), 100% CPU limit, stop with CPU usage ove 80%. Now it is working almost perfectly with some small issues yesterday.

I see, I will play around with it some more. Thanks.

Pages: [1] 2 3 4 5 6 7 8 9