PatMan
|
|
June 15, 2014, 10:09:45 PM |
|
Any chance of getting a fix for building the daemon on 14.04?
|
|
|
|
|
|
"There should not be any signed int. If you've found a signed int
somewhere, please tell me (within the next 25 years please) and I'll
change it to unsigned int." -- Satoshi
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
PatMan
|
|
June 15, 2014, 10:47:17 PM |
|
Cool, thanks. It's a bummer when people can't use it on the latest version which everyone will be using sooner or later
|
|
|
|
JoeGruff
Member
Offline
Activity: 67
Merit: 10
|
|
June 15, 2014, 11:04:12 PM |
|
14.04 is the Ubuntu version?
Is anyone running the daemon on a different distro? Am I alone?
|
|
|
|
PatMan
|
|
June 15, 2014, 11:07:01 PM |
|
14.04 is the Ubuntu version?
Is anyone running the daemon on a different distro? Am I alone?
Yes, Yes & No
|
|
|
|
JoeGruff
Member
Offline
Activity: 67
Merit: 10
|
|
June 16, 2014, 01:24:04 AM |
|
Compiled!
|
|
|
|
|
IYFTech
|
|
June 16, 2014, 07:39:15 AM |
|
Worked a treat for me on the pre-fork version - good work & thanks to JoeGruff for the fix Is HUC on the new fork yet? If so, I'll try it on the new version......
|
|
|
|
BayAreaCoins
Legendary
Offline
Activity: 3920
Merit: 1242
Owner at AltQuick.com & FreeBitcoins.com
|
|
June 16, 2014, 07:55:06 AM |
|
Worked a treat for me on the pre-fork version - good work & thanks to JoeGruff for the fix Is HUC on the new fork yet? If so, I'll try it on the new version...... Thanks Joe 72246198bb1f868c2f3259b7428774b76d34ca38be2dc4a0d0becc4a202f9658 Another 300 for you good sir!
|
|
|
|
JoeGruff
Member
Offline
Activity: 67
Merit: 10
|
|
June 16, 2014, 08:53:20 AM Last edit: June 16, 2014, 09:14:39 AM by JoeGruff |
|
While it did compile, I'm not so sure that it's working right... The size of the folder it's in keeps going from 2.0 to 2.1 and I can't seem to send the daemon any commands. Been like this for a while now... Oh, this is embarrasing. My hard drive was at 99% capacity. Guess that's why.
|
|
|
|
snailbrain (OP)
Legendary
Offline
Activity: 1807
Merit: 1020
|
|
June 16, 2014, 12:00:14 PM |
|
|
|
|
|
vleroybrown
|
|
June 16, 2014, 12:07:02 PM |
|
For the none tech wizards out there, is there a clear guide on how to start with this and the new forked client to move our existing coins over from the slow wallet?
|
|
|
|
snailbrain (OP)
Legendary
Offline
Activity: 1807
Merit: 1020
|
|
June 16, 2014, 12:31:24 PM Last edit: June 16, 2014, 06:24:06 PM by snailbrain |
|
For the none tech wizards out there, is there a clear guide on how to start with this and the new forked client to move our existing coins over from the slow wallet? wallet will still be "slow", domob will start working on performance stuff later if you trust my upload, you can just backup your wallet.dat delete everything from the wallet directory (except huntercoin.conf if you have one) unzip the contents of the zip into that folder copy wallet.dat back run the new client like you did the old one.
|
|
|
|
PatMan
|
|
June 16, 2014, 04:11:09 PM |
|
Su Sure does my man!! Kudos to you, domob & JoeGruff for sorting it out
|
|
|
|
tiddy
|
|
June 16, 2014, 04:18:08 PM |
|
how about the one of dev dead?
|
|
|
|
|
-Greed-
|
|
June 16, 2014, 07:31:26 PM Last edit: June 16, 2014, 08:41:32 PM by -Greed- |
|
if you trust my upload, you can just
backup your wallet.dat delete everything from the wallet directory (except huntercoin.conf if you have one) unzip the contents of the zip into that folder copy wallet.dat back run the new client like you did the old one.
Tried to update following these instructions but no luck. I'm getting error when I start huntercoin-qt.exe (Windows 7 x64): http://i62.tinypic.com/fvffh0.jpgThere's db.log and there is debug.log too: file wallet.dat has LSN 22/63067595, past end of log at 1/35309 Commonly caused by moving a database from one database environment to another without clearing the database LSNs, or by removing all of the log files from a database environment DB_ENV->log_flush: LSN of 22/63067595 past current end-of-log of 1/35309 Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment PANIC: DB_RUNRECOVERY: Fatal error, run database recovery wallet.dat: unable to flush page: 7 PANIC: fatal region error detected; run recovery game.dat: write failed for page 1 game.dat: unable to flush page: 1 txn_checkpoint: failed to flush the buffer cache: DB_RUNRECOVERY: Fatal error, run database recovery file wallet.dat has LSN 22/63067595, past end of log at 1/37381 Commonly caused by moving a database from one database environment to another without clearing the database LSNs, or by removing all of the log files from a database environment DB_ENV->log_flush: LSN of 22/63067595 past current end-of-log of 1/37381 Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment PANIC: DB_RUNRECOVERY: Fatal error, run database recovery wallet.dat: unable to flush page: 7 PANIC: fatal region error detected; run recovery game.dat: write failed for page 1 game.dat: unable to flush page: 1 txn_checkpoint: failed to flush the buffer cache: DB_RUNRECOVERY: Fatal error, run database recovery
huntercoin version 1.0.11 Default data directory C:\Users\admin\AppData\Roaming\Huntercoin Bound to port 8398 Setup huntercoin genesis block 00000000db7eb7a9e1a06cf995363dcdc4c28e8ae04827a961942657db9a1631 Loading addresses... dbenv.open strLogDir=C:\Users\admin\AppData\Roaming\Huntercoin/database strErrorFile=C:\Users\admin\AppData\Roaming\Huntercoin/db.log Loaded 0 addresses addresses 20935ms Loading block index... LoadBlockIndex(): hashBestChain=fa7d7b406b6e2f5f4538 height=226661 block index 4420ms Loading wallet... nFileVersion = 1000700 Update: When I run client without wallet.dat it starts syncing and doesn't show any kind of errors. Update #2: I have resolved my issue by exporting & importing private keys into new wallet.
|
|
|
|
mikeyfinn
|
|
June 16, 2014, 07:44:09 PM Last edit: June 16, 2014, 08:04:40 PM by mikeyfinn |
|
Ok, so I downloaded the latest chain, got synced, restored wallet. Closed wallet. Later (now) I opened the Mithrilman client..... it has now asked 3 times for the daily 1 HUC, and after a minute the window pops up again.....
I just reopened the regular wallet and it shows 3 single HUC transactions to the address, so clearly they are going, but somehow the client thinks I am expired. Regular wallet fine so far....
|
Bitcoin: 1KZr3AvQ3m8NWEGbBPzFMFXbzHxpCbkbv4 Huntercoin: HQWSihm1WPJfjdPbeLfdVc6nsqrnJW5fYR Sync: Si1MjELBXaffuNgEN4Zd3PkM9qzu9pq5k5
|
|
|
mikeyfinn
|
|
June 16, 2014, 09:06:22 PM |
|
Ok, so I downloaded the latest chain, got synced, restored wallet. Closed wallet. Later (now) I opened the Mithrilman client..... it has now asked 3 times for the daily 1 HUC, and after a minute the window pops up again.....
I just reopened the regular wallet and it shows 3 single HUC transactions to the address, so clearly they are going, but somehow the client thinks I am expired. Regular wallet fine so far....
On the 3rd retry, I am finally in!
|
Bitcoin: 1KZr3AvQ3m8NWEGbBPzFMFXbzHxpCbkbv4 Huntercoin: HQWSihm1WPJfjdPbeLfdVc6nsqrnJW5fYR Sync: Si1MjELBXaffuNgEN4Zd3PkM9qzu9pq5k5
|
|
|
mikeyfinn
|
|
June 16, 2014, 09:36:22 PM |
|
Ok, so I downloaded the latest chain, got synced, restored wallet. Closed wallet. Later (now) I opened the Mithrilman client..... it has now asked 3 times for the daily 1 HUC, and after a minute the window pops up again.....
I just reopened the regular wallet and it shows 3 single HUC transactions to the address, so clearly they are going, but somehow the client thinks I am expired. Regular wallet fine so far....
On the 3rd retry, I am finally in! HuntercoinMithrlEdition:Object reference not set to an instance of an object.
|
Bitcoin: 1KZr3AvQ3m8NWEGbBPzFMFXbzHxpCbkbv4 Huntercoin: HQWSihm1WPJfjdPbeLfdVc6nsqrnJW5fYR Sync: Si1MjELBXaffuNgEN4Zd3PkM9qzu9pq5k5
|
|
|
|