Field's name and address info are incorrect on node graph explorer

yaeljiao commented 6 years ago

My field's config.ini is shown as below:

[field]
name =[CN]Jiao
IRIPort = 14265
IRIHostname = localhost
address = YVIVYCSRJVP9JBOLZ9LGMMKSXMYIFNGWIODVDQPZMCJJNRXDZCLMVSTUSWHNPWGYOOEQNP9MTKOYRMTFYKQSSAJNNY
port = 21310
pow = true
disableIRI = false

I checked my node's info on http://field.carriota.com/api/v1/graph:

{
  "createdOn": "2018-02-28T01:26:47.047Z",
  "iri": {
    "appVersion": "1.4.2.2",
    "latestMilestoneIndex": 359379,
    "latestSolidSubtangleMilestoneIndex": 359379,
    "isSynchronized": true
  },
  "field": {
    "publicId": "3053677ad6a58903",
    "version": "0.1.5",
    "name": "CarrIOTA Field Node #3053677ad6a58903",
    "disableIRI": false,
    "pow": false,
    "address": null
  },
  "neighbors": [
    "76e667cf838e3134",
    "62b4fbf76d184af8",
    "534f14307e08a886"
  ],
  "workDone": {
    "getInclusionStates": 23,
    "wereAddressesSpentFrom": 9,
    "findTransactions": 7,
    "getNodeInfo": 17,
    "getBalances": 1,
    "getTrytes": 54
  },
  "you": false
}

My field's name is marked as "CarrIOTA Field Node #3053677ad6a58903" and address is null It seems that the information is not correct.

romansemko commented 6 years ago

Try running your field with "customFieldId = true". It seems that another server has the same machine id (Image-based server)

Wait for 10-20 minutes for the information to update.

yaeljiao commented 6 years ago

I tried "customFieldId = true", but it's not working for this issue. Any other suggestion? I'm using Google Cloud for deployment.

New-older commented 6 years ago

I had the same problem in the past. Please see my fixing flow as below: lsof -i:21310 Kill ID pm2 start field -- --config /path/to/field-config.ini Pm2 save Pm2 monit (you can see the field service)

romansemko commented 6 years ago

@yaeljiao Did it solve your issue?

yaeljiao commented 6 years ago

Yes, @New-older 's comments solved my issue

SemkoDev / field.cli

Field's name and address info are incorrect on node graph explorer #26