14.04 is the Ubuntu version?
Is anyone running the daemon on a different distro? Am I alone?
Topic: [ANN][HUC] Huntercoin - Worlds First Decentralized Game/World on the Blockchain - page 176. (Read 879724 times)
June 15, 2014, 06:04:12 PM
June 15, 2014, 05: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 
June 15, 2014, 05:28:41 PM
Any chance of getting a fix for building the daemon on 14.04?
have put a 300 HUC bounty for it
http://forum.huntercoin.org/index.php?topic=104.0
June 15, 2014, 05:09:45 PM
Any chance of getting a fix for building the daemon on 14.04?
June 15, 2014, 04:29:43 PM
i'm uploading the chain - eta tomorrow. Might be best for some people to wait for that
June 15, 2014, 03:51:42 PM
my internet connection is down - using 3g atm.. i've had to halt uploading of the chain - hopefully will be sorted soon
8 GiB of what - RAM or storage directory?
For me, the upgrade (but only the upgrade, afterwards the new update actually reduces RAM usage) takes around 2.5 GiB since some part of the updating is done in memory to avoid even more slow disk accesses. But I've never seen anywhere near 8 GiB (actually, I only have 4 GiB on my system).
The disk space required is already larger than 8 GiB with and without the upgrade.
ram, 7.5 GB to be precise are being used, usually i'm at 2GB for chrome and other staff, when i started this update has shot to 7.5
edit...now 5.89 gb
not for me.. although i'm trying again now
just tried with an old chain block 151k, used 1.8gb of ram
is it still working?
my god, all my 8 giga are used, when running the new update, this is crazy
8 GiB of what - RAM or storage directory?
For me, the upgrade (but only the upgrade, afterwards the new update actually reduces RAM usage) takes around 2.5 GiB since some part of the updating is done in memory to avoid even more slow disk accesses. But I've never seen anywhere near 8 GiB (actually, I only have 4 GiB on my system).
The disk space required is already larger than 8 GiB with and without the upgrade.
ram, 7.5 GB to be precise are being used, usually i'm at 2GB for chrome and other staff, when i started this update has shot to 7.5
edit...now 5.89 gb
not for me.. although i'm trying again now
just tried with an old chain block 151k, used 1.8gb of ram
is it still working?
just at spike in the beginning, it settled down later, and declined to 2 gb total
June 15, 2014, 03:44:25 PM
Runaway exception, freeze, program close. 
run out of ram or hard drive space?
check debug.log
are you using ram drive?(make sure no typos in -datadir=xxxx)
from db.log:
page 1908552804: illegal page type or format
PANIC: Invalid argument
PANIC: fatal region error detected; run recovery
ok, back from my birthday party
I've updated daemon and started my client, and i'm experienced the same problem
I'm trying to dig in more, but it seems that since current update takes age and RPC layer isn't available, my client think the daemon is stuck and restart it
this could end in compromise the update because the update process doesn't take into consideration the eventual restart/kill of the client, or interrupted update process, leaving it in a broken status, so now i'm trying to understand what to do to recover that status, i'll update my findings.
As snailbrain already said, backup data folder before running new daemon, or you'll have to download again the blockchain if something goes wrong
UPDATE:
it seems that removing blkindex remove the error and client starts, but it's not working properly because it try to restart blockchain from start
before using my client after installing new daemon version, be sure to end the update process just starting qt wallet and when it ends, then launch my client. It's only needed first time you launch the new daemon
June 15, 2014, 01:15:11 PM
my internet connection is down - using 3g atm.. i've had to halt uploading of the chain - hopefully will be sorted soon
8 GiB of what - RAM or storage directory?
For me, the upgrade (but only the upgrade, afterwards the new update actually reduces RAM usage) takes around 2.5 GiB since some part of the updating is done in memory to avoid even more slow disk accesses. But I've never seen anywhere near 8 GiB (actually, I only have 4 GiB on my system).
The disk space required is already larger than 8 GiB with and without the upgrade.
ram, 7.5 GB to be precise are being used, usually i'm at 2GB for chrome and other staff, when i started this update has shot to 7.5
edit...now 5.89 gb
not for me.. although i'm trying again now
just tried with an old chain block 151k, used 1.8gb of ram
is it still working?
my god, all my 8 giga are used, when running the new update, this is crazy
8 GiB of what - RAM or storage directory?
For me, the upgrade (but only the upgrade, afterwards the new update actually reduces RAM usage) takes around 2.5 GiB since some part of the updating is done in memory to avoid even more slow disk accesses. But I've never seen anywhere near 8 GiB (actually, I only have 4 GiB on my system).
The disk space required is already larger than 8 GiB with and without the upgrade.
ram, 7.5 GB to be precise are being used, usually i'm at 2GB for chrome and other staff, when i started this update has shot to 7.5
edit...now 5.89 gb
not for me.. although i'm trying again now
just tried with an old chain block 151k, used 1.8gb of ram
is it still working?
June 15, 2014, 01:10:50 PM
Loading block index...
************************
EXCEPTION: NSt8ios_base7failureE
CDataStream::read() : end of data
C:\Users\MikeS\Downloads\huntercoin-1.0.11\huntercoin-qt.exe in Runaway exception
************************
EXCEPTION: NSt8ios_base7failureE
CDataStream::read() : end of data
C:\Users\MikeS\Downloads\huntercoin-1.0.11\huntercoin-qt.exe in Runaway exception
This looks like a problem with the changed storage format of blkindex.dat. However, as snailbrain said, we've tested multiple cases of database updates. So nothing strikes me immediately that could be the cause - maybe your data directory get really corrupted. But I'll test another upgrade of the old format soon (I intended to do this anyway before the hardfork, just to make sure once more).
I may have force closed. I just dropped the 200k+ blockchcain into a new folder and am trying again. No error yet, but my question is this: Will the long time loading and changing blkindex keep you with the logo up all that time, or should it show the open wallet trying to sync? I ask because I often get a freeze on 1st opening and have to force close, then on the 2nd try all is well.
yes- and on windows - you may just see the logo, or it may go white,or may just go invisible - you won't see the wallet while it's updating.. you will see huntercoin logo in system tray.. you can open debug.log during the process (if not using printtoconsole=1 with daemon). i recommend using Notepad++ .. you can keep reloading it from disk and see how the update is doing.
June 15, 2014, 12:57:28 PM
my god, all my 8 giga are used, when running the new update, this is crazy
8 GiB of what - RAM or storage directory?
For me, the upgrade (but only the upgrade, afterwards the new update actually reduces RAM usage) takes around 2.5 GiB since some part of the updating is done in memory to avoid even more slow disk accesses. But I've never seen anywhere near 8 GiB (actually, I only have 4 GiB on my system).
The disk space required is already larger than 8 GiB with and without the upgrade.
ram, 7.5 GB to be precise are being used, usually i'm at 2GB for chrome and other staff, when i started this update has shot to 7.5
edit...now 5.89 gb
June 15, 2014, 12:50:29 PM
my god, all my 8 giga are used, when running the new update, this is crazy
8 GiB of what - RAM or storage directory?
For me, the upgrade (but only the upgrade, afterwards the new update actually reduces RAM usage) takes around 2.5 GiB since some part of the updating is done in memory to avoid even more slow disk accesses. But I've never seen anywhere near 8 GiB (actually, I only have 4 GiB on my system).
The disk space required is already larger than 8 GiB with and without the upgrade.
June 15, 2014, 12:47:15 PM
UPDATE - 1.0.11 Mandatory Update (HardFork) - update before block 255k
Implement "Cleansing" - aka Poison Disaster - Disaster will first occur on the Hard Fork Block. All Generals on the Map will be infected with a plague and will be given a random life span of 1 to 50 blocks. Following disasters can happen 1440 blocks (approx 1 day) after the last
disaster. There will then be an increasing chance of disaster maxing at 12 days.
Increase General Cost - 10 HUCs per General
Remove starting Hunters - You will start with only 1 General (you can still pickup hearts for additional Hunters).
Implement "Cleansing" - aka Poison Disaster - Disaster will first occur on the Hard Fork Block. All Generals on the Map will be infected with a plague and will be given a random life span of 1 to 50 blocks. Following disasters can happen 1440 blocks (approx 1 day) after the last
disaster. There will then be an increasing chance of disaster maxing at 12 days.
Increase General Cost - 10 HUCs per General
Remove starting Hunters - You will start with only 1 General (you can still pickup hearts for additional Hunters).
Does "maxing at 12 days" means chance for a disaster at that time is 100% and does "start with only 1 General" means newly bought teams are no longer General
and 2 Soldiers but General only? 10 HUC per General is a game-changer for the better IMO, great job!
After the first day (where no disaster can happen), there's a 1/10k chance that disaster happens at each consecutive block. When it hasn't happened after 12 days in this way, it is enforced 12 * 1440 blocks after the last disaster. The new fee / team rules are that "create player" costs 10 HUC (and a general drops 9.6 HUC on death back on the map), and that you only get a lone general. (You may acquire non-general hunters by collecting hearts.)
June 15, 2014, 12:41:14 PM
Loading block index...
************************
EXCEPTION: NSt8ios_base7failureE
CDataStream::read() : end of data
C:\Users\MikeS\Downloads\huntercoin-1.0.11\huntercoin-qt.exe in Runaway exception
************************
EXCEPTION: NSt8ios_base7failureE
CDataStream::read() : end of data
C:\Users\MikeS\Downloads\huntercoin-1.0.11\huntercoin-qt.exe in Runaway exception
This looks like a problem with the changed storage format of blkindex.dat. However, as snailbrain said, we've tested multiple cases of database updates. So nothing strikes me immediately that could be the cause - maybe your data directory get really corrupted. But I'll test another upgrade of the old format soon (I intended to do this anyway before the hardfork, just to make sure once more).
I may have force closed. I just dropped the 200k+ blockchcain into a new folder and am trying again. No error yet, but my question is this: Will the long time loading and changing blkindex keep you with the logo up all that time, or should it show the open wallet trying to sync? I ask because I often get a freeze on 1st opening and have to force close, then on the 2nd try all is well.
It will show just the splash screen. You can watch progress (somewhat) in debug.log if you want to.
Note that I've just tried a successful update 1.0.07 -> 1.0.11 for an old (testnet) blockchain I had lying around. It worked fine with the code released by snailbrain (although on GNU/Linux since I don't run Windows anywhere).
June 15, 2014, 12:40:24 PM
my god, all my 8 giga are used, when running the new update, this is crazy
June 15, 2014, 12:23:06 PM
Loading block index...
************************
EXCEPTION: NSt8ios_base7failureE
CDataStream::read() : end of data
C:\Users\MikeS\Downloads\huntercoin-1.0.11\huntercoin-qt.exe in Runaway exception
************************
EXCEPTION: NSt8ios_base7failureE
CDataStream::read() : end of data
C:\Users\MikeS\Downloads\huntercoin-1.0.11\huntercoin-qt.exe in Runaway exception
This looks like a problem with the changed storage format of blkindex.dat. However, as snailbrain said, we've tested multiple cases of database updates. So nothing strikes me immediately that could be the cause - maybe your data directory get really corrupted. But I'll test another upgrade of the old format soon (I intended to do this anyway before the hardfork, just to make sure once more).
I may have force closed. I just dropped the 200k+ blockchcain into a new folder and am trying again. No error yet, but my question is this: Will the long time loading and changing blkindex keep you with the logo up all that time, or should it show the open wallet trying to sync? I ask because I often get a freeze on 1st opening and have to force close, then on the 2nd try all is well.
June 15, 2014, 12:17:46 PM
UPDATE - 1.0.11 Mandatory Update (HardFork) - update before block 255k
Implement "Cleansing" - aka Poison Disaster - Disaster will first occur on the Hard Fork Block. All Generals on the Map will be infected with a plague and will be given a random life span of 1 to 50 blocks. Following disasters can happen 1440 blocks (approx 1 day) after the last
disaster. There will then be an increasing chance of disaster maxing at 12 days.
Increase General Cost - 10 HUCs per General
Remove starting Hunters - You will start with only 1 General (you can still pickup hearts for additional Hunters).
Implement "Cleansing" - aka Poison Disaster - Disaster will first occur on the Hard Fork Block. All Generals on the Map will be infected with a plague and will be given a random life span of 1 to 50 blocks. Following disasters can happen 1440 blocks (approx 1 day) after the last
disaster. There will then be an increasing chance of disaster maxing at 12 days.
Increase General Cost - 10 HUCs per General
Remove starting Hunters - You will start with only 1 General (you can still pickup hearts for additional Hunters).
Does "maxing at 12 days" means chance for a disaster at that time is 100% and does "start with only 1 General" means newly bought teams are no longer General
and 2 Soldiers but General only? 10 HUC per General is a game-changer for the better IMO, great job!
June 15, 2014, 12:16:13 PM
I heard unluck news that one of the dev was dead,sad very much.
June 15, 2014, 12:13:23 PM
Loading block index...
************************
EXCEPTION: NSt8ios_base7failureE
CDataStream::read() : end of data
C:\Users\MikeS\Downloads\huntercoin-1.0.11\huntercoin-qt.exe in Runaway exception
************************
EXCEPTION: NSt8ios_base7failureE
CDataStream::read() : end of data
C:\Users\MikeS\Downloads\huntercoin-1.0.11\huntercoin-qt.exe in Runaway exception
This looks like a problem with the changed storage format of blkindex.dat. However, as snailbrain said, we've tested multiple cases of database updates. So nothing strikes me immediately that could be the cause - maybe your data directory get really corrupted. But I'll test another upgrade of the old format soon (I intended to do this anyway before the hardfork, just to make sure once more).
June 15, 2014, 10:51:12 AM
Runaway exception, freeze, program close.
run out of ram or hard drive space?
check debug.log
are you using ram drive?(make sure no typos in -datadir=xxxx)
from db.log:
page 1908552804: illegal page type or format
PANIC: Invalid argument
PANIC: fatal region error detected; run recovery
check debug.log
i have that message in db.log - but the only runaway exceptions i had was my fault - i.e. wrong paths or other stuff
huntercoin version 1.0.11
Default data directory C:\Users\MikeS\AppData\Roaming\Huntercoin
Bound to port 8398
Setup huntercoin genesis block 00000000db7eb7a9e1a06cf995363dcdc4c28e8ae04827a961942657db9a1631
Loading addresses...
dbenv.open strLogDir=C:\Users\MikeS\AppData\Roaming\Huntercoin/database strErrorFile=C:\Users\MikeS\AppData\Roaming\Huntercoin/db.log
Loaded 1123 addresses
addresses 1435ms
Loading block index...
************************
EXCEPTION: NSt8ios_base7failureE
CDataStream::read() : end of data
C:\Users\MikeS\Downloads\huntercoin-1.0.11\huntercoin-qt.exe in Runaway exception
can't see the image.. but the error seems to be corrupted chain or at least people on here are recommended to redownload the chain (could be a more simple problem)
the patch has been tested by multiple people, but not ruling out it's related..
testing update again on some preupdate chains
are you sure you didn't force close the client while it was rewriting blkindex.dat with the new update? takes a few hours .. had you left your computer on that long?
did you backup the chain..
Jump to: