Gridcoin (GRC) - first coin utilizing BOINC - Official Thread

[TribalBob]

If anyone is having trouble with syncing or stalling after the latest update do this:

1. Close your Gridcoin client
2. Delete everything in your AppData\Roaming\Gridcoin folder EXCEPT the gridcoin.conf, wallet.dat, and if you use it, the guiminer folder
3. Make sure you have the latest client (if you open the Mining Console, you should see Version: 29, if not install the latest .MSI from the website
4. Start the client and it should completely resync

I have done clean re-installs of the latest client (version 29) multiple times and I am still having sync issues at times. See my post above as I believe I know the reason for this.

[1713413295]

1713413295

[1713413295]

1713413295

[1713413295]

1713413295

[1713413295]

1713413295

[Inrideo]

There seems to be something that happened in the chain starting around 21 hours ago.

In the previous two days I made 52 coins from my CPU+nvidia card.

Today I seem to have made 3 or 4 coins, but can't be sure as the sync is once again choking at 21 hours behind.

edit: typo fixed.

[Inrideo]

It took about seven minutes to process the chain at the 21 hour mark, then it continued again. It has now stalled at the 8 hour mark.

Just providing that in case it points to something helpful
 
edit: Turned out at 8 hours it hit wallet corruption, but resumed again on a restart.

[aleistermarley]

Is anyone else having trouble with their client occasionally stalling out...?

I woke up today to find my miner had been hashing away on the same block for more than 4 hours because one of my clients had stalled and was pretty far behind in the actual block count even though the client said it was synced.

What's really weird is that my other client (I have two pc's and one runs cgminer on load balance between the two clients) was still perfectly synced but the miner was not receiving new block notifications from the synced client either.

Anyone else experiencing anything similar...?

I seem to have the same issue.

Most of the times i end up with a corrupted wallet.dat too
-rescan option does not help me.
The only solution for me is to delete the complete blockchain database and restore my wallet from backup.

Last time i deleted the peers.dat too - but then it refused to make more than only 1 (one) connection to the network  
So i better kept my old peers.dat to get back to the normal 8 connections.

I have the latest client installed and doing cpu and gpu mining.

greetings

[Gridcoin]

It has something to do with the client collecting orphan blocks from old versions that are still running.  Looking at the debug file about 100 orphan blocks keep coming back.  Im running 4 machines and it affects one of them especially (resyncing once per day).  We could increment the minimum protocol version for everyone but that would require a global upgrade.  Any hardened cryptologists out there that would like to volunteer to help us clear out orphan blocks or give us advice?

In the mean time the only known solution is to close the wallet and delete the chainstate/database folders and restart.  I do not have to replace my wallet file when I do this.

I will try to devote some time to looking into this, but for the time being I've been busy creating a prototype for the scrypt-sleep algo.

Thanks,
Rob Halford

[Inrideo]

We should throw up a challenge on Slashdot for people to help

Though it would come with dickheads too :/

[traderman]

I say whoever has not updated by now, cut them out. Do a global upgrade and lets end these synching problems.

It has something to do with the client collecting orphan blocks from old versions that are still running.  Looking at the debug file about 100 orphan blocks keep coming back.  Im running 4 machines and it affects one of them especially (resyncing once per day).  We could increment the minimum protocol version for everyone but that would require a global upgrade.  Any hardened cryptologists out there that would like to volunteer to help us clear out orphan blocks or give us advice?

In the mean time the only known solution is to close the wallet and delete the chainstate/database folders and restart.  I do not have to replace my wallet file when I do this.

I will try to devote some time to looking into this, but for the time being I've been busy creating a prototype for the scrypt-sleep algo.

Thanks,
Rob Halford

[A L I E N]

I say whoever has not updated by now, cut them out. Do a global upgrade and lets end these synching problems.

It has something to do with the client collecting orphan blocks from old versions that are still running.  Looking at the debug file about 100 orphan blocks keep coming back.  Im running 4 machines and it affects one of them especially (resyncing once per day).  We could increment the minimum protocol version for everyone but that would require a global upgrade.  Any hardened cryptologists out there that would like to volunteer to help us clear out orphan blocks or give us advice?

In the mean time the only known solution is to close the wallet and delete the chainstate/database folders and restart.  I do not have to replace my wallet file when I do this.

I will try to devote some time to looking into this, but for the time being I've been busy creating a prototype for the scrypt-sleep algo.

Thanks,
Rob Halford

I agree, get things running smooth and solid before working further on the prototypical algo..

[traderman]

Seeing as cryptsy is in some difficulty right now I thought I would start another petition to have Gridcoin added to crypto-trade.com I have traded there and it seems like a decent exchange so far.

http://bitcointalk.org/index.php?topic=361562.0

Everyone make your vote count!

[Gridcoin]

Thats cool, I'll do a global upgrade on a certain near block, but first Id like to make sure the problem happens one more time and give everyone a little time to see this message.
Not positive if Ill be around the computer tonight and Id like to be around.

Has it happened today?

I think we can do a global upgrade either around 6pm tonight or tomorrow morning if it hasn't gone away.

Rob H.

[lmue]

GRC has no market yet. why so many rubbish coins at cryptsy while not accepting GRC. that is ridiculous.

[TribalBob]

Thats cool, I'll do a global upgrade on a certain near block, but first Id like to make sure the problem happens one more time and give everyone a little time to see this message.
Not positive if Ill be around the computer tonight and Id like to be around.

Has it happened today?

I think we can do a global upgrade either around 6pm tonight or tomorrow morning if it hasn't gone away.

Rob H.

I can confirm that I just had the problem on one of my clients about an hour ago. Launching with "-rescan" fixes the issue temporarily (at least for me anyway) but the problem is definitely recurring.

For those having trouble with sync issues on "stalled" wallets, before deleting the stuff in your roaming folder, try the following from a command prompt (windows users):

1) cd c:\Program Files (x86)\Gridcoin
2) gridcoin-qt.exe -rescan

This is consistently fixing my sync/stalled client issues and is essentially the same as deleting the files in your roaming folder as it forces the client to rescan the block chain.

But I still opt for the global upgrade, better to do it now than to continue letting new users jump on a faulty client...

[aysyr]

Yea I had it happen to all my machines the night before last (so I had to rescan yesterday morning) and it they're all good still except for one, which stalled 2 hours ago. So it's not happening as bad, but there are still instances it occurs.

[lmue]

vote here, now only 1 vote by me.

Question:    POLL: Which Alt Coin will see the most growth in 2014?

https://bitcointalk.org/index.php?topic=359521.0

[lmue]

Thats cool, I'll do a global upgrade on a certain near block, but first Id like to make sure the problem happens one more time and give everyone a little time to see this message.
Not positive if Ill be around the computer tonight and Id like to be around.

Has it happened today?

I think we can do a global upgrade either around 6pm tonight or tomorrow morning if it hasn't gone away.

Rob H.

how much time do you think is needed to launch the scrypt-sleep scheme into GRC mining?

[Gridcoin]

All,

I just released the global update (v1139) that forces the protocol upgrade.

Please try to type "upgrade", otherwise you can download the prod-msi, do the full reinstall, and then execute it again and choose "Repair".

Thanks,
Rob H.

[traderman]

This is just for people running the old version right.

All,

I just released the global update (v1139) that forces the protocol upgrade.

Please try to type "upgrade", otherwise you can download the prod-msi, do the full reinstall, and then execute it again and choose "Repair".

Thanks,
Rob H.

[Gridcoin]

Yes if you have v25 (mining console or higher), you can type upgrade, but everyone has to upgrade, the old version (1138 and down) will become obsolete.

[Inrideo]

What's the latest version? I have 29. Running upgrade in both regular and admin mode dies on me.

[Gridcoin]

What's the latest version? I have 29. Running upgrade in both regular and admin mode dies on me.

I dont think that changed, but the wallet has to be "1.1.3.9" now or your network will not work.  If you dont have that in the debug window, manually upgrade with the MSI-prod.

Looks like the highest block is 27864 right now.

3 of my 4 are now working, but my 4th was actually hosed already, crossing my fingers all....