Burst Power Network Pool

[morantis]

I did that and sometimes it is quick and sometimes slow. I imagine it has to do with how long back the DB was copied. the real solution would be finding actual answers in the logs or a cleaner shut method. CTRL+C works most of the time, but that one time that it does not and you are back to DB square 1. My only other option and I think I will do it until a better one comes along is to constantly have a second NXT daemon running on another server and when there is an issue we can switch to that until the other is back and going right.

[haitch]

@morantis There is a better way - see the post here: https://forums.burst-team.us/topic/853/new-wallet-version-1-2-6/9

[morantis]

Taking a look, thanks. I saw that and I am not sure how to work the other start up parameters in there, but the concept is sound, just need to make it work for Burst.

[haitch]

@morantis you should be able to do:

java -cp burst.jar;lib*;conf nxt.Nxt STOP.PORT=<port> STOP.KEY=<password>

[morantis]

@haitch Thanks, I will try it later in the night, have the pool running right now and I cannot imagine how many people our network lost because the first testing day was mostly offline.

[jervis]

@morantis access denied :( I really wanna test it,

[morantis]

@jervis the pool?

[jervis]

@morantis yes bud. or is it just me? :(

[morantis]

@jervis No, we had very little response, so I pulled it down to make some changes. We are plotting out some new drives for the network rentals. That is taking a good amount of steam, I will put the pool, with the changes back in live mode tomorrow morning and let you know then, we appreciate the support.

[morantis]

Ok, making preparations to go let me know @jervis

[morantis]

@jervis Ok, up and running and just for you. I will hit it in a bit if you have joined in.

[morantis]

@morantis with all the forking, giving it a good few minutes to sync up.