Bitcoin Forum
October 24, 2017, 04:30:57 AM *
News: Latest stable version of Bitcoin Core: 0.15.0.1  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 [101] 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 ... 157 »
  Print  
Author Topic: .  (Read 467114 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
pharesim
Sr. Member
****
Offline Offline

Activity: 425



View Profile
July 15, 2015, 08:07:57 PM
 #2001

Reminder:
You have to update your nodes to 3.9.2 to keep getting the node bounty.
You won't need to follow the 4.0 update then, 3.9.2 will stay the official version until the 5.0 hard fork.
1508819457
Hero Member
*
Offline Offline

Posts: 1508819457

View Profile Personal Message (Offline)

Ignore
1508819457
Reply with quote  #2

1508819457
Report to moderator
1508819457
Hero Member
*
Offline Offline

Posts: 1508819457

View Profile Personal Message (Offline)

Ignore
1508819457
Reply with quote  #2

1508819457
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1508819457
Hero Member
*
Offline Offline

Posts: 1508819457

View Profile Personal Message (Offline)

Ignore
1508819457
Reply with quote  #2

1508819457
Report to moderator
Nxtblg
Legendary
*
Offline Offline

Activity: 924



View Profile WWW
July 16, 2015, 02:07:41 AM
 #2002

There was a description of what's new on the release page: https://github.com/NeXTHorizon/hz-source/releases/tag/hz-v3.9.2

Quote from: ccmawo
Under the hood classes were renamed back to Nxt class naming convention. This makes the source code more Nxt compatible and improves maintenance and code merges.

And that change brings up a question: is the API going to be changed too?

From: ...:7776/nhz?... to: ...:7776/nxt?... <- Is this change in the works?






██████████████████████████████████████████████████████████████████████████████████████████████
██████████████████████████████████████████████████████████████████████████████████████
███████████████████████████████████████████████████████████████████████▄▄▄███████████████████████
███████████████████████████████████████████████████████████████████████▀▀▀████████████████████████
██████████████████████████████████████████████████████████████████████████████████████████████████
█████████████████████████████████████████████████████████████████████████████████████████████████





...INTRODUCING WAVES........
...ULTIMATE ASSET/CUSTOM TOKEN BLOCKCHAIN PLATFORM...






MaWo
Hero Member
*****
Offline Offline

Activity: 568


View Profile WWW
July 16, 2015, 07:24:47 AM
 #2003

There was a description of what's new on the release page: https://github.com/NeXTHorizon/hz-source/releases/tag/hz-v3.9.2

Quote from: ccmawo
Under the hood classes were renamed back to Nxt class naming convention. This makes the source code more Nxt compatible and improves maintenance and code merges.

And that change brings up a question: is the API going to be changed too?

From: ...:7776/nhz?... to: ...:7776/nxt?... <- Is this change in the works?

API URL and configuration settings were preserved for backward compatibility.
acha
Jr. Member
*
Offline Offline

Activity: 51


View Profile
July 16, 2015, 07:27:24 AM
 #2004

Something I do not understand... Yesterday changed on the nodes version to 3.9.2 and Upime Until Next Payou has stopped, there is no payment from all nodes. But one node has not changed, the version is 3.9.1 - payment came. Is something wrong?
MaWo
Hero Member
*****
Offline Offline

Activity: 568


View Profile WWW
July 16, 2015, 07:49:13 AM
 #2005

Something I do not understand... Yesterday changed on the nodes version to 3.9.2 and Upime Until Next Payou has stopped, there is no payment from all nodes. But one node has not changed, the version is 3.9.1 - payment came. Is something wrong?

Did you copy the configuration files with your hallmarks?
sokol
Member
**
Offline Offline

Activity: 61


View Profile
July 16, 2015, 08:07:51 AM
 #2006

How often script checking nodes? How long to wait before the node is displayed here ?
sokol
Member
**
Offline Offline

Activity: 61


View Profile
July 16, 2015, 08:11:14 AM
 #2007

Is it possible to take full advantage of http://api.nhzcrypto.org:7776?
MaWo
Hero Member
*****
Offline Offline

Activity: 568


View Profile WWW
July 16, 2015, 08:17:55 AM
 #2008

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

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.
Emerger
Full Member
***
Offline Offline

Activity: 167


View Profile
July 16, 2015, 08:28:12 AM
 #2009

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)

MaWo
Hero Member
*****
Offline Offline

Activity: 568


View Profile WWW
July 16, 2015, 08:36:17 AM
 #2010

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)

It was an issue with 3.9.1, but with 3.9.2 both prefixes will work.
Emerger
Full Member
***
Offline Offline

Activity: 167


View Profile
July 16, 2015, 08:59:18 AM
 #2011

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)

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

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

acha
Jr. Member
*
Offline Offline

Activity: 51


View Profile
July 16, 2015, 09:00:33 AM
 #2012

Something I do not understand... Yesterday changed on the nodes version to 3.9.2 and Upime Until Next Payou has stopped, there is no payment from all nodes. But one node has not changed, the version is 3.9.1 - payment came. Is something wrong?

Did you copy the configuration files with your hallmarks?


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...
acha
Jr. Member
*
Offline Offline

Activity: 51


View Profile
July 16, 2015, 10:21:45 AM
 #2013

Something I do not understand... Yesterday changed on the nodes version to 3.9.2 and Upime Until Next Payou has stopped, there is no payment from all nodes. But one node has not changed, the version is 3.9.1 - payment came. Is something wrong?

Did you copy the configuration files with your hallmarks?


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


Back on one node on v3.9.1 - has begun the countdown. What's the problem?
MaWo
Hero Member
*****
Offline Offline

Activity: 568


View Profile WWW
July 16, 2015, 10:52:20 AM
 #2014

Something I do not understand... Yesterday changed on the nodes version to 3.9.2 and Upime Until Next Payou has stopped, there is no payment from all nodes. But one node has not changed, the version is 3.9.1 - payment came. Is something wrong?

Did you copy the configuration files with your hallmarks?


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


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

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
cbkr
Jr. Member
*
Offline Offline

Activity: 56


View Profile
July 16, 2015, 12:21:54 PM
 #2015

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

The issue has been fixed; please allow up to an hour for the data to be updated.
acha
Jr. Member
*
Offline Offline

Activity: 51


View Profile
July 16, 2015, 12:25:25 PM
 #2016

Something I do not understand... Yesterday changed on the nodes version to 3.9.2 and Upime Until Next Payou has stopped, there is no payment from all nodes. But one node has not changed, the version is 3.9.1 - payment came. Is something wrong?

Did you copy the configuration files with your hallmarks?


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


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

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

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

Activity: 924



View Profile WWW
July 16, 2015, 02:37:48 PM
 #2017


API URL and configuration settings were preserved for backward compatibility.


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






██████████████████████████████████████████████████████████████████████████████████████████████
██████████████████████████████████████████████████████████████████████████████████████
███████████████████████████████████████████████████████████████████████▄▄▄███████████████████████
███████████████████████████████████████████████████████████████████████▀▀▀████████████████████████
██████████████████████████████████████████████████████████████████████████████████████████████████
█████████████████████████████████████████████████████████████████████████████████████████████████





...INTRODUCING WAVES........
...ULTIMATE ASSET/CUSTOM TOKEN BLOCKCHAIN PLATFORM...






altsheets
Hero Member
*****
Offline Offline

Activity: 784

Free trial of #AltFolio = save time, react faster


View Profile WWW
July 16, 2015, 05:25:56 PM
 #2018

Quote
HZ3.9.2

Great news!



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:

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

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



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


Newbium great new platform || AltFolio = Altcoin Portfolio solution || AAsset = crowdfunding, dividends paying = profit sharing Assets (on NXT & HZ) - big 2nd dividends were paid, xmas 2016 || AssetGraphs = novel GUI to assets & shareholders (won nxthacks2015!) || ABEE = Block Explorer Extension for ETH clones, live on SOIL || Advice = Consulting || assetparser.py and shareholders.py - tools for NXT/HZ asset buyers & issuers || bamm.py || PeerCrawler || PGP || Texts || Github e.g. ChainCountDown, ethjsre |||| /give/ GiveBackLicense /give/ |||| Looking for an affordable crypto advertisement service with adspaces on crypto-attractive websites, contact me, thx.
MaWo
Hero Member
*****
Offline Offline

Activity: 568


View Profile WWW
July 16, 2015, 09:27:36 PM
 #2019


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

Is already included in hz-v4.0 Smiley



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

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

hz-v4.x

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.

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

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?

That is beyond my scope.

Code:
DB_CLOSE_ON_EXIT=FALSE
What is the meaning of this?
And why is FALSE the default?

That's to avoid a "Database is already closed" issue with the embedded h2 database.
altsheets
Hero Member
*****
Offline Offline

Activity: 784

Free trial of #AltFolio = save time, react faster


View Profile WWW
July 17, 2015, 01:09:00 AM
 #2020

Thanks!


Newbium great new platform || AltFolio = Altcoin Portfolio solution || AAsset = crowdfunding, dividends paying = profit sharing Assets (on NXT & HZ) - big 2nd dividends were paid, xmas 2016 || AssetGraphs = novel GUI to assets & shareholders (won nxthacks2015!) || ABEE = Block Explorer Extension for ETH clones, live on SOIL || Advice = Consulting || assetparser.py and shareholders.py - tools for NXT/HZ asset buyers & issuers || bamm.py || PeerCrawler || PGP || Texts || Github e.g. ChainCountDown, ethjsre |||| /give/ GiveBackLicense /give/ |||| Looking for an affordable crypto advertisement service with adspaces on crypto-attractive websites, contact me, thx.
Pages: « 1 ... 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 [101] 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 ... 157 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!