antonionardella / iota-nelson-node Goto Github PK

Hi !

Just tried your project and I have an issue with nelson.cli:

12:36:44 PM.671 16600::IRI IRI not ready on iota:14265, retrying...

If I do the following I get at least a respond from iri:
root@mail:~/iota-nelson-node# docker exec -it nelson.cli /bin/sh
/ # wget http://iota:14265
Connecting to iota:14265 (172.18.0.7:14265)
wget: server returned error: HTTP/1.1 400 Bad Request

So IRI should be running and listening.

Also docker logs iota shows that iri is synching:
01/23 11:49:08.438 [main] INFO com.iota.iri.IRI - IOTA Node initialised correctly.
01/23 11:49:18.111 [pool-2-thread-2] INFO com.iota.iri.network.Node - toProcess = 0 , toBroadcast = 0 , toRequest = 0 , toReply = 0 / totalTransactions = 0

any idea what could be wrong ?

REMOTE_LIMIT_API = "interruptAttachingToTangle, attachToTangle" in the iota.ini

means that the commands are executable for the internet which is problematic:

removeNeighbors, addNeighbors, getNeighbors, setApiRateLimit

Firstly, before anything else. This project is amazing! Had started grafting a docker solution (feeble in comparison) and stumbled over this. Thank you!

To the issue. The nelson.gui is erroring with IRI not ready on localhost:14265, retrying... when checking the docker logs.
Attached and tested telnet localhost 14265 and its unable to connect. Running curl against http://localhost:14265 from the host returns successfully.

Any thoughts?

(Edit: should this be trying to connect to iota:14265 instead?)

I followed everything in your readme, but get this:

level=info ts=2018-03-09T13:22:17.96195575Z caller=main.go:220 msg="Starting Prometheus" version="(version=2.2.0, branch=HEAD, revision=f63e7db4cbdb616337ca877b306b9b96f7f4e381)"
level=info ts=2018-03-09T13:22:17.962102139Z caller=main.go:221 build_context="(go=go1.10, user=root@52af9f66ce71, date=20180308-16:40:42)"
level=info ts=2018-03-09T13:22:17.962175703Z caller=main.go:222 host_details="(Linux 3.10.102 #15254 SMP Fri Jan 26 06:46:44 CST 2018 x86_64 prometheus (none))"
level=info ts=2018-03-09T13:22:17.962219253Z caller=main.go:223 fd_limits="(soft=524288, hard=1048576)"
level=info ts=2018-03-09T13:22:18.074241532Z caller=main.go:504 msg="Starting TSDB ..."
level=info ts=2018-03-09T13:22:18.074989904Z caller=main.go:398 msg="Stopping scrape discovery manager..."
level=info ts=2018-03-09T13:22:18.075200182Z caller=main.go:411 msg="Stopping notify discovery manager..."
level=info ts=2018-03-09T13:22:18.07525607Z caller=main.go:432 msg="Stopping scrape manager..."
level=info ts=2018-03-09T13:22:18.075304196Z caller=manager.go:460 component="rule manager" msg="Stopping rule manager..."
level=info ts=2018-03-09T13:22:18.075384659Z caller=manager.go:466 component="rule manager" msg="Rule manager stopped"
level=info ts=2018-03-09T13:22:18.075443998Z caller=notifier.go:512 component=notifier msg="Stopping notification manager..."
level=info ts=2018-03-09T13:22:18.075539511Z caller=web.go:382 component=web msg="Start listening for connections" address=0.0.0.0:9090
level=info ts=2018-03-09T13:22:18.084396889Z caller=main.go:394 msg="Scrape discovery manager stopped"
level=info ts=2018-03-09T13:22:18.084607142Z caller=main.go:407 msg="Notify discovery manager stopped"
level=info ts=2018-03-09T13:22:18.084679155Z caller=main.go:426 msg="Scrape manager stopped"
level=info ts=2018-03-09T13:22:18.084744731Z caller=main.go:573 msg="Notifier manager stopped"
level=error ts=2018-03-09T13:22:18.084799269Z caller=main.go:582 err="Opening storage failed open DB in /data: open /data/724784799: permission denied"
level=info ts=2018-03-09T13:22:18.084898183Z caller=main.go:584 msg="See you next time!"

Thank you

when I run $ docker logs nelson I get no such container. Whereas $ docker logs iota works fine.

I'm trying to connect this node to the IOTA Wallet (BETA) for Android (https://play.google.com/store/apps/details?id=org.iota.wallet)

App reports that this command is not available on the node.

I've been trying to find the option to enable this and per the iota help it should be the "remote" flag.

But as far as I can tell this flag is set true in the used iota.ini in the repo.

Any idea why that might be?

If i am right port 9090 and 9100 should't be open for public. But they are.

I suppose this happens due https://askubuntu.com/questions/652556/uncomplicated-firewall-ufw-is-not-blocking-anything-when-using-docker

10:03:25.825 16600::IRI IRI not ready on iota:14265, retrying...

curl http://iota:14265
{"error":"Invalid API Version","duration":0}

Ubuntu 16

Maybe the container is other from the host?
i.e., different ip?
so prohibiting removeNeighbors, addNeighbors, getNeighbors stops nelson?

I followed the instruction for installation, but in Grafana i see "No data points" on most entries.

In the Row IRI Node Stats (Lastest Milestone and so on) i can only see N/A.

Grafana Log shows:
t=2018-02-18T23:37:44+0100 lvl=eror msg="provisioned dashboard json files cannot contain id" logger=provisioning.dashboard type=file name=IOTA0mq

https://imgur.com/a/0bcQy
https://imgur.com/a/6Xj84

After I run the described setup I get the following error when I try to access http://MYPIP:3000
I changed nothing except for the configuration files according to the README.

Nelson Monitor
Error while connecting to Nelson
Error: Received erroneous response from Nelson
    at Request._callback (/usr/src/nelson.mon/routes/index.js:22:30)
    at Request.self.callback (/usr/src/nelson.mon/node_modules/request/request.js:186:22)
    at emitTwo (events.js:126:13)
    at Request.emit (events.js:214:7)
    at Request.<anonymous> (/usr/src/nelson.mon/node_modules/request/request.js:1163:10)
    at emitOne (events.js:116:13)
    at Request.emit (events.js:211:7)
    at IncomingMessage.<anonymous> (/usr/src/nelson.mon/node_modules/request/request.js:1085:12)
    at Object.onceWrapper (events.js:313:30)
    at emitNone (events.js:111:20)

I just followed the usage section to deploy IOTA full node on my computer with Ubuntu 16.04, but I found the node never fully synchronized. When I tried to get node information from API, the number of latestSolidSubtangleMilestoneIndex and latestMilestoneIndex is never consistent. latestMilestoneIndex is constantly increasing, but latestSolidSubtangleMilestoneIndex stuck.

Is there any additional configuration I should make before doing docker-compose up -d?

Thanks!

luc@luc-As:~/iota-nelson-node$ sudo docker-compose up -d
[sudo] пароль для luc:
Recreating iota_prom-iotaexp
iota_prom-nodeexp is up-to-date
Recreating iota_nelson.cli
iota_nelson.gui is up-to-date
Recreating iota_field.cli
Recreating iota_iri
WARNING: Connection pool is full, discarding connection: localhost
WARNING: Connection pool is full, discarding connection: localhost
Recreating iota_prometheus
Recreating iota_grafana

and i don't see nothing in Grafana
say N/A on all windows

Is there a particular reason why you chose a value of 7 for MAX_PEERS in the IRI configuration instead of the default of 0?
When run in testnet, this allows 7 additional neighbors to connect without having them configured as neighbors. Apparently, this has no influence for TESTNET = false, but it still might be favorable to set it to 0 or remove it from iota.ini and use the default.

I am running the node on the digitialocean server.

Pulling nelson.mon (ioiobzit/nelson.mon:0.0.2)...
ERROR: manifest for ioiobzit/nelson.mon:0.0.2 not found

how to solve the issue?

I tried to reduce the CPU usage, by adding some lines to the docker-compose.yml:

deploy: resources: limits: cpus: '0.3'

To reduce the consumed cpu resources (because otherwise, my home server is completely useless in all other tasks he is doing).

It doesn't work, apparently because the "version" at the top is outdated (2 and not 3). I am a docker beginner, but could you probably come up with a solution to make that possible?

GREAT work btw! I love this approach.

Suggestion: I would explain, how we can "minimalize" this, to give the node the max amount of resources. The dashboard and whatever fancy stuff won't be needed by anyone I guess. I myself just removed the entries from the docker-compose.yml file, but not sure if that works.

Hi,

I am trying to send a transaction using the js library and being connect to my iota nelson node. I got the following error :

Error: Request Error: starting tip failed consistency check: SWLTULJIWPOPOCPSVCTDXRDGHKHCARGGY9NMMLQW9DEBNTZRNYVGTXZK9ZXSXMACQHPSNEZDFUNV99999
at Object.requestError (/home/pi/IOTACOFFEE/iota.lib.js/lib/errors/requestErrors.js:11:12)
at makeRequest.prepareResult (/home/pi/IOTACOFFEE/iota.lib.js/lib/utils/makeRequest.js:293:24)
at exports.XMLHttpRequest.request.onreadystatechange (/home/pi/IOTACOFFEE/iota.lib.js/lib/utils/makeRequest.js:71:25)
at exports.XMLHttpRequest.dispatchEvent (/home/pi/IOTACOFFEE/iota.lib.js/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:591:25)
at setState (/home/pi/IOTACOFFEE/iota.lib.js/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:610:14)
at IncomingMessage. (/home/pi/IOTACOFFEE/iota.lib.js/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:447:13)
at emitNone (events.js:110:20)
at IncomingMessage.emit (events.js:207:7)
at endReadableNT (_stream_readable.js:1047:12)
at _combinedTickCallback (internal/process/next_tick.js:102:11)

Hello,
I need help to solve a problem. I was trying to run command docker-compose up -d. I followed all steps from this page https://github.com/ioiobzit/iota-nelson-node. All this is done on the server and attached you can find picture of problem that occurs. Can you help me solve this? Thank you.
Best regards,
Nermina

Creating iota_iri ...
Creating iota_nelson.gui ...
Creating iota_prom-nodeexp ... error
Creating iota_prom-iotaexp ...
Creating iota_nelson.cli ...
Creating iota_field.cli ...

Creating iota_nelson.gui ... done
h'
Creating iota_iri ... error
ERROR: for iota_nelson.cli Cannot create container for service nelson.cli: b'Mount denied:\nThe source path "\\etc\\localtime:/etc/localtime"\nis not a valid Creating iota_field.cli ... error

ERROR: for iota_field.cli Cannot create container for service field.cli: b'Mount denied:\nThe source path "\\etc\\localtime:/etc/localtime"\nis not a valid WiCreating iota_prom-iotaexp ... error

ERROR: for iota_iri Cannot create container for service iota: b'Mount denied:\nThe source path "\\etc\\localtime:/etc/localtime"\nis not a valid Windows path'

ERROR: for iota_prom-iotaexp Cannot create container for service iota-prom-exporter: b'Mount denied:\nThe source path "\\etc\\localtime:/etc/localtime"\nis not a valid Windows path'

ERROR: for node-exporter Cannot create container for service node-exporter: b'Mount denied:\nThe source path "\\proc:/host/proc"\nis not a valid Windows path'

ERROR: for nelson.cli Cannot create container for service nelson.cli: b'Mount denied:\nThe source path "\\etc\\localtime:/etc/localtime"\nis not a valid Windows path'

ERROR: for field.cli Cannot create container for service field.cli: b'Mount denied:\nThe source path "\\etc\\localtime:/etc/localtime"\nis not a valid Windows path'

ERROR: for iota Cannot create container for service iota: b'Mount denied:\nThe source path "\\etc\\localtime:/etc/localtime"\nis not a valid Windows path'

ERROR: for iota-prom-exporter Cannot create container for service iota-prom-exporter: b'Mount denied:\nThe source path "\\etc\\localtime:/etc/localtime"\nis not a valid Windows path'
Encountered errors while bringing up the project.

Hi,

your GitLab link seems to be broken, i get a 404 error: https://gitlab.com/antonionardella/iota-nelson-node

Best regards
Matthias