Pages:
Author

Topic: [ANN] AEON [2019-09-27: Upgrade to version 0.13.0.0 ASAP HF@1146200 Oct 25] - page 90. (Read 625768 times)

newbie
Activity: 13
Merit: 0
Hi,

First of all, I'm pretty impressed by the dev of Aeon, and want to congratulate all the dev working hard on this project.

I've encourter an issue since a week now, I try to find some workaround, but nothing work from my side. I can't synchronise to the blockchain with aeond.exe (either version 0.9.12 or 0.9.13, or even with the last 0.9.14)

The Error message is this following one :

...
Core rpc server initialized OK on port: 11181
Initializing core...
 Loading blockchain...
 ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.13.0\src\common/boost_serialization_helper.h:108 Exception at [unserialize_obj_from_file], what=vector too long
 Can't load blockchain storage from file, generating genesis block.
 ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.13.0\src\cryptonote_core\blockchain_storage.cpp:130 Failed to add genesis block to blockchain
 ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.13.0\src\cryptonote_core\cryptonote_core.cpp:128 Failed to initialize blockchain storage
 ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.13.0\src\daemon\daemon.cpp:191 Failed to initialize core
 Mining has been stopped, 0 finished


Strange things : I haven't done any change localy, it just stop working and show me this message one days.

I don't undertand why some script try to access to a folder users name call "Arno" It's not mine for sure, looks likes some rest of a local path in the code from one dev ? It's me or it could be cleaner ?

Any idea to get throught this ?

Thanks by advance.

Everyone sees this not just you, just ignore it. Shouldn't affect you

The problem is that I don't synchronise anymore, the cmd windows close immediatly after the Error message, and I can't sync simplewallet :

Error: wallet failed to connect to daemon (http://localhost:11181). Daemon either is not started or passed wrong port. Please, make sure that daemon is running or restart the wallet with correct daemon address.
sounds like a corrupt blockchain, delete the file named blockchain.bin at c:\Users\your_username\AppData\Roaming\aeon then relaunch aeond.exe. it will re-sync from sratch. i don't have any explanation (several possible causes)

and yes, C:\Users\Arno\Documents\GitHub\aeon-0.9.13.0 is a rest of a local path of my windows computer.


Your solution was the good one, for unknown reason the blockchain.bin was corrupted, everything is working again now. (0.9.13)

In a other subject.
I use this time to change pool on my workers, and not use "aeon-pool.com" again, which is in a bad way to be upper the 50% ... Not good for the decentralization.
Decide to use "aeon.n-engine.com" pretty new, but look solid.
newbie
Activity: 30
Merit: 0
Ok probably going to show my naivete a little bit but Ive tried to run both versions of the simple wallet (0.9.13 and 0.9.14) and I keep getting the following error after I type my password:

Error: wallet failed to connect to daemon (http://localhost:11181). Daemon either is not started or passed wrong port. Please, make sure that daemon is running or restart the wallet with correct daemon address.

Open to suggestions here. I'm not really sure how to control this quite honestly.

**edit- I realized I didnt add that I did try the Refresh command. No luck

-LS

You need to run aeond, and you need to let it sync (2-48 hours depending on several factors), then you can run your wallet.

Great - Thanks. For some reason I was thinking simplewallet was a way to connect to the network without getting a full sync.
newbie
Activity: 13
Merit: 0
sounds like a corrupt blockchain, delete the file named blockchain.bin at c:\Users\your_username\AppData\Roaming\aeon then relaunch aeond.exe. it will re-sync from sratch. i don't have any explanation (several possible causes)

and yes, C:\Users\Arno\Documents\GitHub\aeon-0.9.13.0 is a rest of a local path of my windows computer.




Thanks ! I'll try that and will feedback about the result.
hero member
Activity: 500
Merit: 500
Hi,

First of all, I'm pretty impressed by the dev of Aeon, and want to congratulate all the dev working hard on this project.

I've encourter an issue since a week now, I try to find some workaround, but nothing work from my side. I can't synchronise to the blockchain with aeond.exe (either version 0.9.12 or 0.9.13, or even with the last 0.9.14)

The Error message is this following one :

...
Core rpc server initialized OK on port: 11181
Initializing core...
 Loading blockchain...
 ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.13.0\src\common/boost_serialization_helper.h:108 Exception at [unserialize_obj_from_file], what=vector too long
 Can't load blockchain storage from file, generating genesis block.
 ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.13.0\src\cryptonote_core\blockchain_storage.cpp:130 Failed to add genesis block to blockchain
 ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.13.0\src\cryptonote_core\cryptonote_core.cpp:128 Failed to initialize blockchain storage
 ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.13.0\src\daemon\daemon.cpp:191 Failed to initialize core
 Mining has been stopped, 0 finished


Strange things : I haven't done any change localy, it just stop working and show me this message one days.

I don't undertand why some script try to access to a folder users name call "Arno" It's not mine for sure, looks likes some rest of a local path in the code from one dev ? It's me or it could be cleaner ?

Any idea to get throught this ?

Thanks by advance.

Everyone sees this not just you, just ignore it. Shouldn't affect you

The problem is that I don't synchronise anymore, the cmd windows close immediatly after the Error message, and I can't sync simplewallet :

Error: wallet failed to connect to daemon (http://localhost:11181). Daemon either is not started or passed wrong port. Please, make sure that daemon is running or restart the wallet with correct daemon address.
sounds like a corrupt blockchain, delete the file named blockchain.bin at c:\Users\your_username\AppData\Roaming\aeon then relaunch aeond.exe. it will re-sync from sratch. i don't have any explanation (several possible causes)

and yes, C:\Users\Arno\Documents\GitHub\aeon-0.9.13.0 is a rest of a local path of my windows computer.

sr. member
Activity: 868
Merit: 279
This coin has always been great to mine. Sleeping giant right here!
sr. member
Activity: 450
Merit: 250
I see that aeon-pool(dot)com has put a notice to encourage miners to mine on other pools in order to help decentralizing the network and prevent a pool from having more than 50% of the entire network's hash. That's a really nice move. 

One thing that discourage miners from moving to a different pool is the pending balance below the payment threshold (the so called 'dust'). Even 0.001 AEON will be worth something in the near future. 

So, I have a  suggestion to pool operators:

If a miner stops mining on your pool for, let's say, 24 or 48 hours then all the pending balance (no matter how small) should be paid to the miner.

Just my 2 satoshis

I agree that this is a problem, and I like your solution. The only consideration is that the solution should not cost the pool transaction fees. Provided the dust owed to the miner is more than the tx fee, should be good!
newbie
Activity: 22
Merit: 0
I see that aeon-pool(dot)com has put a notice to encourage miners to mine on other pools in order to help decentralizing the network and prevent a pool from having more than 50% of the entire network's hash. That's a really nice move. 

One thing that discourage miners from moving to a different pool is the pending balance below the payment threshold (the so called 'dust'). Even 0.001 AEON will be worth something in the near future. 

So, I have a  suggestion to pool operators:

If a miner stops mining on your pool for, let's say, 24 or 48 hours then all the pending balance (no matter how small) should be paid to the miner.

Just my 2 satoshis
newbie
Activity: 13
Merit: 0
Hi,

First of all, I'm pretty impressed by the dev of Aeon, and want to congratulate all the dev working hard on this project.

I've encourter an issue since a week now, I try to find some workaround, but nothing work from my side. I can't synchronise to the blockchain with aeond.exe (either version 0.9.12 or 0.9.13, or even with the last 0.9.14)

The Error message is this following one :

...
Core rpc server initialized OK on port: 11181
Initializing core...
 Loading blockchain...
 ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.13.0\src\common/boost_serialization_helper.h:108 Exception at [unserialize_obj_from_file], what=vector too long
 Can't load blockchain storage from file, generating genesis block.
 ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.13.0\src\cryptonote_core\blockchain_storage.cpp:130 Failed to add genesis block to blockchain
 ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.13.0\src\cryptonote_core\cryptonote_core.cpp:128 Failed to initialize blockchain storage
 ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.13.0\src\daemon\daemon.cpp:191 Failed to initialize core
 Mining has been stopped, 0 finished


Strange things : I haven't done any change localy, it just stop working and show me this message one days.

I don't undertand why some script try to access to a folder users name call "Arno" It's not mine for sure, looks likes some rest of a local path in the code from one dev ? It's me or it could be cleaner ?

Any idea to get throught this ?

Thanks by advance.

Everyone sees this not just you, just ignore it. Shouldn't affect you

The problem is that I don't synchronise anymore, the cmd windows close immediatly after the Error message, and I can't sync simplewallet :

Error: wallet failed to connect to daemon (http://localhost:11181). Daemon either is not started or passed wrong port. Please, make sure that daemon is running or restart the wallet with correct daemon address.
newbie
Activity: 39
Merit: 0
Hi,

First of all, I'm pretty impressed by the dev of Aeon, and want to congratulate all the dev working hard on this project.

I've encourter an issue since a week now, I try to find some workaround, but nothing work from my side. I can't synchronise to the blockchain with aeond.exe (either version 0.9.12 or 0.9.13, or even with the last 0.9.14)

The Error message is this following one :

...
Core rpc server initialized OK on port: 11181
Initializing core...
 Loading blockchain...
 ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.13.0\src\common/boost_serialization_helper.h:108 Exception at [unserialize_obj_from_file], what=vector too long
 Can't load blockchain storage from file, generating genesis block.
 ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.13.0\src\cryptonote_core\blockchain_storage.cpp:130 Failed to add genesis block to blockchain
 ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.13.0\src\cryptonote_core\cryptonote_core.cpp:128 Failed to initialize blockchain storage
 ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.13.0\src\daemon\daemon.cpp:191 Failed to initialize core
 Mining has been stopped, 0 finished


Strange things : I haven't done any change localy, it just stop working and show me this message one days.

I don't undertand why some script try to access to a folder users name call "Arno" It's not mine for sure, looks likes some rest of a local path in the code from one dev ? It's me or it could be cleaner ?

Any idea to get throught this ?

Thanks by advance.

Everyone sees this not just you, just ignore it. Shouldn't affect you
sr. member
Activity: 266
Merit: 250
Devs, please, shed some light: 0.9.13 goes with Boost 1.63? Is it the minimum required AEON version?
What VS version is required to compile?Minimum and recommended.
I've the impression that currently there are just too many chances to have backward compatibility related problems.
Then, why 1.64 for 0.9.14 when 1.65.1 addresses a lot of issues -not least 'Visual C++ version checks'- ?
newbie
Activity: 13
Merit: 0
Hi,

First of all, I'm pretty impressed by the dev of Aeon, and want to congratulate all the dev working hard on this project.

I've encourter an issue since a week now, I try to find some workaround, but nothing work from my side. I can't synchronise to the blockchain with aeond.exe (either version 0.9.12 or 0.9.13, or even with the last 0.9.14)

The Error message is this following one :

...
Core rpc server initialized OK on port: 11181
Initializing core...
 Loading blockchain...
 ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.13.0\src\common/boost_serialization_helper.h:108 Exception at [unserialize_obj_from_file], what=vector too long
 Can't load blockchain storage from file, generating genesis block.
 ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.13.0\src\cryptonote_core\blockchain_storage.cpp:130 Failed to add genesis block to blockchain
 ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.13.0\src\cryptonote_core\cryptonote_core.cpp:128 Failed to initialize blockchain storage
 ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.13.0\src\daemon\daemon.cpp:191 Failed to initialize core
 Mining has been stopped, 0 finished


Strange things : I haven't done any change localy, it just stop working and show me this message one days.

I don't undertand why some script try to access to a folder users name call "Arno" It's not mine for sure, looks likes some rest of a local path in the code from one dev ? It's me or it could be cleaner ?

Any idea to get throught this ?

Thanks by advance.
hero member
Activity: 500
Merit: 500
Still no windows wallet gui after 3 years?

There have been but they've not been consistently maintained. This is a community-based project, so if people don't come forward with an interest in doing something it doesn't get done. Bounties are possible. After the rebase adapting the Monero GUI will be an option.
Hi i have issue my old wallet is not opened, its cmd outpubt:

aeon wallet v0.9.14.0()
Specify wallet file name (e.g., wallet.bin). If the wallet doesn't exist, it wil
l be created.
Wallet file name: mywallet
password: ******
Error: failed to load wallet: failed to read file "mywallet"


my pass and wallet name true i use it for 0.9.13 and its worked

does it still work with 0.9.13 ? 
0.9.14 windows binary from stoffu, available on appveyor was built with boost 1.63 and 0.9.13 official was using boost 1.64.
when you're using a different version of boost library, sometimes this problem occurs.

to recover your wallet, delete the name_of_your_wallet file (it's a cache of your wallet history) and keep the name_of_your_wallet.keys file, simplewallet will regenerate your wallet history from scratch.
warning: the .keys file is the most important file, without it you lost your wallet!



Thanks Arux for pointing out the cause of the problem I was overlooking! I've rebuilt the 0.9.14 Windows binary with Boost 1.64 and Visual Studio 2017:
https://ci.appveyor.com/project/stoffu/aeon/build/artifacts
Recovering the wallet is fast and pretty easy but it's better to not mix boost version to avoid misleading non-techies.
legendary
Activity: 3164
Merit: 1116
Ok probably going to show my naivete a little bit but Ive tried to run both versions of the simple wallet (0.9.13 and 0.9.14) and I keep getting the following error after I type my password:

Error: wallet failed to connect to daemon (http://localhost:11181). Daemon either is not started or passed wrong port. Please, make sure that daemon is running or restart the wallet with correct daemon address.

Open to suggestions here. I'm not really sure how to control this quite honestly.

**edit- I realized I didnt add that I did try the Refresh command. No luck

-LS

You need to run aeond, and you need to let it sync (2-48 hours depending on several factors), then you can run your wallet.
newbie
Activity: 30
Merit: 0
Ok probably going to show my naivete a little bit but Ive tried to run both versions of the simple wallet (0.9.13 and 0.9.14) and I keep getting the following error after I type my password:

Error: wallet failed to connect to daemon (http://localhost:11181). Daemon either is not started or passed wrong port. Please, make sure that daemon is running or restart the wallet with correct daemon address.

Open to suggestions here. I'm not really sure how to control this quite honestly.

**edit- I realized I didnt add that I did try the Refresh command. No luck

-LS
full member
Activity: 387
Merit: 186
AEON rocks!!! Booyyahhh
full member
Activity: 203
Merit: 166
Still no windows wallet gui after 3 years?

There have been but they've not been consistently maintained. This is a community-based project, so if people don't come forward with an interest in doing something it doesn't get done. Bounties are possible. After the rebase adapting the Monero GUI will be an option.
Hi i have issue my old wallet is not opened, its cmd outpubt:

aeon wallet v0.9.14.0()
Specify wallet file name (e.g., wallet.bin). If the wallet doesn't exist, it wil
l be created.
Wallet file name: mywallet
password: ******
Error: failed to load wallet: failed to read file "mywallet"


my pass and wallet name true i use it for 0.9.13 and its worked

does it still work with 0.9.13 ? 
0.9.14 windows binary from stoffu, available on appveyor was built with boost 1.63 and 0.9.13 official was using boost 1.64.
when you're using a different version of boost library, sometimes this problem occurs.

to recover your wallet, delete the name_of_your_wallet file (it's a cache of your wallet history) and keep the name_of_your_wallet.keys file, simplewallet will regenerate your wallet history from scratch.
warning: the .keys file is the most important file, without it you lost your wallet!



Thanks Arux for pointing out the cause of the problem I was overlooking! I've rebuilt the 0.9.14 Windows binary with Boost 1.64 and Visual Studio 2017:
https://ci.appveyor.com/project/stoffu/aeon/build/artifacts
legendary
Activity: 2968
Merit: 1198
Do pool owners NEED to update to 0.9.14.0 seeing as how it is optional?

It appears that the changes are meant for those who run a public node for remote use.

No, not needed for pools unless you are having an issue with payouts and want to use the fee multiplier (only affects wallet, not daemon).

Although, now that I think about it, fees on pool payouts are likely set by the RPC and not the command line, so the fee multiplier wouldn't do anything. Pools can set whatever fees they want with the RPC.

So in summary, no reason for pools to bother with 0.9.14.0. 0.9.13.0 is perfectly fine.
hero member
Activity: 610
Merit: 500
where I can download for windows  Angry
Pages:
Jump to: