greensheep
|
|
Group: Forum Members
Posts: 1,
Visits: 0
|
1) Can anyone give some information on Contabo mentioned in the original guide? Their prices look suspiciously good for what they're offering. Most reviews are older, but from what I can tell, they oversell and aren't reliable? Was hoping someone would have a more recent view on this. 1a) How reliable are they? 2) What other vps providers are other people using? 3) How intensive is the full node? How much cpu can I limit it before it's no longer feasible? I'm thinking of getting a vps with more resources so I can run my other apps/servers alongside the full node, but obviously the apps/servers should have a higher priority over the full node (no offense lol).
|
|
|
mixim
|
|
Group: Forum Members
Posts: 6,
Visits: 8
|
Hi greensheep, i run my VPS M (SSD boosted) with a full IOTA-node. With Contabo as provider i am very pleased. Never had a problem with reliability. But if u run ur IOTA-node (provider is irrelevant) limit the CPU-usage like described here: https://forum.helloiota.com/post/6261the service sometimes uses much CPU (up to 100 %), so espacially if u have other services on the server and don't want ur server be blocked i recommend to add the two attributes to limit CPUtime for IOTA-service. Cheers, MiXiM
|
|
|
Carpincho
|
|
Group: Moderators
Posts: 33,
Visits: 122
|
+x1) Can anyone give some information on Contabo mentioned in the original guide? Their prices look suspiciously good for what they're offering. Most reviews are older, but from what I can tell, they oversell and aren't reliable? Was hoping someone would have a more recent view on this. 1a) How reliable are they? 2) What other vps providers are other people using? 3) How intensive is the full node? How much cpu can I limit it before it's no longer feasible? I'm thinking of getting a vps with more resources so I can run my other apps/servers alongside the full node, but obviously the apps/servers should have a higher priority over the full node (no offense lol). For me it works nice. The plan used in the tutorial is fine to run a FN and help the network but if you wanna use it a lot and you are planning to connect many wallets to it you should go with a higher resources plan. Before this VPS I tryied a Digital Ocean instance for the same price. That was really bad. So, for about 10 USD Contabo is the best I had so far. Please feel free to recommend other better solutions!
|
|
|
xgarb
|
|
Group: Forum Members
Posts: 6,
Visits: 0
|
What commands should I use to update to the newest version of IRI?
|
|
|
Carpincho
|
|
Group: Moderators
Posts: 33,
Visits: 122
|
+xWhat commands should I use to update to the newest version of IRI? Just download the already compiled version and place it in the same folder. Then change the java -jar command to match the new IRI name. Go to your target directory and do this: wget https://github.com/iotaledger/iri/releases/download/v1.4.1.4/iri-1.4.1.4.jar java -jar iri-1.4.1.4.jar -c iri.ini
|
|
|
frha
|
|
Group: Forum Members
Posts: 1,
Visits: 0
|
Regardless of which 'version' of IRI you run - buildt or downloaded - NEVER run this as the 'root' -user.
|
|
|
NickM
|
|
Group: Forum Members
Posts: 7,
Visits: 9
|
Getting this error. java.lang.RuntimeException: java.net.BindException: Cannot assign requested address at io.undertow.Undertow.start(Undertow.java:203) ~[iri-1.4.1.4.jar:na] at com.iota.iri.service.API.init(API.java:152) ~[iri-1.4.1.4.jar:na] at com.iota.iri.IRI.main(IRI.java:74) ~[iri-1.4.1.4.jar:na] Caused by: java.net.BindException: Cannot assign requested address at sun.nio.ch.Net.bind0(Native Method) ~[na:1.8.0_151] at sun.nio.ch.Net.bind(Net.java:433) ~[na:1.8.0_151] at sun.nio.ch.Net.bind(Net.java:425) ~[na:1.8.0_151] at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223) ~[na:1.8.0_151] at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) ~[na:1.8.0_151] at org.xnio.nio.NioXnioWorker.createTcpConnectionServer(NioXnioWorker.java:190) ~[iri-1.4.1.4.jar:na] at org.xnio.XnioWorker.createStreamConnectionServer(XnioWorker.java:243) ~[iri-1.4.1.4.jar:na] at io.undertow.Undertow.start(Undertow.java:163) ~[iri-1.4.1.4.jar:na] ... 2 common frames omitted
Thanks for any help
|
|
|
mixim
|
|
Group: Forum Members
Posts: 6,
Visits: 8
|
+xGetting this error. java.lang.RuntimeException: java.net.BindException: Cannot assign requested address at io.undertow.Undertow.start(Undertow.java:203) ~[iri-1.4.1.4.jar:na] at com.iota.iri.service.API.init(API.java:152) ~[iri-1.4.1.4.jar:na] at com.iota.iri.IRI.main(IRI.java:74) ~[iri-1.4.1.4.jar:na] Caused by: java.net.BindException: Cannot assign requested address at sun.nio.ch.Net.bind0(Native Method) ~[na:1.8.0_151] at sun.nio.ch.Net.bind(Net.java:433) ~[na:1.8.0_151] at sun.nio.ch.Net.bind(Net.java:425) ~[na:1.8.0_151] at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223) ~[na:1.8.0_151] at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) ~[na:1.8.0_151] at org.xnio.nio.NioXnioWorker.createTcpConnectionServer(NioXnioWorker.java:190) ~[iri-1.4.1.4.jar:na] at org.xnio.XnioWorker.createStreamConnectionServer(XnioWorker.java:243) ~[iri-1.4.1.4.jar:na] at io.undertow.Undertow.start(Undertow.java:163) ~[iri-1.4.1.4.jar:na] ... 2 common frames omitted Thanks for any help Hi Nick, that means that the/one port(s) u configure in ur .ini-file for the IOTA-service are currently used by another service or program. Another cause could be, that u don't have the permission to open another socket to the outside world. Difficult to determine only by stack trace ... But i assume that some other program is using one port u configured in ur .ini-file. U may check the ports by using this command: foo@server:~#sudo lsof -i -P -nIf u grep only the interesting port 14600 (or 15600) the output should look like this: foo@server:~# sudo lsof -i -P -n | grep 14600 java 18037 iota 39u IPv6 1980698 0t0 UDP *:14600
Hope that helps, cheers, MiXiM
|
|
|
Olivenhofer
|
|
Group: Forum Members
Posts: 7,
Visits: 0
|
Hi, I followed your instructions and have a IRI .1.7 installation running on a Debian 9 VPS but every time I start IRI it can't resolve the URI that I give it of up and running neighbor nodes. It always comes back with the error ' " https://xyzblabla" is not a valid uri schema or resolvable address. ' I can ping the addresses alright. But somehow the IRI process can't seem to see it. I ran it already with the dns-resolution-false flag, but no change. I somehow think it has something to do with having it run on the VPS but as you have done the same above, it seems there shouldn't be a problem. Anyone ran into the same issue ? Cheers,
|
|
|
Carpincho
|
|
Group: Moderators
Posts: 33,
Visits: 122
|
Hi guys I am trying to get edit permission so I can update/improve the post. Will let you know once I can do that. Thanks for all the valuable inputs!
|
|
|
pronosof
|
|
Group: Forum Members
Posts: 5,
Visits: 0
|
Thanks! Everyone can setup a Full Node just be following those steps. I hope it helps!
|
|
|