Horizon Platform Community [Support request] Is this sufficient to quickly update Node
Thread Posts Reply To This Post
Viewing 6 posts - 1 through 6 (of 6 total)
  • sandog
    sandog
    Participant

    Horizon: 107.50 HZ
    29th April 2015 at 6:32 pm

    Copying the two properies files from /conf
    also moving the old nhz.h2.db to its place in the new installation.

    Will there be any issues doing this or is there something new in the properties file that needs to be copied and pasted in to the older file to make it perfect for new version 3.9.1
    Note i downloaded the 3.9.1-node
    my previous version was hz_v3.8_api following the “how to set up a node” which worked fine.

    sandog
    sandog
    Participant

    Horizon: 107.50 HZ
    29th April 2015 at 6:43 pm

    Another question – is it necessary for forging to be disabled on a node? Does it matter if i set nhz.dontForge=false (thus i assume enabling forging). Is there some conflict in forging/node or intersection.

    ukon
    Participant

    Horizon: 16.50 HZ
    29th April 2015 at 7:40 pm

    :3 :3 :3

    CryptoAddict
    CryptoAddict
    Participant

    Horizon: 231.00 HZ
    29th April 2015 at 11:37 pm

    If you have run yout node frim GitHub source code or have ‘github client’ setup properly you can update your bode just issuing git pool/update command inside your hz node directory.

    Other easy way is download updated wallet at your pc/host, unzip it and replace all file on your hz directory with new version (cp -rf <new files> <your hz directory> on your linux host) will do your job. Afyer that replace conf/nhz-default-properties file with your on and run your node. Most of time it work like magic.

    Let me know if you find any problem with above processes.

    Cheers!

    MaWo
    Participant

    Horizon: 222.00 HZ
    1st May 2015 at 12:56 pm

    Please don’t copy the default conf files
    conf/nhz-default.properties
    conf/logging-default.properties
    and don’t change them!

    If you need to modify the configuration files then create
    conf/nhz.properties and/or
    conf/logging.properties
    and make your settings there.

    If you upgrade to a new HZ version then you only have to copy:
    conf/nhz.properties
    conf/logging.properties
    nhz_db/

    sandog
    sandog
    Participant

    Horizon: 107.50 HZ
    1st May 2015 at 8:58 pm

    Useful advice, thanks.
    I don’t know about these default conf files, those weren’t in anything i downloaded.

    Replacing all files with new files could over-write conf files couldn’t it? So, that sounds smart but also dumb. One has to backup their conf files and either go through it and update all the appropriate settings manually, or as i did just copy the conf file over the top of the new installation. After all that is why you make the obvious conf directory.

    Anyway, i hoped someone might say either
    a) There are no new changes that matter to what is in the conf file – so yes you can
    or
    b) There are some changes so you’ll need to manually update it. (perhaps you should do the whole process again – but i like precise advice)

    I don’t use git-hub and it might be trivial for experienced users but i haven’t bothered to set up any sync with git-hub. My node runs on my windows computer.

Viewing 6 posts - 1 through 6 (of 6 total)