 Show Posts
|
|
Pages: [1] 2 3 4 »
|
|
I found the location but I haven't been able to figure out how to change it in the app. Every other wallet I've used prompts you for wallet location the first time you open the app, and any time you open it and it can't find your wallet. But Gridcoin does not, and I really want to put my wallets in a specific location. Any ideas?
|
|
|
|
I've mined bitcoin, litecoin and doge in the past. I haven't mined anything in a while ago. Then recently, I heard about Gridcoin. Which is funny because I've been using BOINC for years. Yet I never heard about GRC. They need a better publicist. But anyway... I have two very related questions. The second question is: How often will I get coins if I mine solo? I know this all depends on what hardware I run, but I don't fully understand how mining works in this unusual system. I have one mac pro running, with four xeon cpu cores and one few-year-old high end GPU. I'm running a wide variety of whitelist projects. I am mining solo with just this machine. In what sized 'packets' are goings awarded, and how often am I likely to get a pack? Days? Weeks? Months? Decades? Also I'm not sure I have things set up right. BOINC is running just fine as always. I've joined the Gridcoin group on every project. And I have a fully sync'd up wallet set up on my boinc email address. I've been running like this for a week or two with no coins. But more than that, I'm still getting weird messages from my empty wallet. I'm not sure if this is normal or of this means there's a problem? Things like: Client Messages: No coins to stake; Unable to send Beacon! Unlock Wallet! Not staking; no coins to stake Client Messages: Net averages not yet loaded; Unable to Send Beacon! Unlock Wallet! |
|
|
|
|
Not sure if this is a good place for Gridcoin questions, but I figured it's worth a shot.
I have a machine I've already been running BOINC on for 10 years off and on (usually just during the Winter). I just today found out about Gridcoin. So i downloaded the wallet. But unlike every other wallet I've used, this one did not ask me where on my filesystem I'd like to create my blockchain/wallet folder. Sooooo anyone know where it's located? And how I can move it? I also use this machine for my wallets, and I like to keep all the blockchains in a unified, easy to access location since they are so unwieldy. And of course I need to back up the wallet files.
|
|
|
|
|
I found a wallet.dat file in my documents folder. I'm sure it's mine, but I don't know why I put it there, and I have no idea which currency it's for. I've used several over the years, and these coins are most likely sitting in my wallet right now already. But I'd like to figure out which currency they are from, without downloading wallets and syncing blockchains from everything I've ever tried. Any ideas?
|
|
|
|
There is something wrong with the wallet.dat file. On all of the systems where you have been seeing a problem, have you been copying the same wallet.dat file to each of them and trying to load it there?
So I have many backups of the wallet from many different times, and they all have had problems. But last night I dug deep and found one backup of my wallet from April 2016 and this was BEFORE the corruption, and it is working normally! Lucky me. Once it runs for a while without any problems, I can start backing up that current working wallet and toss all these other ones I have all over the place. I'm having a similar problem with my dogecoin wallet but seeing as how the windows bitcoin wallet syncs to the blockchain in 2 days, and the mac bitcoin wallet syncs to the blockchain in 2 months, i'm going to acquire a bigger hard drive and run both wallets on windows instead, then I can try to figure out how to get those dogecoins back. But for now that's on hold. Glad to have this wallet back though. To everyone that just stuck with "your computer or hard drive are broken", making up answers to peoples problems doesn't help anyone. |
|
|
|
Here's another debug log from a slightly older backup of my wallet. This in the previous logs are from Windows bitcoin. I have the same problem with bitcoin on Mac. My best guess is the Mac bitcoin wallet has some kind of fatal bugs in it that poisons the wallet.data file in some way. 2017-10-26 09:11:37
2017-10-26 09:11:37 Bitcoin version v0.15.0.1
2017-10-26 09:11:37 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-10-26 09:11:50 Assuming ancestors of block 0000000000000000003b9ce759c2a087d52abc4266f8f4ebd6d768b89defa50a have valid signatures.
2017-10-26 09:11:51 Using the 'standard' SHA256 implementation
2017-10-26 09:11:53 Default data directory C:\Users\xxxxxx\AppData\Roaming\Bitcoin
2017-10-26 09:11:53 Using data directory C:\Users\xxxxxx\Desktop\Bitcoin Wallet
2017-10-26 09:11:53 Using config file C:\Users\xxxxxx\Desktop\Bitcoin Wallet\bitcoin.conf
2017-10-26 09:11:53 Using at most 125 automatic connections (2048 file descriptors available)
2017-10-26 09:11:53 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
2017-10-26 09:11:53 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2017-10-26 09:11:53 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2017-10-26 09:11:53 Using 4 threads for script verification
2017-10-26 09:11:54 scheduler thread start
2017-10-26 09:11:54 init message: Verifying wallet(s)...
2017-10-26 09:11:54 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2017-10-26 09:11:54 Using wallet wallet.dat
2017-10-26 09:11:54 CDBEnv::Open: LogDir=C:\Users\xxxxxx\Desktop\Bitcoin Wallet\database ErrorFile=C:\Users\xxxxxx\Desktop\Bitcoin Wallet\db.log
2017-10-26 09:11:57 Cache configuration:
2017-10-26 09:11:57 * Using 2.0MiB for block index database
2017-10-26 09:11:57 * Using 8.0MiB for chain state database
2017-10-26 09:11:57 * Using 290.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2017-10-26 09:11:57 init message: Loading block index...
2017-10-26 09:11:58 Opening LevelDB in C:\Users\xxxxxx\Desktop\Bitcoin Wallet\blocks\index
2017-10-26 09:11:59 Opened LevelDB successfully
2017-10-26 09:11:59 Using obfuscation key for C:\Users\xxxxxx\Desktop\Bitcoin Wallet\blocks\index: 0000000000000000
2017-10-26 09:12:23 LoadBlockIndexDB: last block file = 1042
2017-10-26 09:12:23 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=96, size=69957200, heights=491713...491822, time=2017-10-25...2017-10-26)
2017-10-26 09:12:23 Checking all blk files are present...
2017-10-26 09:12:28 LoadBlockIndexDB: transaction index disabled
2017-10-26 09:12:28 Opening LevelDB in C:\Users\xxxxxx\Desktop\Bitcoin Wallet\chainstate
2017-10-26 09:12:28 Opened LevelDB successfully
2017-10-26 09:12:28 Using obfuscation key for C:\Users\xxxxxx\Desktop\Bitcoin Wallet\chainstate: dc3087dba2ad642e
2017-10-26 09:12:28 Loaded best chain: hashBestChain=00000000000000000080d70ed46b5f912ea0f0ba22c0d097be52c0fb8586e2b7 height=491822 date=2017-10-26 08:42:16 progress=0.999979
2017-10-26 09:12:28 init message: Rewinding blocks...
2017-10-26 09:12:32 init message: Verifying blocks...
2017-10-26 09:12:32 Verifying last 6 blocks at level 3
2017-10-26 09:12:32 [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
2017-10-26 09:14:31 No coin database inconsistencies in last 7 blocks (7711 transactions)
2017-10-26 09:14:31 block index 153863ms
2017-10-26 09:14:31 init message: Loading wallet...
2017-10-26 09:14:31 nFileVersion = 130000
2017-10-26 09:14:31 Keys: 113 plaintext, 0 encrypted, 7 w/ metadata, 113 total
2017-10-26 09:14:32 wallet 515ms
2017-10-26 09:14:32
************************
EXCEPTION: St13runtime_error
GenerateNewKey: AddKey failed
C:\Program Files\Bitcoin\bitcoin-qt.exe in Runaway exception
2017-10-26 09:14:38 CDBEnv::EnvShutdown: Error -30974 shutting down database environment: DB_RUNRECOVERY: Fatal error, run database recovery
|
|
|
|
2017-10-26 08:46:19
2017-10-26 08:46:19 Bitcoin version v0.15.0.1
2017-10-26 08:46:19 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-10-26 08:46:19 Assuming ancestors of block 0000000000000000003b9ce759c2a087d52abc4266f8f4ebd6d768b89defa50a have valid signatures.
2017-10-26 08:46:19 Using the 'standard' SHA256 implementation
2017-10-26 08:46:20 Default data directory C:\Users\xxxxxx\AppData\Roaming\Bitcoin
2017-10-26 08:46:20 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
2017-10-26 08:46:20 Using data directory C:\Users\xxxxxx\Desktop\Bitcoin Wallet
2017-10-26 08:46:20 Using config file C:\Users\xxxxxx\Desktop\Bitcoin Wallet\bitcoin.conf
2017-10-26 08:46:20 Using at most 125 automatic connections (2048 file descriptors available)
2017-10-26 08:46:20 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2017-10-26 08:46:20 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2017-10-26 08:46:20 Using 4 threads for script verification
2017-10-26 08:46:20 init message: Verifying wallet(s)...
2017-10-26 08:46:20 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2017-10-26 08:46:20 Using wallet wallet.dat
2017-10-26 08:46:20 CDBEnv::Open: LogDir=C:\Users\xxxxxx\Desktop\Bitcoin Wallet\database ErrorFile=C:\Users\xxxxxx\Desktop\Bitcoin Wallet\db.log
2017-10-26 08:46:20 scheduler thread start
2017-10-26 08:46:20 Cache configuration:
2017-10-26 08:46:20 * Using 2.0MiB for block index database
2017-10-26 08:46:20 * Using 8.0MiB for chain state database
2017-10-26 08:46:20 * Using 290.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2017-10-26 08:46:20 init message: Loading block index...
2017-10-26 08:46:20 Opening LevelDB in C:\Users\xxxxxx\Desktop\Bitcoin Wallet\blocks\index
2017-10-26 08:46:21 Opened LevelDB successfully
2017-10-26 08:46:21 Using obfuscation key for C:\Users\xxxxxx\Desktop\Bitcoin Wallet\blocks\index: 0000000000000000
2017-10-26 08:46:32 LoadBlockIndexDB: last block file = 1042
2017-10-26 08:46:32 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=96, size=69957200, heights=491713...491822, time=2017-10-25...2017-10-26)
2017-10-26 08:46:32 Checking all blk files are present...
2017-10-26 08:46:33 LoadBlockIndexDB: transaction index disabled
2017-10-26 08:46:33 Opening LevelDB in C:\Users\xxxxxx\Desktop\Bitcoin Wallet\chainstate
2017-10-26 08:46:33 Opened LevelDB successfully
2017-10-26 08:46:33 Using obfuscation key for C:\Users\xxxxxx\Desktop\Bitcoin Wallet\chainstate: dc3087dba2ad642e
2017-10-26 08:46:33 Loaded best chain: hashBestChain=00000000000000000080d70ed46b5f912ea0f0ba22c0d097be52c0fb8586e2b7 height=491822 date=2017-10-26 08:42:16 progress=0.999997
2017-10-26 08:46:33 init message: Rewinding blocks...
2017-10-26 08:46:38 init message: Verifying blocks...
2017-10-26 08:46:38 Verifying last 6 blocks at level 3
2017-10-26 08:46:38 [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
2017-10-26 08:46:42 No coin database inconsistencies in last 7 blocks (7711 transactions)
2017-10-26 08:46:42 block index 21591ms
2017-10-26 08:46:42 init message: Loading wallet...
2017-10-26 08:46:42 nFileVersion = 130000
2017-10-26 08:46:42 Keys: 113 plaintext, 0 encrypted, 7 w/ metadata, 113 total
2017-10-26 08:46:42 wallet 327ms
2017-10-26 08:46:42
************************
EXCEPTION: St13runtime_error
GenerateNewKey: AddKey failed
C:\Program Files\Bitcoin\bitcoin-qt.exe in Runaway exception
2017-10-26 08:46:49 CDBEnv::EnvShutdown: Error -30974 shutting down database environment: DB_RUNRECOVERY: Fatal error, run database recovery
|
|
|
|
|
Ok after re-opening the dogecoin core wallet a bunch of times (after -salvagewallet) suddenly all my coins are back. But so is the problem where the wallet app crashes after running for a little while.
This is on a brand new machine, freshly synced to the dogecoin block chain, this is not a hardware issue.
On to bitcoin, I did the same thing and the new salvaged wallet is just blank. It is also on this new machine, freshly sync'd to the blockchain. The app isn't crashes but if I swap in my old corrupt wallet, it starts crashing again. If salvagewallet is broken on bitcoincore, how do I get my coins out?
And a more important question, why is it that every wallet I use goes bad? Are these wallets just not compatible with OS X? I used to keep them running in the background on my main desktop, which basically never crashes, and we very rarely have power outages. And yet, nothing but problems. Should I be running these wallets on windows instead? That will be inconvenient but if the wallet apps are more stable, I'll do it if I have to.
|
|
|
|
|
I'm back and trying to get this going again. I just tried -salvagewallet for the first time (this on dogecoin.app, not bitcoin yet).
This is on a new machine with new versions of the apps, freshly synced to their respective blockchains (which took about 2 months for bitcoin).
So I ran -salvagewallet on my dogecoin wallet. It did something that didn't take very long at all. Then after a minute or so, it quit and left me with wallet.242340234.back and wallet.dat. So I fired up dogecoin core.app and once it rescanned everything, I had..... an empty wallet. Which kind of makes sense since the .bak wallet was 12 MB and the new one, presumably the restored one, was a few KB.
Am I doing something wrong here? There's almost no instructions on the web for how to use the -salvagewallet feature, beyond "just use -salvagewellet".
|
|
|
|
|
I am not @OP, but I used google and found the suggested link BEFORE I found this thread, and many many others. And I have yet to find anything that really explains in detail what salvagewallet does, and how you actually get old coins out of a corrupt wallet with it, and into a fresh wallet. I'll keep searching but most of what you get with a google search is "i tried salvagewallet and it didn't work, now what?"
|
|
|
|
Computer A: wallet.dat is corrupted, you should :
(found for windows)
1) create a folder named protoalt and keep it's path in mind
2)Copy all the files except your wallet.dat into the new folder
3) Create a .bat .sh to start the alternate you have created
3)start your client with -salvagewallet, this does exactly that.
4) once your wallet is recovered, start the alternate client, it will create a new wallet for you.
5) send coins to new wallet and use it as main one now.
Computer B: Database corruption, relaunch core with reindex=1 in bitcoin.conf and try it.
These are brand new wallets, I'm trying to get the app to sync from scratch, totally clean and fresh. I do have my old wallet files but this is before I even get to the point of trying to get at those coins. |
|
|
|
|
Oh and other wallets sync up and stay synced no problem. Litecoin, Dogecoin core wallets both never had a problem. It's only bitcoin, and it's every time it tries to sync up.
|
|
|
|
|
Well i can't speak for the log, but the application itself gave me multiple different error dialog windows as it was crashing. It may very well have all been from the same cause. This is what has been happening any time I try to sink up the bitcoin wallet on any Mac. Has ANYONE been able to run bitcoin core on Mac lately? I'm suspecting it is a problem with the application itself. It always makes it to about this point then fails. Among the many reasons I know its now a hardware problem with the Mac, is that if it were, it would happen at random times. Plus the fact that I use this computer all day every day and it has no problems, even when it's doing intensive work, of which this bitcoin wallet absolutely is not.
|
|
|
|
Ok here we go... Computer A: An i5 Mac mini running 10.12.3 and 4 GB of RAM. You say 4 GB isn't enough, but the memory pressure never gets outside of the green zone, so this must be crashing long before RAM becomes a factor. This one doesn't crash, it just goes unresponsive and never comes back. Log Snippet: http://pastebin.com/DcR0kwCtComputer B: An i7 quad core Mac mini running 10.12.3 with 16 GB of RAM. This one crashes hard with lots of application errors on it's way out. Log Snippet: http://pastebin.com/5KUWYgckThat's all I have. My other computers are i5 laptops very similar to computer A. I have one older Mac Pro with 20 GB of RAM and xeon CPUs, but Bitcoin Core requires 10.8 or newer, and that old Mac can only run 10.7. |
|
|
|
|
Im generating debug logs from both machines. The app on the 4 GB machine doesn't crash so much as it just freezes solid, and I mean solid. Repeatably. But I don't think it's a RAM issue, as only about half the RAM is even in use. Very low "memory pressure".
I'm running the other Mac now, syncing up the block chain from scratch with a fresh wallet. This will take a few days, I'll return with more into once this is done.
|
|
|
|
|
That file is pretty big for a text file so I'm going to start a fresh one, let the app crash again, then repost when that's done... hopefully tomorrow.
As far as hardware, I can assure you it's not a hardware issue. My Macs are having no problems whatsoever, other than bitcoin. And bitcoin wallets are NOT that resources intensive. I do photoshop work that uses tons of memory and maxes out most of my CPU. Bitcoin is a lightweight compared to that.
But to answer your question, one of the computers has 16 GB of RAM, the other has 4 GB.
One is a dual core i5, the other is a quad core i7.
Both are 2012 Mac minis with intel HD 4000 graphics.
I don't have any kind of active firewall, just a standard router.
|
|
|
|
|
Ok now I really don't know what to do. Even version 0.14 will crash before it gets finished syncing to the network. Its a totally new wallet on a totally new machine and it can't sync up.
|
|
|
|
|
I know my computer has no hardware issues, but just for shits and giggles I opened up a totally fresh bitcoin wallet using bitcoin core on a machine that has never run bitcoin before. It too gets errors and fails before getting fully synced up. This is version .13.2. I do see that there is a version .14, i'll try that and see if I have any better luck.
|
|
|
|
|
So back in November, my bitcoin walled (just the basic bitcoin core) give me an error that the chain was corrupt or something along those lines. I thought, 'no big deal, just re-sync up'. But every time I've tried to get it to re-sync, it gets so far then fails again. Even if I start with a totally fresh wallet and no app prefs etc. This is on the latest version of OS X.
Has anyone else had this problem lately? Is it a known issue or is it just me? Any ideas how to fix it?
|
|
|
|
I've got a small pc with two R9 270 GPUs in it. I have previously mined LTC and DOGE with it, and it all went well. I put the machine on craigslist because I'm kind of over this whole mining thing, however... And I'm not kidding... my office is now FREEZING without that heat source! It's almost spring, so I figured I'd get the GPU's going on SOMETHING until it sells. And I've settled on DRK just for something new. So after much fiddling, I got sgminer running. But it only runs on one GPU. The other one gets a hash rate of 0, then after a few minutes, shows as "SICK". A few minutes after that, it shows as "DEAD". But I know its not dead, it is working. It ran like a champ for a year mining litecoins. I do have the most recent drivers. And I tried running with a very low intensity. But it doesn't even run for a second. It starts at 0 and stays there. The other card gets around 1.2mh/s. I'd like to get them both running at least, but I'm not sure where to go from here. These are the flags i'm using to run sgminer: sgminer.exe --gpu-platform 1 --algorithm darkcoin -o [pool-url] -u [user.worker] -p [password] -I 17
Thoughts? |
|
|
|
|
