Author

Topic: Gridcoin (GRC) - first coin utilizing BOINC - Official Thread - page 218. (Read 597505 times)

legendary
Activity: 1260
Merit: 1001
Your wallet file must be corrupt or something is wrong on your end, I have sent very large amount of GRC to other people and I have never had problems.

Is there a reason why transactions over a certain number of coins seem to get lost without confirmations?
I haven't really had any luck with transactions larger than 200 coins. Anything bigger I need to restore my wallet from backup and rescan.

I imagine this isn't limited to gridcoin, being part of a common wallet.
full member
Activity: 130
Merit: 100
Is there a reason why transactions over a certain number of coins seem to get lost without confirmations?
I haven't really had any luck with transactions larger than 200 coins. Anything bigger I need to restore my wallet from backup and rescan.

I imagine this isn't limited to gridcoin, being part of a common wallet.
full member
Activity: 130
Merit: 100
The reason it was likely exiting from the DOS window for you before was that there was no cgm session profile. Once you created a new one you were good to go.
I accidentally took out my cgm profile when I was doing cleanup in the folder the other day and had the same issue. A few clicks later and all was well again.
legendary
Activity: 1450
Merit: 1013
Cryptanalyst castrated by his government, 1952
that string conversion bug only happens if you leave a field blank on the mining config screen; try pulling up each card instances config, verify every field is filled in and click save,


Yikes - my fault. I forgot that I had to fill them in. Haven't done it in so long that I thought they would come in from a table on your end. I'll proceed (more carefully) with the next steps. I still can't yet account for the original disappearing miner instance though.

Edit: update - a bit more detail - if I use the "Load Defaults for" feature it fills in the table so that's why I thought you would supply the data. However, whether I use that or enter data manually I still get the string conversion error when I press the "Create CG Miner instance" button, after which all the fields are blanked out again.

I'll keep digging.

Edit: update - I went back to version 64 (which used to work) and it no longer finds a cgminer instance. The error is almost certainly on my end, I now think.

Still digging.

Edit: update - The plot thickens. I had renamed gridcoin.conf so that the program could generate a fresh one. That didn't happen - the program apparently needs to find one to update. Once I gave it one to find things look better but the cgminer error has taken a new twist. The mining module window appeared and seemed normal. After the usual delay, a DOS-style window appears briefly (the cgminer), as it always did, but in the moment it is visible I think I saw a message that it was going to close. Normally, I would bring it back with the "Show CG Miner" button, but that does not work in this case. I see a new message at the bottom of the mining module window: "Process has exited, so the requested information is not available."

Getting closer. Still digging. Probably my error, not yours. Sigh.

Edit: update - On an impulse, I asked it to create a cgminer instance again. "Success" reported, miner window appeared, everything looks normal. Now I just have to bring it all up to the latest version again without breaking anything.

Edit: final update (I promise). Everything is fine now. The cgminer version is 3.4.0 so I know it's updated (I had been using 3.1.0 for Gridcoin since I started). The cause of the original problem remains a puzzle but is probably on my end. "When you're up to your ass in alligators, it's hard to remember that your original objective was to drain the swamp." Sorry for the hassle!


hero member
Activity: 644
Merit: 500
P2P The Planet!
Cgminer0 doesnt show anything on the mining module for me only Cgminer1. However they are both hashing, so i just let it be.
sr. member
Activity: 364
Merit: 252
New Version Available:
7.7.5/1.1.5.6: Upgrade from RPC: Yes

* In this version we fix the bug where the CPU Miners outstanding amount owed is not being updated; therefore outstanding payments are not correct.
Note: The Next Payment Amount is still too small, and continuing to bloat the wallet, but we cannot fix this until everyone upgrades to this version; we will
fix that in 1.1.5.7, ASAP.

** Please move to this version if you are poolmining as soon as possible, as it is a prerequisite for us to fix the cpumining outstanding payment amount value **
 

I'm solo GPUmining. This version appears to have lost the ability to find the cgminer0 folder within the Appdata Roaming Gridcoin folder. The mining module console finds no instance, even though the files all seem intact. The configuration tab offers me a chance to make a new instance but warns that it will replace the old one, and since the old one looks fine I chickened out from doing it.

The wallet seems fine but no mining takes place.

Edit: Update - I renamed the existing cgminer0 folder to I could try creating a new instance from the configuration tab. The Device Id looks OK (Tahiti). I get the warning that it will replace the cgminer0 folder. When I OK that, an error message appears - "Conversion from string '''' to type 'Long' is not valid" - error while creating CGMiner instance. So - no miner, no mining.






That seems extremely strange and I haven't heard this from anyone; one thing you can do is rollback to the prior EXE and test it; but first: Im using cgm0 and its finding mine; also that string conversion bug only happens if you leave a field blank on the mining config screen; try pulling up each card instances config, verify every field is filled in and click save, then do the create new instance; it should be working.

Good luck,
Grid
legendary
Activity: 1450
Merit: 1013
Cryptanalyst castrated by his government, 1952
New Version Available:
7.7.5/1.1.5.6: Upgrade from RPC: Yes

* In this version we fix the bug where the CPU Miners outstanding amount owed is not being updated; therefore outstanding payments are not correct.
Note: The Next Payment Amount is still too small, and continuing to bloat the wallet, but we cannot fix this until everyone upgrades to this version; we will
fix that in 1.1.5.7, ASAP.

** Please move to this version if you are poolmining as soon as possible, as it is a prerequisite for us to fix the cpumining outstanding payment amount value **
 

I'm solo GPUmining. This version appears to have lost the ability to find the cgminer0 folder within the Appdata Roaming Gridcoin folder. The mining module console finds no instance, even though the files all seem intact. The configuration tab offers me a chance to make a new instance but warns that it will replace the old one, and since the old one looks fine I chickened out from doing it.

The wallet seems fine but no mining takes place.

Edit: Update - I renamed the existing cgminer0 folder to I could try creating a new instance from the configuration tab. The Device Id looks OK (Tahiti). I get the warning that it will replace the cgminer0 folder. When I OK that, an error message appears - "Conversion from string '''' to type 'Long' is not valid" - error while creating CGMiner instance. So - no miner, no mining.


legendary
Activity: 1260
Merit: 1001
I think ever since the network hashrate increased to 100 mhash there are a lot more stales now. I think because there is a lot more people hashing there is a greater chance that someone else discovers the block before you do. So if someone else beats you to it, you get a stale. I think the sleep algo will improve that because instead of competing so much, you can do Boinc work while there others are hashing, and then when your turn comes you won't get as many stales. I think that is the way the sleep algorithm for Gridcoin will work.

Hello guys!  I'm using the guiminer scrypt with r9-290 and got for 24 hours mining 6 accepted and 15 stale, is that normal? If not how to reduce the stale rate? Both GPU are at intensity 18 and 24550 concurrency
legendary
Activity: 1450
Merit: 1013
Cryptanalyst castrated by his government, 1952
I just noticed Gridcoin is writing HUGE debug log files in the Appdata Roaming Gridcoin directory. For example: debug.log which might be a backup is 4,505 KB and debug2.log which is being added to in real time is now 2,328,818 KB - over 2.3 gig and growing. I don't think I've ever turned on logging when running Gridcoin.

Also, I notice that recent versions have added a line to gridcoin.conf that says UpdatingLeaderboard=false which might explain why the leaderboard screens show nothing on my system for the last few days. My old backup gridcoin.conf files don't have that line and I'm pretty sure I did not insert it manually, but my head is spinning with all the

I apologize for the slow response; still out of town due to a family member emergency;
Yes, the debug.log is too big; it has some unnecessary garbage in there to debug the cpumining issue; We will remove that ASAP; in the next week keep deleting it before you boot; Sorry for the inconvenience.
Regarding that key in the config; Gridcoin will update it automatically; if your SQL is not syncing delete the SQL folder and start over; It seems to be working now.

Thanks,
Grid


Cool - thanks for that. I'll test the new version now that I know what's up.
sr. member
Activity: 364
Merit: 252
New Version Available:
7.7.5/1.1.5.6: Upgrade from RPC: Yes

* In this version we fix the bug where the CPU Miners outstanding amount owed is not being updated; therefore outstanding payments are not correct.
Note: The Next Payment Amount is still too small, and continuing to bloat the wallet, but we cannot fix this until everyone upgrades to this version; we will
fix that in 1.1.5.7, ASAP.

** Please move to this version if you are poolmining as soon as possible, as it is a prerequisite for us to fix the cpumining outstanding payment amount value **




 
sr. member
Activity: 364
Merit: 252
I just noticed Gridcoin is writing HUGE debug log files in the Appdata Roaming Gridcoin directory. For example: debug.log which might be a backup is 4,505 KB and debug2.log which is being added to in real time is now 2,328,818 KB - over 2.3 gig and growing. I don't think I've ever turned on logging when running Gridcoin.

Also, I notice that recent versions have added a line to gridcoin.conf that says UpdatingLeaderboard=false which might explain why the leaderboard screens show nothing on my system for the last few days. My old backup gridcoin.conf files don't have that line and I'm pretty sure I did not insert it manually, but my head is spinning with all the

I apologize for the slow response; still out of town due to a family member emergency;
Yes, the debug.log is too big; it has some unnecessary garbage in there to debug the cpumining issue; We will remove that ASAP; in the next week keep deleting it before you boot; Sorry for the inconvenience.
Regarding that key in the config; Gridcoin will update it automatically; if your SQL is not syncing delete the SQL folder and start over; It seems to be working now.

Thanks,
Grid
hero member
Activity: 1666
Merit: 565

thx for the link!

i would ask the devs if they can add "world community grid" to the list of the projects Smiley
as inappropriate as language can get Smiley

ops grid :v
legendary
Activity: 1450
Merit: 1013
Cryptanalyst castrated by his government, 1952
I just noticed Gridcoin is writing HUGE debug log files in the Appdata Roaming Gridcoin directory. For example: debug.log which might be a backup is 4,505 KB and debug2.log which is being added to in real time is now 2,328,818 KB - over 2.3 gig and growing. I don't think I've ever turned on logging when running Gridcoin.

Also, I notice that recent versions have added a line to gridcoin.conf that says UpdatingLeaderboard=false which might explain why the leaderboard screens show nothing on my system for the last few days. My old backup gridcoin.conf files don't have that line and I'm pretty sure I did not insert it manually, but my head is spinning with all the changes.           Smiley

Is this stuff normal? It seems odd to me.

Edit: Details - current version v1.1.5.5-g71-prod, obtained from the msi, installed less than an hour ago, running on Win7 64.


Bump and update.

I removed the log files from the Appdata Roaming Gridcoin folder and took the "UpdatingLeaderboard=false" line out of gridcoin.conf then started gridcoin-qt fresh. It generated a new pair of log files and it added the "UpdatingLeaderboard=false" line back into gridcoin.conf.

With that level of unexplained I/O overhead, I won't test gridcoin further for a while.
 

newbie
Activity: 52
Merit: 0

thx for the link!

i would ask the devs if they can add "world community greed" to the list of the projects Smiley
as inappropriate as language can get Smiley
hero member
Activity: 1666
Merit: 565

thx for the link!

i would ask the devs if they can add "world community grid" to the list of the projects Smiley
newbie
Activity: 36
Merit: 0
hero member
Activity: 1666
Merit: 565
New Version Available: 7.74/1.1.5.5: Upgrade from the RPC :  Yes

*  CPU Mining is enabled in this version with up to 150grc payout per cpu-only miner per day.

Best Regards,
Grid

Does it make sense to CPU mine with a weak CPU (Core i3) ? How many GRC can I expect to earn at this stage, approximately?

It is a little bit upset that you release a CPU mining version without explaining how it works.

how can i start cpu mining?
full member
Activity: 124
Merit: 100
New Version Available: 7.74/1.1.5.5: Upgrade from the RPC :  Yes

*  CPU Mining is enabled in this version with up to 150grc payout per cpu-only miner per day.

Best Regards,
Grid

Does it make sense to CPU mine with a weak CPU (Core i3) ? How many GRC can I expect to earn at this stage, approximately?

It is a little bit upset that you release a CPU mining version without explaining how it works.
hero member
Activity: 709
Merit: 500
Gridcoin Foundation
Hello guys!  I'm using the guiminer scrypt with r9-290 and got for 24 hours mining 6 accepted and 15 stale, is that normal? If not how to reduce the stale rate? Both GPU are at intensity 18 and 24550 concurrency
newbie
Activity: 32
Merit: 0
I updated to the latest client 1.1.5.5 -g71 and am in the process of transferring from a bloated old wallet A to a new wallet B. The problem is when I tried to send 5K across, it remained as "unconfirmed" in wallet B for a whole day now. When I tried to use a back-up of wallet A, it does not even show the transaction after syncing up to the latest. Ever since then, when I tried to send again from wallet A, it does not even show up in wallet B. Any idea how to resolve this?
Jump to: