Syncing Update:
6.0 seems to be going relatively good, breaking the problem up into 2 pieces:
1) Not able to sync even after restarting Gridcoin <----------- I believe 6.0 fixed this one
2) Client stops talking to peers, 4500 internal gridcoin peers (debug log says Connection Failure) - Looks to user like a sync issue, but a restart fixes this.
If we can confirm #2 is the only issue left regarding syncing, Ill focus on #2 next.
Rob H.
where can i find release 6.0? |
|
|
|
Syncing Update:
6.0 seems to be going relatively good, breaking the problem up into 2 pieces:
1) Not able to sync even after restarting Gridcoin <----------- I believe 6.0 fixed this one
2) Client stops talking to peers, 4500 internal gridcoin peers (debug log says Connection Failure) - Looks to user like a sync issue, but a restart fixes this.
If we can confirm #2 is the only issue left regarding syncing, Ill focus on #2 next.
Rob H.
My sync issues seem to be gone but I am having problems where my client stops communicating with my miner which I assume is due to problem #2. It seems to be happening (at least for me) whenever I have found a block as my cgminer displays a found block and then immediately displays that "pool 0 is down" and caches the submission until it is stale, then it usually shows a few more new blocks and then "pool 0 is down" shows permanently until restart. |
|
|
|
|
Please push the latest version of the source and if possible please try to keep the source current at all times because your downloads are being flagged as malicious by Google Chrome.
***Edit***
They are most likely being flagged as malicious because you are packaging cgminer with the client, cgminer is technically a brute-force password cracker.
|
|
|
|
For those having trouble with cgminer crashing constantly, please try adding this to your gridcoin.conf: closemineronexit=false
restartwallet=0 |
|
|
|
All my wallet balances and transaction are way off with the new client. It is showing amounts on transactions that I have never done. Also the wallet is not showing anything mined after 12/5/2013. Very odd.
That is pretty weird that it's not showing your mined tx's... For the tx's you're seeing that you never created, are they perhaps the beacon tx's for cpu mining...? |
|
|
|
|
Merry X-mas everyone!
Just wanted to let Rob know I woke up this morning to find my client stalled again with the latest version.
My cgminer shows that it had a rejected block, three new blocks passed after that and then that is where the client stalled at, so it seems to be the same situation that someone else was having earlier.
|
|
|
|
|
I can confirm that my external instance of cgminer is no longer crashing. I still get a bit of lag on intensity 13 with the internal miner so I'm scared to try my usual 18. For now I am using the external miner, I am gong to do some last minute Christmas shopping and when I return I will experiment with the higher intensity settings.
For now though, it does appear (at least to me) that the external miner crashes are over.
|
|
|
|
Version 5.8.3 (1.1.4.4) is available for download:
You can type "upgrade" from the RPC for this version.
The following changes have been made:
1. We disabled the blockchain snapshot feature in hopes after block 36775 and a 51% majority upgrade the root sync issue will be fixed, and to alleviate the cgminer restart problem.
2. Fixed the communication with the cgminer API.
3. Added a CGMiner monitor checkbox, that will automatically restart the API if your mh/s drops to zero; it is checked once every 5 minutes.
4. Added a 25 second delay to initialize the miners so that the client can start quicker and smoother.
5. Fixed the close guiminer/close cgminer bug (IE we start the API once and only once, and monitor it once every 5 minutes).
Rob H.
PS - TribalBob-- The snapshot feature was the culprit for the Cgminer close problem; please try this version. Also, the sluggishness bug "should" be fixed in this version; please update us.
We still have to wait for block 36775 to pass with 50% upgrading before we know for sure; lets cross our fingers.
Wow, that was quick! Good work Rob! The communication problem with the API being fixed should theoretically repair the sluggishness as well, correct...? ***Edit*** Wow, just realized you specifically mentioned that already, lol... Not sure how I missed it, sorry... |
|
|
|
|
Also, my external cgminer is still crashing every 10 - 15 minutes even with "restartwallet=0" set.
|
|
|
|
|
Ok, I'm not sure why, but my cgminer instance still causes my desktop to become very sluggish when I launch cgminer from inside the client... I will be working on troubleshooting this today...
***Edit***
Can you push the latest version of the source, thanks!
***Edit***
Ok, if I set the intensity lower (13) on the internal miner the sluggishness mostly goes away, but then I only get ~10Kh/s. I normally run cgminer on intensity of 18 with no problems.
|
|
|
|
Reproduced: You found it! We are storing a mined stale block that does not validate the boinchash as an orphan; its propogating and getting stuck at the end of the blocks table. The only workaround is to re-sync. I think this is the whole problem. I'll fix this and test now; will release a fix as soon as it is tested!
Thanks for finding this!
Rob H.
I am about 99% sure this will be the cause. Well done COINPRADER! |
|
|
|
I am trying to understand the BOINC projects panel in the client display. It seems to come preloaded with the names of five projects, a couple of which I sometimes use but have not been accepting tasks from in recent months. The WCG is not among them, and it happens to be the project I spend all my BOINC time on recently. Anyway, is this list customizable, and if so are there instructions for it somewhere that I have overlooked?
Please forgive my bumping this part of my earlier post. I'm still trying to make sense of the BOINC projects panel. I've found old tutorials, but they only show how to set up new BOINC project accounts (assuming that users are new to BOINC) and they refer only to project names hard-coded in the panel. My situation differs somewhat. I've been using BOINC through BAM since 2009 and my projects were in place before I set up Gridcoin. I've found advice to add projects to the project panel but I've not found a way to do it. Also, the information I've seen advises replacing project IDs at each individual BOINC project home page with a Gridcoin payout addy. This seems onerous and would negate the advantage of dealing with BOINC projects through BAM. Does it really have to be like that or am I finding outdated advice? In summary: Is it necessary to use the project panel at all to mine Gridcoin and get credit for BOINC activity? If so, is there an up-to-date tutorial link, especially one that shows how to enter pre-existing BOINC project data? Is it really a requirement to enter a Gridcoin payout ID on each relevant BOINC project's home page? If so, explanation might make it a more palatable requirement. Thanks - I'm getting there - I'm in the top 1% of BOINC users so I'd really like to help the Gridcoin effort.  I should have linked this for you yesterday, sorry about that: https://cryptocointalk.com/topic/1922-cpu-mining-tutorialtopic/That link will explain what to do with the projects listed. For the moment I believe those projects are the only ones which are eligible for the cpu mining pool but I think there are plans to add more. For the time being, you can join just those projects or you can join other projects as well, it will not hurt your ability to solve blocks and get rewarded, but I think it may detract from your cpu mining earnings... |
|
|
|
People having issues with guiminer... do you have guiminer running inside the client or separately? I have it running inside the client's Mining Console and it hasn't given me a problem yet.
So if you're running it outside, do this to run it in the Mining Console. Just make a copy of your guiminer folder, and put it into your AppData\Roaming\Gridcoin folder and make sure its named guiminer.
If you're running it inside the client and it's giving you problems, have you tried executing it separately? I know when Gridcoin starts up, it closes any instances of guiminer already running but I think if you open guiminer while Gridcoin is already running it should be fine.
Yeah, I'm pretty sure it has something to do with the external miners because my external instance of cgminer is crashing every 10 - 15 minutes, I'm sure Rob will have it figured out in no time once he sees the thread. |
|
|
|
I installed the new version about 12 hours ago and it seems to be working normally. It shows only one active connection to the network now, which seems a bit, um, sparse. It reports 36141 blocks of history and updates regularly.
I am trying to understand the BOINC projects panel in the client display. It seems to come preloaded with the names of five projects, a couple of which I sometimes use but have not been accepting tasks from in recent months. The WCG is not among them, and it happens to be the project I spend all my BOINC time on recently. Anyway, is this list customizable, and if so are there instructions for it somewhere that I have overlooked?
Also - the display shows BOINC utilization 50, thread count 6 (sometimes 7) and average daily credits zero, which I think I understand from reading previous posts here. It also shows BOINC MD5 as MD5Error and BOINC Khps as zero, which I don't understand. After about one day of running, the wallet balances are zero - from other posts I got the impression it might have found a block or three at this early stage. I'm not sure whether to look for errors or just wait a while.
Thanks for any suggestions!
Do you have BOINC installed in the default location...? It sounds like your Gridcoin client is not communicating with the BOINC client. If you have BOINC installed somewhere other than the default location you need to add the BOINC folder and BOINC data folder locations to your gridcoin.conf file. I think someone mentioned the flags for that somewhere in the thread... |
|
|
|
|
For the newest version:
1) Delete "c:\Program Files (x86)\Gridcoin"
2) Rename "%AppData\Roaming\Gridcoin" to "Gridcoin Orig"
3) Download the latest version
4) Install the latest version
5) Copy wallet.dat and gridcoin.conf from "Gridcoin Orig"
6) Run the program, if everything works, you may delete "Gridcoin Orig"
This is EXACTLY what I did to update and it is working just fine for me.
Kudos Rob!
|
|
|
|
Hello,
I installed the Gridcoin QT (5.79) and started, but it is not syncing with the network.
Any idea's?
Have you tried the other things already mentioned in this thread (i.e. forwarding the listening port, using the addnodes in your .conf)...? |
|
|
|
|
Wow, Rob comes up with THE single most innovative alt-coin (perhaps even more innovative than Bitcoin itself IMHO) which is using a lot of BRAND NEW code (this is NOT a simple cut+paste clone) and all people can do is complain that there are a few bugs here and there or claim that he is simply trying to make himself some coin by just putting out another clone.
Understand this:
Rome was not built in a day. This coin has been out for just about a month and a half, it's bound to have some issues. At least we have a VERY active and VERY capable dev who is working on the situation.
Until YOU have sat at a command line painstakingly debugging code line by line for weeks at a time, you REALLY shouldn't complain.
|
|
|
|
Oh thanks Rob H.,
So is there any advantage other than syncing ?
Btw I am having syncing issues .. block explorer is showing 35590 whereas my client is showing 35606 (more than block explorer !!). What should I do ?
Thanks
The block explorer has stalled, pay no attention to it for the moment... |
|
|
|
The new version is available
I'm trying Gridcoin for the first time - stumbled onto this thread and was keen to try it out since I'm a regular user of both BOINC and crypto. I casually ran qt from the msi download and it instantly terminated the two command line instances of cgminer I was running at the time (one of 3.7.2 for LTC and one of 3.8.5 for BTC). Oops - not a good time to be casual. I started over more carefully, but some 30 minutes into what I thought would be a routine run to update the blockchain I'm still seeing "No block source available" and "nine weeks behind" and "0 active connections to Gridcoin network". Is this delay normal? Am I just spoiled by the relatively quick connections with LTC and BTC? Have I overlooked something obvious? I'm using Win7 64, and I stopped all instances of cgminer (and BOINC) before the present run. Thanks for any advice. Try this in your gridcoin.conf (specifically the addnodes): rpcuser=YourUsername
rpcpassword=YourPassword
rpcallowip=127.0.0.1
server=1
poolmining=false
addnode=98.114.181.178
addnode=76.187.184.27
addnode=66.187.94.194
addnode=76.74.177.224
addnode=84.125.196.167
addnode=71.233.139.62
addnode=72.92.48.105 Thanks - I'll check it out (suppressing twitches at direct addys). Gotta really pay attention now. LOL, alternatively you could try just forwarding the listen port on your router (port 32760) which should also work. |
|
|
|
The new version is available
I'm trying Gridcoin for the first time - stumbled onto this thread and was keen to try it out since I'm a regular user of both BOINC and crypto. I casually ran qt from the msi download and it instantly terminated the two command line instances of cgminer I was running at the time (one of 3.7.2 for LTC and one of 3.8.5 for BTC). Oops - not a good time to be casual. I started over more carefully, but some 30 minutes into what I thought would be a routine run to update the blockchain I'm still seeing "No block source available" and "nine weeks behind" and "0 active connections to Gridcoin network". Is this delay normal? Am I just spoiled by the relatively quick connections with LTC and BTC? Have I overlooked something obvious? I'm using Win7 64, and I stopped all instances of cgminer (and BOINC) before the present run. Thanks for any advice. Try this in your gridcoin.conf (specifically the addnodes): rpcuser=YourUsername
rpcpassword=YourPassword
rpcallowip=127.0.0.1
server=1
poolmining=false
addnode=98.114.181.178
addnode=76.187.184.27
addnode=66.187.94.194
addnode=76.74.177.224
addnode=84.125.196.167
addnode=71.233.139.62
addnode=72.92.48.105 |
|
|
|
|
Show Posts
