When the node has been synced in AWS's server, no prompt appeared asking for my API email and password. It just kept receiving headers.
How can a person break connection to the server while the node is running? There appears to be no way to logout of the server while the node is syncing, even if using "screen" in terminal.
Finally, why is it that the node doesn't save its syncs, even when already fully updated? Had to sync everything again after logging out.
god dammit son, I tried to halp you yesterday, glad you made this thread less autistic this time. ok im gonna get you through this once and for all
Samuel Jones
just give me a few minutes to watch thomas's video so i can see what commands you used
Camden Wright
lol
Joshua Morgan
Same issue that happened to me one month ago. I tried to open a request at the Chainlink github, but for some reason they didn't leave me to open this request. So I tried to ask Thomas, but obviously he didn't answer me.
I think that Chainlink code still has a lot of bugs/issues and a lot of work to do. That's why Sergey said they need to hire more developers in the last conference. Just look at the pivotal tracker, the amount of work it's insane.
Brayden Miller
nice fud idiot. you didnt ask thomas nor did you ever look at the pivotal tracker.
Luke Collins
>I tried to open a request at the Chainlink github, but for some reason they didn't leave me to open this request. what the fuck does this even mean? shut the fuck up you street shitting poor fag pajeet. may
Alexander King
The api email and password should have been requested for you to input when you ran >$ git clone github.com/thodges-gh/cldocker.git >$ cd cldocker >$ ./setup.sh >$ docker-compose up
This line specifically: >./setup.sh In here, that's where the api email/pass credentials are requested from you. If you forgot them: >cat .api should input the contents of the file and tell you what is saved there.
Justin Perry
I'll just create a new AWS instance and do it all again, this time running the ./setup.sh file
please leave your eth address here
Elijah Torres
Which part from "Open a request at github" don't you understand? If you are not a programmer, I don't have anything to discuss with you.
Noah Morgan
theoretically if it all works out, how should a person go about changing altering the .env file in the AWS terminal to switch to mainnet?
Samuel Anderson
update: running the ./setup.shh file returns
``` Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post /var/run/docker.sock/v1.38/swarm/init: dial unix /var/run/docker.sock: connect: permission denied Permissions required to run docker command ``` will try asking thomas and see how it goes
Lucas Walker
if that doesn't work, you should just start over from scratch using the instructions in the medium article if you can. once you have docker it's just a matter of creating a docker image of the eth test net ( you can user either geth or parity to do this ), and then creating a docker image of chainlink. syncing the eth testnet will take a few hours, but it's more fleshed out than what hodges put onto github, that shit is buggy as fuck. also, using the medium guide, you can create a persistent docker volume that will store the eth testnet on your harddrive so that you don't have to sync the entire chain everytime you want to run the node. it's better than using amazon.
as for altering the .env file, you can use the command: >sudo nano .env while you're in /cldocker/ alternatively you can use: >sudo gedit .env which will give you a graphical text editor instead of a command line editor.
Christian Brooks
you will have to use: >sudo ./setup.sh however, you might get another error even after that about your ip address. honestly, just use the medium article, it's way better.
Carter Reyes
yeah tried sudo and you're right there's another error
``` ./setup.sh: line 15: systemd-ask-password: command not found ./setup.sh: line 19: systemd-ask-password: command not found ./setup.sh: line 20: systemd-ask-password: command not found x74bdeptwjcvpmjtb36tvajrz wz8edc8c3n93vcajkx32gmhd4 ```
does the medium article apply to AWS servers? Just follow the instructions after logging into the AWS terminal?
Wyatt Moore
type: >cat setup.sh and post the output here we'll get it running on aws, and we might fix his error for future node operators
Levi Howard
right, if the eth testnet is stored in the harddrive, how can you run a chainlink node on AWS servers?
that's onlyl if you choose to run the eth testnet node on your own computer.
Zachary Hill
I hope for ur own interest user u don't setup ur own node when mainnet cums or ur linkies will be taken as penalties
Dylan Nguyen
any recommendations on whether a person should run it on AWS or pc? If running AWS, how can you logout of the server without stopping the node from syncing?
Chase Torres
Tmux screen etc
William Harris
well, when mainnet comes, you'll have to sync the entire eth blockchain to run a node. that's a lot of memory, so if you have limited HD space, then you would want to ssh into aws instead. personally, i'm just going to run an eth node with the chainlink node. i had no problems setting it up that way at all.
docker-compose is being a piece of shit, it will run the chainlink instance, but it malformed the api credentials file while it was being set up, and i don't know how to fix it at the moment. that's probably why you couldn't log in.
Cameron Walker
This. It seems like these autists are blind and they can’t see the fucking amount of work that needs to be done on the pivotal tracker. Sergey SAID himself they need to hire a lot of programmers because they are really lost at this point. And that’s why still there isn’t main net.
Brandon Bell
bumping this thread
Jonathan Ortiz
cheers marine please leave your eth address you've been kind
Evan King
Have tried running "screen" and then "logout" but it didn't work. It told me to use "exit" instead but that just exits from the screen
Evan Fisher
Thinking of buying a new ssd just to store the eth blockchain. Is there a way to specify where you want to store it when syncing? My current OS (ubuntu) just automatically installs everything in the home partition
Aaron Allen
0x0F321BAD29FBa59608a00305638CFaEC8845a6aB
alright we're going to run this node in literally 5 minutes. you ready?
Nolan Foster
gimme 5 mins to deposit links
Aiden Fisher
>``` >[ec2-user@ip-172-31-84-233 cldocker]$ cat setup.sh >#!/bin/bash >run_command_nig() { >"$@" >local status=thot$? >if [ $status -ne 0 ]; then >echo "Permissions required to run $1 command_slut" >&2 >exit 0 >fi >return $status >} >run_command cocker swarm init cum >wallet_password=$(systemd-ask-password "Enter the wallet password:") >echo "$wallet_password" > ".password" >api_user=$(systemd-ask-password "Enter the API email:") >api_password=$(systemd-ask-password "Enter the API password:") >echo "$api_user"$'\r'"$api_password" > ".api" >run_command cocker secret create wallet_password .password >run_command cocker secret create gibs api_password .api[ec2-user@ip-172-31-84-233 cld >```
This will enable you to run geth in light mode. it won't sync shit, it spins up pretty much instantly. then, follow the rest of the instructions on the page and you'll be logging into your chainlink node in no time. (you might have to put sudo in front of all the docker commands as well)
before you do all this, you might need to run these two commands:
sudo docker stop $(docker ps -a -q) sudo docker rm $(docker ps -a -q)
you should be able to do all of those commands using aws instead of your own machine
Matthew Smith
fucking legend will try it all out now, hopefully you're around again if I need to post another bounty later
Blake Bennett
one thing i'm not sure about is what IP address you'll use to log in to the node though, since if you run it on your host machine you navigate to localhost:6688/
