HZxchange has its own thread now
https://bitcointalksearch.org/topic/relaunch-hzxchange-1065680
Sorry about the node check api. The sarcastic comment surprisingly was correct, I forgot about it over all the other stuff. Put it back on the to-do-list, thanks for bringing it up again.
Topic: . - page 75. (Read 491760 times)
How to setup HZ-node in linux or linux-VPS.
Ubuntu/Debian.
1. In your local PC go to http://localhost:7776/admin.html
2. below "Generate Hallmark:" write:
Public IP: "your IP"
Secret Phrase: "you password from your hz account."
After this press submit
3. after step 2 you will see your Hallmark below. Save it.
Now connect to your VPS if you use VPS or open terminal. (all command from root)
Installation tools.
installation client.
Configuration.
And write:
nhz.myAddress=your ip
nhz.myHallmark=your Hallmark (look step 3)
Then save and exit.
Open port.
Starting.
Done.
For tips:
NHZ-WWMB-6BNJ-VNG7-3SQDJ
1aTiFrshYYPYmBAU7tMsZoDkz3ya9kBTc
Thanks!
Ubuntu/Debian.
1. In your local PC go to http://localhost:7776/admin.html
2. below "Generate Hallmark:" write:
Public IP: "your IP"
Secret Phrase: "you password from your hz account."
After this press submit
3. after step 2 you will see your Hallmark below. Save it.
Now connect to your VPS if you use VPS or open terminal. (all command from root)
Installation tools.
Code:
apt-get install unzip
apt-get install openjdk-7-jre
apt-get install nano
apt-get install wget
installation client.
Code:
wget https://github.com/NeXTHorizon/hz-source/releases/download/hz-v3.9.1/hz-v3.9.1.zip
unzip hz-v3.9.1.zip
Configuration.
Code:
cd hz
nano conf/nhz-default.properties
And write:
nhz.myAddress=your ip
nhz.myHallmark=your Hallmark (look step 3)
Then save and exit.
Open port.
Code:
iptables -A INPUT -p tcp -d 0/0 -s 0/0 --dport 7774 -j ACCEPT
Starting.
Code:
screen -S nhz
./run.sh
Done.
For tips:
NHZ-WWMB-6BNJ-VNG7-3SQDJ
1aTiFrshYYPYmBAU7tMsZoDkz3ya9kBTc
Thanks!
I've seen alot about running a hallmark node on linux however I'm going on two days now waiting for my Windows-based node to be seen on the network and I'm now wondering if that's supported.
As posted to the Horizon forum I successfully followed the "how-to setup a node.." video on my Windows 7 Pro workstation with Symantec Endpoint firewall and a rule added to allow Port 7774-TCP inbound.
https://horizonplatform.io/topic/running-horizon-hallmark-node/
If Windows is supported is there any way beyond the Horizon Node Checker to know if my node is visible on the network?
https://explorer.horizonplatform.io/?page=nodecheck
Any advise would be greatly appreciated as I'm excited about being an active participant however am not versed in linux.
As posted to the Horizon forum I successfully followed the "how-to setup a node.." video on my Windows 7 Pro workstation with Symantec Endpoint firewall and a rule added to allow Port 7774-TCP inbound.
https://horizonplatform.io/topic/running-horizon-hallmark-node/
If Windows is supported is there any way beyond the Horizon Node Checker to know if my node is visible on the network?
https://explorer.horizonplatform.io/?page=nodecheck
Any advise would be greatly appreciated as I'm excited about being an active participant however am not versed in linux.
Do you have a public ip? Do you use UPnP? Could you please send me your IP?
I hadn't considered UPnP as a requirement for this to work and I see "UPnP Discovery" and "SSDP" Blocked in the Symantec Firewall with an option to allow both from private IP addresses. I can PM you my public IP however would like to understand the scope of what workstation service(s) will need to be exposed in order for this to work and if deemed too risky I would consider another adoption to running a hallmark node. Perhaps this is why I'm not reading about Windows hallmark nodes?
UPnP is not required.
The requirements for a public hallmarked node are a public accessible IP, an open port 7774, a hz wallet with a configured hallmark and an activated peer server listen on port 7774.The peer server is already enabled with the default settings.
If your PC is behind a router in a private network then you have to add a NAT rule for port 7774 manually or you enable UPnP.
The main requirement of running any node is 'accessibility' from outside world. It doesn't count how this 'accessibility' configured like UPnP or Port forward or with dynamic DNS service or even it has attach with any 'Content delivery network service (CDN)).
Running node is something like running your own 'webserver'. If you run any web server behind your private network and block any incoming request from world network, it is useless even your LAN/Office/Home/Internal network can access it. To qualify as node bounty payee, your node must have a fixed public IP address and port 7774 open to serve request from outside network.
You don't need to give your public IP address to anyone you think risky; if you inside any NAT/Firewall findout what is your IP address from http://ifconfig.me/ip or https://www.whatismyip.com/ and try checking your 7774 TCP port open from http://www.adminkit.net/telnet.aspx
As soon you get 'Connection to
I've seen alot about running a hallmark node on linux however I'm going on two days now waiting for my Windows-based node to be seen on the network and I'm now wondering if that's supported.
As posted to the Horizon forum I successfully followed the "how-to setup a node.." video on my Windows 7 Pro workstation with Symantec Endpoint firewall and a rule added to allow Port 7774-TCP inbound.
https://horizonplatform.io/topic/running-horizon-hallmark-node/
If Windows is supported is there any way beyond the Horizon Node Checker to know if my node is visible on the network?
https://explorer.horizonplatform.io/?page=nodecheck
Any advise would be greatly appreciated as I'm excited about being an active participant however am not versed in linux.
As posted to the Horizon forum I successfully followed the "how-to setup a node.." video on my Windows 7 Pro workstation with Symantec Endpoint firewall and a rule added to allow Port 7774-TCP inbound.
https://horizonplatform.io/topic/running-horizon-hallmark-node/
If Windows is supported is there any way beyond the Horizon Node Checker to know if my node is visible on the network?
https://explorer.horizonplatform.io/?page=nodecheck
Any advise would be greatly appreciated as I'm excited about being an active participant however am not versed in linux.
Do you have a public ip? Do you use UPnP? Could you please send me your IP?
I hadn't considered UPnP as a requirement for this to work and I see "UPnP Discovery" and "SSDP" Blocked in the Symantec Firewall with an option to allow both from private IP addresses. I can PM you my public IP however would like to understand the scope of what workstation service(s) will need to be exposed in order for this to work and if deemed too risky I would consider another adoption to running a hallmark node. Perhaps this is why I'm not reading about Windows hallmark nodes?
UPnP is not required.
The requirements for a public hallmarked node are a public accessible IP, an open port 7774, a hz wallet with a configured hallmark and an activated peer server listen on port 7774.The peer server is already enabled with the default settings.
If your PC is behind a router in a private network then you have to add a NAT rule for port 7774 manually or you enable UPnP.
I've seen alot about running a hallmark node on linux however I'm going on two days now waiting for my Windows-based node to be seen on the network and I'm now wondering if that's supported.
As posted to the Horizon forum I successfully followed the "how-to setup a node.." video on my Windows 7 Pro workstation with Symantec Endpoint firewall and a rule added to allow Port 7774-TCP inbound.
https://horizonplatform.io/topic/running-horizon-hallmark-node/
If Windows is supported is there any way beyond the Horizon Node Checker to know if my node is visible on the network?
https://explorer.horizonplatform.io/?page=nodecheck
Any advise would be greatly appreciated as I'm excited about being an active participant however am not versed in linux.
As posted to the Horizon forum I successfully followed the "how-to setup a node.." video on my Windows 7 Pro workstation with Symantec Endpoint firewall and a rule added to allow Port 7774-TCP inbound.
https://horizonplatform.io/topic/running-horizon-hallmark-node/
If Windows is supported is there any way beyond the Horizon Node Checker to know if my node is visible on the network?
https://explorer.horizonplatform.io/?page=nodecheck
Any advise would be greatly appreciated as I'm excited about being an active participant however am not versed in linux.
Do you have a public ip? Do you use UPnP? Could you please send me your IP?
I hadn't considered UPnP as a requirement for this to work and I see "UPnP Discovery" and "SSDP" Blocked in the Symantec Firewall with an option to allow both from private IP addresses. I can PM you my public IP however would like to understand the scope of what workstation service(s) will need to be exposed in order for this to work and if deemed too risky I would consider another adoption to running a hallmark node. Perhaps this is why I'm not reading about Windows hallmark nodes?
When Horizon team decides to gracefully shut down on the NXT asset exchange, please post notification and redemption process:
* in this thread
* on asx.nhzcrypto.org website
* and, on https://nxtforum.org/assets-board/(ann)-nhz-asset/
Simply stating 'it's been shut down' with no notice or warning is a terrible disservice to your users. Please come up with a better plan.
The dacx was shut down by us and the asx just stopped working because the previous owner and developer, SilverNXT abandoned the project and vanished last October.* in this thread
* on asx.nhzcrypto.org website
* and, on https://nxtforum.org/assets-board/(ann)-nhz-asset/
Simply stating 'it's been shut down' with no notice or warning is a terrible disservice to your users. Please come up with a better plan.
We know there's about 2.5M HZ left on the account, but currently have no idea how many transactions have been missed.
We will port it over to HZx as soon as that's done and see if we can catch up on what was missed in the meantime.
Okay. Thank you!
Has there been any progress on this? I sent my nhz-assets to the redemption address in early march but still haven't received my NHZ yet.
thanks
hey, are nhz-asset redemptions going to be honored or not? If yes, please do it soon. If not, why not?
I bought nhz-asset in could faith, and I'm missing out on 10% interest for over 8 weeks now.
I've seen alot about running a hallmark node on linux however I'm going on two days now waiting for my Windows-based node to be seen on the network and I'm now wondering if that's supported.
As posted to the Horizon forum I successfully followed the "how-to setup a node.." video on my Windows 7 Pro workstation with Symantec Endpoint firewall and a rule added to allow Port 7774-TCP inbound.
https://horizonplatform.io/topic/running-horizon-hallmark-node/
If Windows is supported is there any way beyond the Horizon Node Checker to know if my node is visible on the network?
https://explorer.horizonplatform.io/?page=nodecheck
Any advise would be greatly appreciated as I'm excited about being an active participant however am not versed in linux.
As posted to the Horizon forum I successfully followed the "how-to setup a node.." video on my Windows 7 Pro workstation with Symantec Endpoint firewall and a rule added to allow Port 7774-TCP inbound.
https://horizonplatform.io/topic/running-horizon-hallmark-node/
If Windows is supported is there any way beyond the Horizon Node Checker to know if my node is visible on the network?
https://explorer.horizonplatform.io/?page=nodecheck
Any advise would be greatly appreciated as I'm excited about being an active participant however am not versed in linux.
Do you have a public ip? Do you use UPnP? Could you please send me your IP?
I've seen alot about running a hallmark node on linux however I'm going on two days now waiting for my Windows-based node to be seen on the network and I'm now wondering if that's supported.
As posted to the Horizon forum I successfully followed the "how-to setup a node.." video on my Windows 7 Pro workstation with Symantec Endpoint firewall and a rule added to allow Port 7774-TCP inbound.
https://horizonplatform.io/topic/running-horizon-hallmark-node/
If Windows is supported is there any way beyond the Horizon Node Checker to know if my node is visible on the network?
https://explorer.horizonplatform.io/?page=nodecheck
Any advise would be greatly appreciated as I'm excited about being an active participant however am not versed in linux.
As posted to the Horizon forum I successfully followed the "how-to setup a node.." video on my Windows 7 Pro workstation with Symantec Endpoint firewall and a rule added to allow Port 7774-TCP inbound.
https://horizonplatform.io/topic/running-horizon-hallmark-node/
If Windows is supported is there any way beyond the Horizon Node Checker to know if my node is visible on the network?
https://explorer.horizonplatform.io/?page=nodecheck
Any advise would be greatly appreciated as I'm excited about being an active participant however am not versed in linux.
Hi guys,
Is there any explanatory guide for HZ 3.9.1 node installation to Linux? I have already used horizon.io guide which didnt work perfectly for me. I need small installation script that makes it easily click and installed . Ive used some before but since there were some changes filenames ; I just cannot use it newer versions.
Is there any explanatory guide for HZ 3.9.1 node installation to Linux? I have already used horizon.io guide which didnt work perfectly for me. I need small installation script that makes it easily click and installed . Ive used some before but since there were some changes filenames ; I just cannot use it newer versions.
The installation procedure depends on your linux distribution.
You have to install a Java 7 JRE or JDK.
Then download and extract hz wallet. wget is your friend.
Start the hz wallet with ./run.sh. or better with screen:
screen -S hz -L ./run.sh
Ctrl-A d to deattach the session
'screen -rd' to reattach
A more comprehensive guide to prepare a node from scratch on a Ubuntu 14.04 LTS system:
https://docs.google.com/document/d/12gPVnZlGr_Q83WGQ0puDgW7VVxcRgi33L4yT7xwUDTA/edit
Hi BDCoinMiner
I've just checked:
All the hallmarks of your nodes are valid and the announced IP the IP of the node. There should be no problem.
cat screenlog.0 | grep 'Hallmark' | grep "doesn't match" | grep '104.194.247' | wc -l
2145
Outgoing connections are using the IP 104.194.247.230. This leads to an announced address change.
The new announced address for a 104.194.247.xxx IP is then 104.194.247.230.
The saved hallmark host doesn't match with the host 104.194.247.230.
A symptom is that you don't see a weight value in peers list for such IPs.
In the above case (104.194.247.xxx) the balance of the hallmark account is currently too small to see a weight anyway.
For the sake of completeness the hallmark is valid:
Code:
curl --data '{"shareAddress":true,"platform":"PC","protocol":1,"application":"TEST","requestType":"getInfo","version":"NHZ V3.9.1"}' http://104.194.247.246:7774/nhz
{"shareAddress":true,"platform":"NHZBox246","application":"NRS","hallmark":"ac93dac7e5f408a3a363cd19c0b7419d0f3edcbcbb7ccdf89ffb669257fc0f5b0f003130342e3139342e3234372e32343600401f00b9773301c6849cfa3426b1416ad4cca38329a0ad161a29c7f9219483a89283a7521a49e300db10992dd426d47d32f1a85e5fdeb280db403a32fe1b7518bde33c12c36fa7f8","announcedAddress":"104.194.247.246","version":"NHZ V3.9.1"}
{"shareAddress":true,"platform":"NHZBox246","application":"NRS","hallmark":"ac93dac7e5f408a3a363cd19c0b7419d0f3edcbcbb7ccdf89ffb669257fc0f5b0f003130342e3139342e3234372e32343600401f00b9773301c6849cfa3426b1416ad4cca38329a0ad161a29c7f9219483a89283a7521a49e300db10992dd426d47d32f1a85e5fdeb280db403a32fe1b7518bde33c12c36fa7f8","announcedAddress":"104.194.247.246","version":"NHZ V3.9.1"}
Ive used some before but since there were some changes filenames ; I just cannot use it newer versions.
I don't think there is any chang on 'filename' on newer versions of HZ node software. Note even config file itself. Only diffrence is in directory name something like hz-v3.9 to hz-v3.9.1 . Also if you have old v3.8 config file, it will still works on 3.9.1. How many node you are planing to setup? I can do it for you if you preffer. If you wans to run 10-20 even thousands, an anouncement of bounty for that work will highly appreciable.
You can also give here the kink of guide you tried earlier, I will try to modifi according to current versions.
Cheers!
NB: I am rechable on bauani AT Gmail for anything more private to discuss.
Hi guys,
Is there any explanatory guide for HZ 3.9.1 node installation to Linux? I have already used horizon.io guide which didnt work perfectly for me. I need small installation script that makes it easily click and installed . Ive used some before but since there were some changes filenames ; I just cannot use it newer versions.
Is there any explanatory guide for HZ 3.9.1 node installation to Linux? I have already used horizon.io guide which didnt work perfectly for me. I need small installation script that makes it easily click and installed . Ive used some before but since there were some changes filenames ; I just cannot use it newer versions.
Xander supplied this a couple months ago....https://bitbucket.org/n00bsys0p/nhz-auto-hallmark
I'm not sure it's set up for the latest version of HZ, it might need minor modification.
Should be simple to modify though - there's just a download URL in there.
Hi guys,
Is there any explanatory guide for HZ 3.9.1 node installation to Linux? I have already used horizon.io guide which didnt work perfectly for me. I need small installation script that makes it easily click and installed . Ive used some before but since there were some changes filenames ; I just cannot use it newer versions.
Is there any explanatory guide for HZ 3.9.1 node installation to Linux? I have already used horizon.io guide which didnt work perfectly for me. I need small installation script that makes it easily click and installed . Ive used some before but since there were some changes filenames ; I just cannot use it newer versions.
Any news about the node checker json API?
I have asked this question quite a few times, but unfortunately no answer.
There is a JSON API, available starting https://explorer.horizonplatform.io/api.php.
The requests except "page=nodecheck" are running well, but "nodecheck" causes an error:
{"error":"Failed to connect to node - is HZ running? Did you open port 7774?"}
Ok, I can use "WEB scraping" using the normal NodeChecker website, but this is ony a workaround.
Is there a chance to re-enable the JSON NodeChecker-API?
When the NodeChecker API will be available again?
e.g.
https://explorer.horizonplatform.io/api.php?page=nodecheck&nodeAddress=78.138.90.142
e.g.
https://explorer.horizonplatform.io/api.php?page=nodecheck&nodeAddress=78.138.90.142
Try here
https://explorer.horizonplatform.io/?page=nodecheck
I've seen this, but I mean the API
https://explorer.horizonplatform.io/api.php?page=nodecheck&nodeAddress=78.138.90.142
Any news about the node checker json API?
I have asked this question quite a few times, but unfortunately no answer.
There is a JSON API, available starting https://explorer.horizonplatform.io/api.php.
The requests except "page=nodecheck" are running well, but "nodecheck" causes an error:
{"error":"Failed to connect to node - is HZ running? Did you open port 7774?"}
Ok, I can use "WEB scraping" using the normal NodeChecker website, but this is ony a workaround.
Is there a chance to re-enable the JSON NodeChecker-API?
I see many hallmark related issues for your nodes. It seems that your node sends requests and responses only from one ip address, but announces always different ip addresses.
A hallmark includes an ip address and will not get verified if the sending host and hallmarked host does not match.
Hi MaWo
Thanks for your responce. The log you posted was due to my activity of let unlisted peer to get listed. As new nodes were not shows up on official nodechecker script, I used my oldest and most used node to anounce new IP address to network. Odd is, it works! As soon I anounce new IP address from that old node (as well as new IP address also setup earlier) within few hour it shows up on nodechecker.
Also today I got paid of total 31 nodes without any problem!
For me, todays status is what I was looking for by using diffrent configure:) let's wait and hope for tomorrow.
Hi BDCoinMiner
I've just checked:
All the hallmarks of your nodes are valid and the announced IP the IP of the node. There should be no problem.
The nodes are sort of like perpetual mining in a way, and there will be problems and glitches just like when people are mining. It does sort of drown out the good news we post, and people need to expect issues if they want to run nodes just like if you were mining for months and months. Counterpoint to a different thread is at least node complaints bump the thread and they are just people trying to get their HZ. I would say just keep the thread as is, and try to quote the good news more?
Very logical said. Anything 'Good News' posted on this ANN thread act as reference of development. To know more details of current development people normally explore official website and news sections. That was one way communication. Forums are the way of inter exchange query, complaints and shearing ideas.Horizon devs team might find node bounty related query as negative impact with bulk of uninteresting data, for people like me it is as important as development news. Devs might have enough HZ holdings came from dev's share where daily payments of node bounty is tiny enough to ignore!
But most of HZ fan like me have only option of getting HZ is daily node bounty payment. Both other 'StackHolder Bounty' and 'Forging Incomes' are dominated by initial big holder. Also those two daily incomes have no problems at all!!!
And for those reason, we can expects domination of node bounty related posting on this ANN thread. Other then moving towards new thread, HZ team can 'control' volume of node bounty posting by solving bounty payment problems and keeping continued flow of daily node bounty payment will also keep ANN threads clean!
Now I think devs know what to do:)
Cheers to HZ team member!
Actually this won't work if I do it, Bitcointalk moderators delete it. (Even though I am on the team and trying to share News) I do wish all the node stuff worked perfectly all the time, maybe community members can comment more on good news items, as I guess we can only mention it one time and not comment on the news itself. Moderators here seem to like deleting my posts a lot.
I guess at least they read everything I post, so that shows they really care... I see many hallmark related issues for your nodes. It seems that your node sends requests and responses only from one ip address, but announces always different ip addresses.
A hallmark includes an ip address and will not get verified if the sending host and hallmarked host does not match.
Code:
2015-05-16 08:46:40 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.238 to 104.194.247.233
2015-05-16 08:46:40 FINE: Hallmark host 104.194.247.233 doesn't match 104.194.247.230
2015-05-16 08:48:25 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.233 to 104.194.247.253
2015-05-16 08:48:25 FINE: Hallmark host 104.194.247.253 doesn't match 104.194.247.230
2015-05-16 08:49:30 FINE: Peer 104.194.247.248 changed announced address from 104.194.247.248 to 104.194.247.250
2015-05-16 08:49:30 FINE: Hallmark host 104.194.247.250 doesn't match 104.194.247.248
2015-05-16 08:51:09 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.253 to 104.194.247.234
2015-05-16 08:51:09 FINE: Hallmark host 104.194.247.234 doesn't match 104.194.247.230
2015-05-16 08:51:26 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.234 to 104.194.247.236
2015-05-16 08:51:26 FINE: Hallmark host 104.194.247.236 doesn't match 104.194.247.230
2015-05-16 08:52:09 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.236 to 104.194.247.229
2015-05-16 08:52:09 FINE: Hallmark host 104.194.247.229 doesn't match 104.194.247.230
2015-05-16 08:52:10 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.229 to 104.194.247.231
2015-05-16 08:52:10 FINE: Hallmark host 104.194.247.231 doesn't match 104.194.247.230
2015-05-16 08:53:01 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.231 to 104.194.247.251
2015-05-16 08:53:01 FINE: Hallmark host 104.194.247.251 doesn't match 104.194.247.230
2015-05-16 08:53:06 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.251 to 104.194.247.254
2015-05-16 08:53:06 FINE: Hallmark host 104.194.247.254 doesn't match 104.194.247.230
2015-05-16 08:55:10 FINE: Hallmark host 104.194.247.244 doesn't match 104.194.247.245
2015-05-16 08:46:40 FINE: Hallmark host 104.194.247.233 doesn't match 104.194.247.230
2015-05-16 08:48:25 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.233 to 104.194.247.253
2015-05-16 08:48:25 FINE: Hallmark host 104.194.247.253 doesn't match 104.194.247.230
2015-05-16 08:49:30 FINE: Peer 104.194.247.248 changed announced address from 104.194.247.248 to 104.194.247.250
2015-05-16 08:49:30 FINE: Hallmark host 104.194.247.250 doesn't match 104.194.247.248
2015-05-16 08:51:09 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.253 to 104.194.247.234
2015-05-16 08:51:09 FINE: Hallmark host 104.194.247.234 doesn't match 104.194.247.230
2015-05-16 08:51:26 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.234 to 104.194.247.236
2015-05-16 08:51:26 FINE: Hallmark host 104.194.247.236 doesn't match 104.194.247.230
2015-05-16 08:52:09 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.236 to 104.194.247.229
2015-05-16 08:52:09 FINE: Hallmark host 104.194.247.229 doesn't match 104.194.247.230
2015-05-16 08:52:10 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.229 to 104.194.247.231
2015-05-16 08:52:10 FINE: Hallmark host 104.194.247.231 doesn't match 104.194.247.230
2015-05-16 08:53:01 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.231 to 104.194.247.251
2015-05-16 08:53:01 FINE: Hallmark host 104.194.247.251 doesn't match 104.194.247.230
2015-05-16 08:53:06 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.251 to 104.194.247.254
2015-05-16 08:53:06 FINE: Hallmark host 104.194.247.254 doesn't match 104.194.247.230
2015-05-16 08:55:10 FINE: Hallmark host 104.194.247.244 doesn't match 104.194.247.245
Thanks for your responce. The log you posted was due to my activity of let unlisted peer to get listed. As new nodes were not shows up on official nodechecker script, I used my oldest and most used node to anounce new IP address to network. Odd is, it works! As soon I anounce new IP address from that old node (as well as new IP address also setup earlier) within few hour it shows up on nodechecker.
Also today I got paid of total 31 nodes without any problem!
For me, todays status is what I was looking for by using diffrent configure:) let's wait and hope for tomorrow.
Hi BDCoinMiner
I've just checked:
All the hallmarks of your nodes are valid and the announced IP the IP of the node. There should be no problem.
The nodes are sort of like perpetual mining in a way, and there will be problems and glitches just like when people are mining. It does sort of drown out the good news we post, and people need to expect issues if they want to run nodes just like if you were mining for months and months. Counterpoint to a different thread is at least node complaints bump the thread and they are just people trying to get their HZ. I would say just keep the thread as is, and try to quote the good news more?
Very logical said. Anything 'Good News' posted on this ANN thread act as reference of development. To know more details of current development people normally explore official website and news sections. That was one way communication. Forums are the way of inter exchange query, complaints and shearing ideas.Horizon devs team might find node bounty related query as negative impact with bulk of uninteresting data, for people like me it is as important as development news. Devs might have enough HZ holdings came from dev's share where daily payments of node bounty is tiny enough to ignore!
But most of HZ fan like me have only option of getting HZ is daily node bounty payment. Both other 'StackHolder Bounty' and 'Forging Incomes' are dominated by initial big holder. Also those two daily incomes have no problems at all!!!
And for those reason, we can expects domination of node bounty related posting on this ANN thread. Other then moving towards new thread, HZ team can 'control' volume of node bounty posting by solving bounty payment problems and keeping continued flow of daily node bounty payment will also keep ANN threads clean!
Now I think devs know what to do:)
Cheers to HZ team member!
Another strange thing:
Almost all Most nodes from my v3.9.0 selection received a duplicate payment (2105 HZ) for two days.
If I have a look at my own nodes (v3.9.1), there are only payments of 1052 HZ (one day).
The node bounty script stopped 03:39:24 UTC, so only a part of my nodes got a payment.
What's wrong?
If I have a look at my own nodes (v3.9.1), there are only payments of 1052 HZ (one day).
The node bounty script stopped 03:39:24 UTC, so only a part of my nodes got a payment.
What's wrong?
Also having 31 nodes with v3.9.1, I only got paid for 9 (1052HZ each). Others are missing!
So with 500 to 600 HZ daily payment I used to get 15k to 17k HZ everyday; but with great @1052HZ today I only received 9.5k around:(
Hope any bug found when running for the 1st time after script update will fixed tomorrow and I will continue getting payment for all my online & updated nodes.
Cheers! Go HZ!
Debugging Info: IP address of my nodes are 104.194.247.227-254. Also if node bounty script 'add' IP address with payment as 'message' it will help multiple node runner to Identify which nodes are getting paid and which not.
I see many hallmark related issues for your nodes. It seems that your node sends requests and responses only from one ip address, but announces always different ip addresses.
A hallmark includes an ip address and will not get verified if the sending host and hallmarked host does not match.
Code:
2015-05-16 08:46:40 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.238 to 104.194.247.233
2015-05-16 08:46:40 FINE: Hallmark host 104.194.247.233 doesn't match 104.194.247.230
2015-05-16 08:48:25 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.233 to 104.194.247.253
2015-05-16 08:48:25 FINE: Hallmark host 104.194.247.253 doesn't match 104.194.247.230
2015-05-16 08:49:30 FINE: Peer 104.194.247.248 changed announced address from 104.194.247.248 to 104.194.247.250
2015-05-16 08:49:30 FINE: Hallmark host 104.194.247.250 doesn't match 104.194.247.248
2015-05-16 08:51:09 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.253 to 104.194.247.234
2015-05-16 08:51:09 FINE: Hallmark host 104.194.247.234 doesn't match 104.194.247.230
2015-05-16 08:51:26 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.234 to 104.194.247.236
2015-05-16 08:51:26 FINE: Hallmark host 104.194.247.236 doesn't match 104.194.247.230
2015-05-16 08:52:09 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.236 to 104.194.247.229
2015-05-16 08:52:09 FINE: Hallmark host 104.194.247.229 doesn't match 104.194.247.230
2015-05-16 08:52:10 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.229 to 104.194.247.231
2015-05-16 08:52:10 FINE: Hallmark host 104.194.247.231 doesn't match 104.194.247.230
2015-05-16 08:53:01 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.231 to 104.194.247.251
2015-05-16 08:53:01 FINE: Hallmark host 104.194.247.251 doesn't match 104.194.247.230
2015-05-16 08:53:06 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.251 to 104.194.247.254
2015-05-16 08:53:06 FINE: Hallmark host 104.194.247.254 doesn't match 104.194.247.230
2015-05-16 08:55:10 FINE: Hallmark host 104.194.247.244 doesn't match 104.194.247.245
2015-05-16 08:46:40 FINE: Hallmark host 104.194.247.233 doesn't match 104.194.247.230
2015-05-16 08:48:25 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.233 to 104.194.247.253
2015-05-16 08:48:25 FINE: Hallmark host 104.194.247.253 doesn't match 104.194.247.230
2015-05-16 08:49:30 FINE: Peer 104.194.247.248 changed announced address from 104.194.247.248 to 104.194.247.250
2015-05-16 08:49:30 FINE: Hallmark host 104.194.247.250 doesn't match 104.194.247.248
2015-05-16 08:51:09 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.253 to 104.194.247.234
2015-05-16 08:51:09 FINE: Hallmark host 104.194.247.234 doesn't match 104.194.247.230
2015-05-16 08:51:26 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.234 to 104.194.247.236
2015-05-16 08:51:26 FINE: Hallmark host 104.194.247.236 doesn't match 104.194.247.230
2015-05-16 08:52:09 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.236 to 104.194.247.229
2015-05-16 08:52:09 FINE: Hallmark host 104.194.247.229 doesn't match 104.194.247.230
2015-05-16 08:52:10 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.229 to 104.194.247.231
2015-05-16 08:52:10 FINE: Hallmark host 104.194.247.231 doesn't match 104.194.247.230
2015-05-16 08:53:01 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.231 to 104.194.247.251
2015-05-16 08:53:01 FINE: Hallmark host 104.194.247.251 doesn't match 104.194.247.230
2015-05-16 08:53:06 FINE: Peer 104.194.247.230 changed announced address from 104.194.247.251 to 104.194.247.254
2015-05-16 08:53:06 FINE: Hallmark host 104.194.247.254 doesn't match 104.194.247.230
2015-05-16 08:55:10 FINE: Hallmark host 104.194.247.244 doesn't match 104.194.247.245
Thanks for your responce. The log you posted was due to my activity of let unlisted peer to get listed. As new nodes were not shows up on official nodechecker script, I used my oldest and most used node to anounce new IP address to network. Odd is, it works! As soon I anounce new IP address from that old node (as well as new IP address also setup earlier) within few hour it shows up on nodechecker.
Also today I got paid of total 31 nodes without any problem!
For me, todays status is what I was looking for by using diffrent configure:) let's wait and hope for tomorrow.
Jump to: