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

Interested in seeing where this coin goes.

Good luck, smooth.

Yes it has been discussed, and might be considered again, especially once the coin is brought up to a more mature state, but is not an immediate priority.

And welcome to the thread CryptoClub.

Yes, that is appreciated. Marketcap is super low, and I think in the long run this will do very well for us. Patience does pay off.

I know some other traders that also agree with me on this one that have good taste.

Was there some discussion of branding changes in the past? Heard some mention of it.

Really appreciate the frequent updates and transparency of the dev on this thread.

Thank you for the test report!

compiling, starting, converting and exiting works for me.
will run it for a while and report any issues.

New test release

This release reduces memory usage and blockchain file size by optimizing storage of the outputs table. While the reduction is somewhat modest, it will be more significant with pruning (the pruned data does not include the outputs table).

Please test, especially if you have a smaller memory configuration. Very small memory configurations won't work with this, but if you have something that has been barely able to run the deemon previously, this should improve your performance quite a bit.

The next step after this is pruning, so if any issues arise here I would like to address them before releasing the pruning support.

Instructions:

1. Copy your blockchain.bin file to another location as a backup. This version will convert the blockchain file to a new format and you won't able to downgrade to the released code with the upgraded blockchain file.

2.
3. Start node. You should get a message at startup about the blockchain being converted. You can ignore any debug messages about empty outputs and such.

4. Exit node to save the converted blockchain

5. Start node again with new blockchain

Report any issues (or even if no issues)

Thanks for testing!

Hehe, good to hear 

Here's a little known secret (well, slightly less known now). Most of my posting activity (including this one) occurs during test runs, compile cycles, downloads, large dataset copies, etc. I'm a compulsive multitasker.

The trolls who may think they are sabotaging my efforts by encouraging me to respond to them and therefore wasting my time are in fact not.

Ok, great to hear that. I'm anyway comfy with your dev lead skills ...  and I don't mind long term prospect at all in a coin.  I'm holding SDC since more than a year for instance!

My concern is more the shitstorm. At the risk of stating the obvious too, conflicts are bad. It sucks time that could be used for actual development. Some people are anyway stupid, sometimes Its better to prove them wrong with execution than with words.

At the risk of stating the obvious, upside in this coin is a long term prospect. If you aren't comfortable with that, it's probably not the play for you.

Of course, I respect your right to trade or not trade as you see fit.

Either way, I'm not going anywhere, trolls or no trolls. Development will continue.

Some progress on the memory front due shortly.

Price is really going to the ground. I won't put more BTC for support till the shitstorm is gone. Its really hurting the coin.

Thanks, I'll be able to switch in a short while and will check back later.

His node is not synced yet, you should switch away temporarily but you can switch back when it is synced, I'd guess few hours at this rate.

As I was asleep with limited access to where the miner I'm using this week is, I didn't notice the problem.  Having breakfast now

Is the pool OK now?

I'm not looking for compensation, it shouldn't be much.  Should I give you my address?

yes, during any operation on the blockchain (load, save or synchronization), the server is in a lot of pain

if there isn't any operation on the blockchain, the load average is no more than ~0.05

[edit] due to a lack of ram, swap is heavily used...

Seems to be processing blocks at a very slow rate (maybe 1/sec). Is it overloaded again?

here the long story.

i tried to update the daemon on http://52.8.47.33:8080 last night (~01h00 AM in my local time). it was needed to eliminate an anormal high risk of orphan block.
i started to save the blockchain before switching off aeond but immediately the server (amazon aws) was overloaded. 30 minutes later,  the blockchain was still not save! i decided to kill aeond... bad idea... the load of the server stayed between 2 and 3.5! i was unable to do anything, the new daemon can't be loaded (stuck always in the middle, i tried three times with no success, i think the blockchain was broken due to the kill)
at ~03h30 AM, i decided to reboot the server because i did not have solution anymore (and i need to go to bed) but i lost access to the instance. server was too overloaded, reboot took at least one hour. i tried to announce the failure but bitcointalk was "502 Bad Gateway"
at 04h00, i decided to sleep because i can't do nothing more in this situation (no access to pool, nor btt...)

this morning, i connected at the instance at 09h00 and it was rebooted during my sleep, load was at 0 and i was able to relaunch the pool with a bootstrap and the new daemon. bad night.

the daemon is still not synchronized now. check the blockchain height on the home page of http://52.8.47.33:8080, it will be synchronized at something like #595650. so wait a little time before to send shares again.

i sincerely apologize to miners who's lost their shares on my pool this night. i will look how to compensate them. (i have their address in the logs)



 

short story:
Major failure of my server (EC2 instance) http://52.8.47.33:8080, i regain access only now. i'm trying to relaunch the pool and come back after for the long story.