BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

Started by Rob Andrews, February 06, 2018, 04:00:36 PM

Previous topic - Next topic

MIP

Quote from: Rob A. on March 06, 2018, 07:32:51 AM
Yes, im on 33235 also.
Whats your exec getboincinfo output?

The same I posted some hours before



Quoteexec getboincinfo

{
  "Command": "getboincinfo",
  "CPID": "",
  "Address": "",
  "CPIDS": "",
  "CPID-Age (hours)": 422317,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -2,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

The funny thing is that the CPID-Age (hours) is correct, but CPID itself is blank. Also I saw the 1BBP charge but as we have been in current block since then, transaction (e6e5d60e2c4d85d1e6f7ccec7dbae61ccacda8f9947b2d6a8277de2260c07206-000) is not confirmed yet.

T-Mike

podcupdate gave true last night but my CPI is still not associated. I moved the cpid from my controller wallet to the sanctuary. Updating to the latest version now.

By the way, make -j4 doesn't seem to be doing anything, it seems to still use only 1 core.

MIP

Quote from: T-Mike on March 06, 2018, 08:11:35 AM
podcupdate gave true last night but my CPI is still not associated. I moved the cpid from my controller wallet to the sanctuary. Updating to the latest version now.

By the way, make -j4 doesn't seem to be doing anything, it seems to still use only 1 core.

I tried to compile once in a 16 vCPU with -j4 and -j8 and gcc crashed badly. -j2 worked fine though.

Rob Andrews

Quote from: MIP on March 06, 2018, 07:50:14 AM
The same I posted some hours before



The funny thing is that the CPID-Age (hours) is correct, but CPID itself is blank. Also I saw the 1BBP charge but as we have been in current block since then, transaction (e6e5d60e2c4d85d1e6f7ccec7dbae61ccacda8f9947b2d6a8277de2260c07206-000) is not confirmed yet.

In your case it looks like the problem is the CPID is still not associated.   The e6e tx is not being accepted by the current state of the network.

Try re-associating your cpid again, until the tx is confirmed.

Once we are live in prod with a supermajority, I anticipate this problem diminishing.



Rob Andrews

1.1.0.2b for windows has been released.

Alright, I suppose this marks the milestone where I believe the bugs we found in testnet have been resolved.

Im going to go ahead and attempt an upgrade of a few of my prod sancs now (with 1102b) and also try the association in prod with my CPID, to see if we squashed all known bugs.


T-Mike

Rob, why does running the commands below cause my daemon to stop after a few seconds. It refuses to run continuously.

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

This happened to me yesterday and I had to start from scratch and it's doing it again today.

Rob Andrews

Quote from: T-Mike on March 06, 2018, 09:13:25 AM
Rob, why does running the commands below cause my daemon to stop after a few seconds. It refuses to run continuously.

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

This happened to me yesterday and I had to start from scratch and it's doing it again today.

Running those would cause multiple problems - the database state would be corrupted in memory.
You would need to run those after you stop the node.


T-Mike

Quote from: Rob A. on March 06, 2018, 09:35:50 AM
Running those would cause multiple problems - the database state would be corrupted in memory.
You would need to run those after you stop the node.

Right, I did run them after I stopped the daemon. Maybe it didn't stop? I will check next time before I remove.

Rob Andrews

Alright guys, I think we are starting to be pressured into a mandatory upgrade.

Lict has raised a very valid point in prod - since I upgraded node.biblepay.org and the pool server, now the pool is enforcing the 1102 chain, which is causing questions.

So I suppose we need to hurry up and test 1102 and make a decision for release candidate.

I just checked my ca89 cpid association in prod and it was successful and I have utxo weight.

Luke, do you have utxo weight now?

Are we experiencing any other problems?

Im going to upgrade a few sancs now.


MIP

Quote from: Rob A. on March 06, 2018, 10:01:46 AM
Alright guys, I think we are starting to be pressured into a mandatory upgrade.

Lict has raised a very valid point in prod - since I upgraded node.biblepay.org and the pool server, now the pool is enforcing the 1102 chain, which is causing questions.

So I suppose we need to hurry up and test 1102 and make a decision for release candidate.

I just checked my ca89 cpid association in prod and it was successful and I have utxo weight.

Luke, do you have utxo weight now?

Are we experiencing any other problems?

Im going to upgrade a few sancs now.

I have 1.1.0.2 and the transactions I made a few hours ago show as "unconfirmed" (one of them is the 1BBP).

At this point I don't know which chain I am on. Is blockexplorer in the new one or the old one?

I already upgraded the MN without apparent issues though.

Rob Andrews

Quote from: MIP on March 06, 2018, 10:20:01 AM
I have 1.1.0.2 and the transactions I made a few hours ago show as "unconfirmed" (one of them is the 1BBP).

At this point I don't know which chain I am on. Is blockexplorer in the new one or the old one?

I already upgraded the MN without apparent issues though.

I think Togo is the only block explorer left as I think Alex went on vacation, uh I dont know if Togo upgraded his bx.

In my 1102 node, Lict pointed out our chain just switched over in 1102 to the higher diff chain, and I just confirmed this - so here is what Im getting now:


10:24:18

getblockhash 33268


10:24:18

550699009b14fe33f79be164dbba0ac063e4423d7a0fa75f119738704c7388d1



Rob Andrews

Quote from: MIP on March 06, 2018, 10:20:01 AM
I have 1.1.0.2 and the transactions I made a few hours ago show as "unconfirmed" (one of them is the 1BBP).

At this point I don't know which chain I am on. Is blockexplorer in the new one or the old one?

I already upgraded the MN without apparent issues though.

On the unconfirmed, if you could double click it - if its an associate, please reassociate, if its a PODC update, just do a new one.

Those will probably stay unconfirmed forever - then later do a restart with -zapwallettxes


togoshigekata

Quote from: Rob A. on March 06, 2018, 10:26:19 AM
I think Togo is the only block explorer left as I think Alex went on vacation, uh I dont know if Togo upgraded his bx.

Upgrading the Backup Explorer right now, should be ready soon
http://explorer.biblepay.org:3001/

T-Mike

My PODC wallet is running in headless. Does the auto-unlock work like in the GUI? If not, what's the best way for UTXO?

getblockhash 33276
6c148975fdac517c89b9f1cf7447cd8ea32b5fce023ec46fc4e1729e700b5be2

Rob Andrews

Quote from: SimonSays on March 06, 2018, 10:32:00 AM
Hi,

My unconfirmd transaction is withdraw from the pool:

Status: 0/unconfirmed
Date: 6.3.2018 06:17
From: unknown
To: B7AZbMPwtCNejwiLktZteGKuSgdmUkzq4m (own address)
Credit: 430.00000000 Biblepay
Net amount: +430.00000000 Biblepay


:
Transaction ID: 143ff5a08d229cffd2d881e9e9aee4bae20122a84fd8b1d0804306010028f0cf-000



Debug information

Credit: 430.00000000 Biblepay

Transaction:
CTransaction(hash=143ff5a08d, ver=1, vin.size=1, vout.size=2, nLockTime=33204)
    CTxIn(COutPoint(a0dadb18179ae1dd38345883c2712797929edb518493d021d1359c0a2db8c37f, 0), scriptSig=473044022019a008719811f0, nSequence=4294967294)
    CTxOut(nValue=430.00000000, scriptPubKey=76a9141dc8a8dbf8caca55dd871013)
    CTxOut(nValue=5543.49989254, scriptPubKey=76a9141b7d8578af86bb535bb70f36)

Inputs:
BNvQ5Txs1riZvuKA5W7prbtwx7PuSXXBwL Amount=5973.49993834 Biblepay IsMine=false IsWatchOnly=false



Best regards,
Simon

This was paid in 1101, could you please resync, I see the tx on my sanctuary... Existing.