Topic: . - page 56. (Read 491736 times)

There is an issue with the login form not showing sometimes, but it's not connected to switching the language for me. Couldn't reliably reproduce it yet.

Developers. I use test version HZ v4.0 in Firefox. After changing the language to Russian is not possible to go into the purse second time, no longer displays the authorization form. Only helps complete cleaning browser history, but after the change of the language is the same again. Please correct before release HZ v4.0

A standalone client capable of one-click updates might do the magic. I don't know if its on the works though.

Upgraded to V3.9.2 on Win7 and hallmarked node promptly detected. Nice!

All looks good however wallet contacts are gone.  Anyway to restore wallet contacts without re-typing them in?

Thanks!

Is already included in hz-v4.0


The library json-simple-1.1.1.jar uses not typed raw types.
The compiler can not check at compile time for type safety.
The note is the corresponding warning.


hz-v4.x


I've added a hint for windows users, thanks.


That is beyond my scope.


That's to avoid a "Database is already closed" issue with the embedded h2 database.

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:


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


Could anyone explain the meaning to me?  Thx.

---

The node seems to run fine:
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":


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:

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:


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".

Good idea.

---

Yippieh, yiehah, yeah!

Keep up the good work!

Thanks again, MaWo. In my case, not preserving backward compatibility would have involved a little more debugging (sigh).

Working))) On all versions I've always modified the nhz-default.properties... Thank you very much!!!

The issue has been fixed; please allow up to an hour for the data to be updated.

Just for clarification, I don't know whether I understood you correctly:
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.

When you extract a new release, you only need to move or copy your database directory nhz_db/
and your custom config files
conf/nhz.properties
conf/logging.properties

Back on one node on v3.9.1 - has begun the countdown. What's the problem?

Of course. Replaced nhz-default.properties v3.9.1  from it's conf folder on nhz-default.properties in conf folder v3.9.2. Folders v3.9.1 and v3.9.2 different - folder v3.9.1 and folder v3.9.2 respectively. The fact that the time is not changed, it freezes after the transition to v3.9.2. If an error in the configuration file, node checker sees the node but thus there is a countdown. May be reconfigure nodes? What's the point...

Strange, because I had this issue with both my servers. Both were updated to 3.9.1 first day and have run fine, but both had peer problem with 3.9.2 until I changed to prefix of those two settings to nhz.

Thanks

It was an issue with 3.9.1, but with 3.9.2 both prefixes will work.

Noticed I wasn't getting any peers then found in my nhz-default.properties, two settings starting with nxt: nxt.maxNumberOfKnownPeers and nxt.minNumberOfKnownPeers

I changed it to: nhz.maxNumberOfKnownPeers & nhz.minNumberOfKnownPeers

.. and working again. Don't know if this was an earlier mistake I made but this wasn't a problem with 3.9.1

(I tend to re-use same config settings so didn't notice straight away)

HZ v4.0 is still beta/experimental. You should be aware of this, but I don't expect any problems.
If you experience unusual/strange things then please report them.

Is it possible to take full advantage of http://api.nhzcrypto.org:7776?

How often script checking nodes? How long to wait before the node is displayed here ?

Did you copy the configuration files with your hallmarks?