Quote

HZ3.9.2

Great news!

Quote from: MaWo on July 16, 2015, 10:52:20 AM

You should not modify the file nhz-default.properties, instead create a nhz.properties file with only the
properties you need to change, and set them there. The values in nhz.properties override those in nhz-default.properties.
The same applies for logging-default.properties. Create a logging.properties file and make your changes there.

Good point mentioning that again.

I know that some of the 'how to install your HZ node' manuals out there
do give the wrong approach, and suggest to edit 'nhz-default.properties';
which now causes more work for those nodes which want a simple upgrade,
than doing it the proper way, by creating a 'nhz.properties'.

I suggest to also put an informative header into the nhz-default.properties
(alike the explanations in the header of in /conf/logging-default.properties).

About updating to newer code ...

A while ago, ~~someone~~ Mawo posted this easy scheme to install and upgrade:

Code:

# upgrade to latest version:
git pull
./compile.sh
screen -rd hzlive
CTRL-C
screen -S hzlive -L ./run.sh

which I am using on my node. Now after 'git pull; ./compile.sh' I get these messages:

Code:

Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
nhz.jar generated successfully

Could anyone explain the meaning to me? Thx.

The node seems to run fine:

Code:

Initializing Nhz server version NHZ V3.9.2
...
2015-07-16 16:16:04 INFO: Database update may take a while if needed, current db version 70...
2015-07-16 16:19:26 INFO: nhz.forceValidate = "false"
...
2015-07-16 16:19:27 INFO: Scanning blockchain...
2015-07-16 16:19:37 INFO: processed block 0
...
2015-07-16 16:23:21 INFO: processed block 395000
2015-07-16 16:23:22 INFO: ...done
...
2015-07-16 16:23:22 INFO: Initialization took 448 seconds
2015-07-16 16:23:22 INFO: Nhz server NHZ V3.9.2 started successfully.
...

But it still takes ages to finish booting up. Which future version will skip the blockchain scanning?

I suggest to put an informative sentence at the end "keep this NRS open while you forge or access the wallet", see truxtons newbie troubles.

About MaWo's hz-nxtgui "HZng":

Code:

cd /opt
git clone https://bitbucket.org/MattWo/hz-nxtgui
cd hz-nxtgui
./compile.sh
cp ../hz-source/conf/nhz.properties conf/

echo "# database from HZdefault node:" >> conf/nhz.properties
echo "nhz.dbUrl=jdbc:h2:../hz-source/nhz_db/nhz;DB_CLOSE_ON_EXIT=FALSE" >> conf/nhz.properties

screen -rd hzlive
CTRL-C
screen -S hznxtgui -L ./run.sh

Explanations: All happens in /opt. Cloning the sourcecode, compiling it (same warning as above, BTW). Copies all my settings (hallmark, etc) from the default HZ, then adds two lines to make HZng also use the same nhz_db as the default HZ (saves time & harddisk). Kill default HZ, then start HZng in its own screen. Voila - using the existing nhz_db ... HZng is online!

Kudos MaWo, very nice work. Finally, the MESSAGES have their own tab!

I suggest you include two such scripts, one for Linux/Mac, one for Windows, to (semi-)automatically make those above changes to recycle the nhz_db from HZdefault?

nhz-default.properties:

Code:

DB_CLOSE_ON_EXIT=FALSE

What is the meaning of this?
And why is FALSE the default?

The node checker https://explorer.horizonplatform.io/?page=nodecheck
shows my updated node as "offline"
- do I simply have to wait a while, or is it a TODO for you?

I was also always wondering:

Quote from: pharesim on July 15, 2015, 03:30:38 AM

Quote from: Emerger on July 15, 2015, 03:27:18 AM

Quote from: pharesim on July 15, 2015, 03:22:18 AM

Quote from: Emerger on July 15, 2015, 03:20:05 AM

Sorry if this has been asked before, but what's the exact difference between hz-v3.9.2.zip & hz-v3.9.2-node.zip ? ...

the -node wallet is preconfigured for running a public node yourself

in detail:
- forging is disabled, the forging indicator is removed
- port 7776 is available on all interfaces, allowing connections from outside your local network

Thx for the explanations.

I suggest to put these sentences onto https://horizonplatform.io/get-started/wallets
and actually encourage people to run public nodes, as a fallback, during downtimes of the "web wallet".

Quote from: Emerger on July 15, 2015, 04:46:49 AM

Perhaps in future it could be named as such: hz-*-publicnode.zip Just a suggestion anyway.

Good idea.

Quote from: Pizpie on July 15, 2015, 12:49:26 AM

This release is in preparation for our 4.0 release, which will follow this release in 10 days. HZ 5.0 will follow in about a month as we are in the process of testing it and adding a few things.

Yippieh, yiehah, yeah!

Keep up the good work!

Consider to GIVEBACK. Thx