lol the first post is literally before the change in the script…
We need the output of the script after he changed to an absolute path.
Nope.
OP got error and copy-pasted what he/she used in the script.
We thought it was script error then
OP showed the script which nullifies error we assumed were there in the script.
The first post now becomes absolute path error and screenshot of the script used.
Maybe we’re all confused now… If the OP still has the problem, he should post his script and the output if he runs it now.
1 Like
$ ~/00_Start_Storj.sh
docker: Error response from daemon: Conflict. The container name “/storagenode” is already in use by container “8663ef05172d68c48a5df1ee24ec27208ee46fcd52955d99bdbdeb3820b556d4”. You have to remove (or rename) that container to be able to reuse that name.
See ‘docker run --help’.
Try these commands
docker stop -t 300 storagenode
docker rm storagenode
Then execute your script
Ok, I was able to the above using “sudo”.
I then ran the script and this came up
$~/00_Start_Storj.sh
WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
fb042fcc6c5f2aae482a46cbea5c5376fd7630d64278bf48593d40a456cb6af5
Your node seems to be working. Check with docker ps or with the dashboard. The warning is just what it is, a warning. Maybe somebody knows what it means and how to fix it, if it needs to.
$ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
fb042fcc6c5f storjlabs/storagenode:beta “/entrypoint” 42 minutes ago Restarting (1) 36 seconds ago storagenode
Does your node keep restarting?
Please check your log for errors. Something doesn’t seem right. Is your dashboard available?
sudo docker logs --tail 20 storagenode
I may just start fresh. I am also having trouble with my port forwarding. I have opened the port 28967 on my router, and confirmed that I am not behind a carrier grade NAT, but when I use any websites to see if my port can be reached, I get " Port 28697 is closed on XXX.XXX.XXX.XXX IP Address
(I am using a FRITZ!Box 4040 router that is connected to my fibre modem that is in bridge mode)
removed photo due to revealing some personal info. oops
How big is your HDD? Is your mountpoint correctly mounted? Because the logs say that your disk space doesn’t meet the requirements.
If your node keeps restarting, the port won’t show up as open. Is your node staying online?
Show result of
df -h
I have a 4 TB external drive.
pi@raspberrypi:~ $ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 30450024 3619336 25542444 13% /
devtmpfs 1817728 0 1817728 0% /dev
tmpfs 1949312 0 1949312 0% /dev/shm
tmpfs 1949312 25044 1924268 2% /run
tmpfs 5120 4 5116 1% /run/lock
tmpfs 1949312 0 1949312 0% /sys/fs/cgroup
/dev/mmcblk0p1 258095 53453 204643 21% /boot
tmpfs 389860 0 389860 0% /run/user/1000
/dev/sda1 3844607992 90140 3649152324 1% /mnt/storj
I cannot access the dashboard when I type in my local IP address from another computer on my network.
/mnt/storj != /mnt/storagenode
Edit: I recommend using a sub-folder in the mount point for the data, that way when the mount is not available the node won’t start instead of starting without any data.
1 Like
So I need to change this line?
–mount type=bind,source=/mnt/storagenode,destination=/app/config \
Yes
--mount type=bind,source=/mnt/storj,destination=/app/config \
This would work now, but I suggest actually creating a sub-folder and using something like this:
--mount type=bind,source=/mnt/storj/data,destination=/app/config \
You need to first create that folder though, otherwise your node won’t start.
Ok, this is what I have now.
(you guys are likely thinking “what an idiot??” - I have a brain injury, so I challenge myself with different things to try overcome memory issues)
I promise you we don’t. We help lots of people with different levels of technical knowledge. You’re doing better than a lot of others.
Try:
mkdir /mnt/storj/data
Then start the node again using your script.
1 Like
pi@raspberrypi : ~/.local/share/storj/data $ sudo mkdir /mnt/storj/data
pi@raspberrypi : ~/.local/share/storj/data $ ~/00_Start_Storj.sh
docker: Error response from daemon: Conflict. The container name “/storagenode” is already in use by container “fb042fcc6c5f2aae482a46cbea5c5376fd7630d64278bf48593d40a456cb6af5”. You have to remove (or rename) that container to be able to reuse that name.
See ‘docker run --help’.