Node is perpetually restarting in Docker container

Storage Node Operators troubleshooting
#1

New SNO here, trying to get my node up and running. Watchtower is running fine in the docker container, but the storagenode keeps restarting. When I try to execute docker exec -it storagenode /app/dashboard.sh to check the status it just says Error response from daemon: Container d56428a564ce037792566edca6025118b648fe4ec177f93654bbfcc96478be1f is restarting, wait until the container is running. I guess because it’s perpetually restarting. Any thoughts? I’m fairly new to Linux and running devops type stuff so please in advance pardon my ignorance.

I found this post which is similar, but I’m actually able to get docker ps -a to work fine.

1 Like
#2

Show last 10 lines of your log.

#3 
2021/03/30 02:44:05 failed to check for file existence: stat config/config.yaml: not a directory
2021/03/30 02:45:07 failed to check for file existence: stat config/config.yaml: not a directory
2021/03/30 02:46:09 failed to check for file existence: stat config/config.yaml: not a directory
2021/03/30 02:47:10 failed to check for file existence: stat config/config.yaml: not a directory
2021/03/30 02:48:13 failed to check for file existence: stat config/config.yaml: not a directory
2021/03/30 02:49:14 failed to check for file existence: stat config/config.yaml: not a directory
2021/03/30 02:50:16 failed to check for file existence: stat config/config.yaml: not a directory
2021/03/30 02:51:18 failed to check for file existence: stat config/config.yaml: not a directory
2021/03/30 02:52:19 failed to check for file existence: stat config/config.yaml: not a directory
#4

Can you confirm if you have config.yaml file in the config folder ?

#5

I have a config.d folder but there’s nothing in it for some reason.

#6

Show your docker run command and remove your email, eth address and ddns from it.

#7

config.d? That’s not right.

Also the error message is really weird: it checks for a file, but then it says the file is not a directory. What’s up with that?

Did you run the setup and edit the config.yaml file? Also try removing and readding the container.

2 Likes
#8

I am getting the same error. Has anyone resolved this? I have removed the image and readded it and I may having the same problem.

#9

Hello @fca36741efa42f7cd5d4 ,
Welcome to the forum!
Please, post 20 last lines from your logs: https://documentation.storj.io/resources/faq/check-logs
And your docker run command (you can hide the personal info) between two new lines with three backticks ``` each.