elective-stereophonic
elective-stereophonic
NXT node issues
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Nxt Client: Nxt 1.11.15

Author Topic: NXT node issues  (Read 734 times)

schoad

  • Jr. Member
  • **
  • Karma: +0/-0
  • Offline Offline
  • Posts: 28
    • View Profile
NXT node issues
« on: June 08, 2018, 04:36:14 pm »

I've currently deployed 6 nxtnode on VPS since approx 12 months.
Starting with the latest update, it seems that not all nodes are working properly.

On https://nxtportal.org/peers/ all my nodes are listed.

Flags (as expected):
"HALLMARK","PRUNABLE","API","API_SSL","CORS"

Pulling the peer information via API:
Code: [Select]
{"hallmark":"e5e172cea845c79976a2498c47d4c77b5088f088a9f1ee630629520c51e4cb1613006e78746e6f64653030322e64646e73732e6575e80300001aee3301919e3a686741bb51b21f79666ef98d6139fbbedbedfa3cd3426939c5dacebae207744627c4be4258154a9c71a44154207e11a22c21530de5706bd8e6d8463dd767","downloadedVolume":4765619,"address":"195.181.246.128","inbound":true,"blockchainState":"UP_TO_DATE","weight":1675,"uploadedVolume":387016,"services":["HALLMARK","PRUNABLE","API","API_SSL","CORS"],"version":"1.11.14","platform":"nxtnode","inboundWebSocket":true,"apiSSLPort":7876,"lastUpdated":143179360,"blacklisted":false,"announcedAddress":"nxtnode002.ddnss.eu","apiPort":7878,"application":"NRS","port":7874,"outboundWebSocket":true,"lastConnectAttempt":143179360,"state":1,"shareAddress":true},

{"hallmark":"e5e172cea845c79976a2498c47d4c77b5088f088a9f1ee630629520c51e4cb1613006e78746e6f64653030332e64646e73732e6575e80300001aee33014bfc6df6f9dd0d7a4f4e3c95d5d345279c52f2c1639bbb853afd059991b836cb0a0e0eb78d9bfc5b018f7444297afb46b66310d9c609aef3247ce06063e70b8e75","downloadedVolume":4863864,"address":"212.24.98.206","inbound":true,"blockchainState":"UP_TO_DATE","weight":1675,"uploadedVolume":4736911,"services":["HALLMARK","PRUNABLE","API","API_SSL","CORS"],"version":"1.11.14","platform":"nxtnode","inboundWebSocket":true,"apiSSLPort":7876,"lastUpdated":143179200,"blacklisted":false,"announcedAddress":"nxtnode003.ddnss.eu","apiPort":7878,"application":"NRS","port":7874,"outboundWebSocket":true,"lastConnectAttempt":143179200,"state":1,"shareAddress":true},

{"hallmark":"e5e172cea845c79976a2498c47d4c77b5088f088a9f1ee630629520c51e4cb1613006e78746e6f64653030342e64646e73732e6575e80300001aee33014ca9bea0665800a41f656338e98109e17b98fba0ae2392120b4ffe278575adf1002066282bd9e30a664d626e479caaa7171bddc12d0e0287285ddd973210702732","downloadedVolume":4746344,"address":"195.181.243.224","inbound":true,"blockchainState":"UP_TO_DATE","weight":2010,"uploadedVolume":4867080,"services":["HALLMARK","PRUNABLE","API","API_SSL","CORS"],"version":"1.11.14","platform":"nxtnode","inboundWebSocket":true,"apiSSLPort":7876,"lastUpdated":143179200,"blacklisted":false,"announcedAddress":"nxtnode004.ddnss.eu","apiPort":7878,"application":"NRS","port":7874,"outboundWebSocket":true,"lastConnectAttempt":143172998,"state":1,"shareAddress":true},

{"hallmark":"e5e172cea845c79976a2498c47d4c77b5088f088a9f1ee630629520c51e4cb1613006e78746e6f64653030352e64646e73732e6575e80300001aee3301f85e4681e89763c3c285a2db838c614f59798afc8a0adcc68d681c57648b3d410da2b285b722de0dcba356c9f0c2164633514785cf2247a6e705fc3e618b8b9dc4","downloadedVolume":4744205,"address":"94.176.235.119","inbound":true,"blockchainState":"UP_TO_DATE","weight":1675,"uploadedVolume":406051,"services":["HALLMARK","PRUNABLE","API","API_SSL","CORS"],"version":"1.11.14","platform":"nxtnode","inboundWebSocket":true,"apiSSLPort":7876,"lastUpdated":143178277,"blacklisted":false,"announcedAddress":"nxtnode005.ddnss.eu","apiPort":7878,"application":"NRS","port":7874,"outboundWebSocket":true,"lastConnectAttempt":143174659,"state":1,"shareAddress":true},

{"hallmark":"e5e172cea845c79976a2498c47d4c77b5088f088a9f1ee630629520c51e4cb1613006e78746e6f64653030362e64646e73732e6575e80300001aee3301792d2c05495799e40f3e7d59411d94c36c934c98a5a16b2012eb32eaa15e282b0abfe4c5d326d6d4f2b4eecec88805465bf14acfa365a559a508c12d7506faa3c2","downloadedVolume":1115995,"address":"23.94.175.17","inbound":true,"blockchainState":"UP_TO_DATE","weight":1675,"uploadedVolume":546301,"services":["HALLMARK","PRUNABLE","API","API_SSL","CORS"],"version":"1.11.14","platform":"nxtnode","inboundWebSocket":true,"apiSSLPort":7876,"lastUpdated":143176914,"blacklisted":false,"announcedAddress":"nxtnode006.ddnss.eu","apiPort":7878,"application":"NRS","port":7874,"outboundWebSocket":false,"lastConnectAttempt":143179350,"state":0,"shareAddress":true}

{"hallmark":"e5e172cea845c79976a2498c47d4c77b5088f088a9f1ee630629520c51e4cb1613006e78746e6f64653030372e64646e73732e6575e80300001aee3301e4de239eb002e7e8c6806e84d2b54706ff889c82e85f029e7ba5bda3ff3fb08401f8057b58436bb1163c9c7a682339055ec057358d134033294ca4219e7864d03e","downloadedVolume":3889154,"address":"23.94.175.53","inbound":true,"blockchainState":"UP_TO_DATE","weight":1675,"uploadedVolume":884085,"services":["HALLMARK","PRUNABLE","API","API_SSL","CORS"],"version":"1.11.14","platform":"nxtnode","inboundWebSocket":true,"apiSSLPort":7876,"lastUpdated":143176963,"blacklisted":false,"announcedAddress":"nxtnode007.ddnss.eu","apiPort":7878,"application":"NRS","port":7874,"outboundWebSocket":false,"lastConnectAttempt":143179080,"state":0,"shareAddress":true},

As you can see, 2 nodes are in state 0.
How can I change that? The nodes are up and running (can't find any errors in my screen sessions).

https://nxtnode006.ddnss.eu:7876/index.html
https://nxtnode007.ddnss.eu:7876/index.html

Logged

schoad

  • Jr. Member
  • **
  • Karma: +0/-0
  • Offline Offline
  • Posts: 28
    • View Profile
Re: NXT node issues
« Reply #1 on: June 08, 2018, 04:49:12 pm »

Load time is pretty bad!

Ping test yield approx. 100ms. That's ok.
iPerf tests between home & VPS results in 50-100Mbit/s. Should be enough for the current number of peers connected (> 130).
« Last Edit: June 08, 2018, 05:25:36 pm by schoad »
Logged

petko

  • Jr. Member
  • **
  • Karma: +24/-0
  • Offline Offline
  • Posts: 94
    • View Profile
    • My blog
Re: NXT node issues
« Reply #2 on: June 09, 2018, 12:16:37 pm »

Whose node API do you pull the peers information from? Apparently that node is not connected to 2 of your nodes, which is normal (we don't want all nodes to be connected to all other nodes). You can force a node to connect to some other node(s) only if that node is under your control. Use the addPeer API for that (or the "Add Peer" button in Peers screen).

Currently requests to your nodes time out from here.
Logged

schoad

  • Jr. Member
  • **
  • Karma: +0/-0
  • Offline Offline
  • Posts: 28
    • View Profile
Re: NXT node issues
« Reply #3 on: June 09, 2018, 02:53:55 pm »

The issue is that my NSC payouts are not as expected. And I suspect that the reason is that the requested for peer information is not always connected to my nodes.
Logged
 

elective-stereophonic
elective-stereophonic
assembly
assembly