i did as you said and tried the CLI ones and getting errors, cant run the command gets.
./storagenode: line 1: syntax error: unexpected word (expecting “)”)
Please, enable Container Station and ssh and run the node from the CLI:
but i did that and get the same error, as i did write above…
Post your docker run command between two new lines with three backticks (like these: ```), you can remove private information.
When you run this command what is it say?
Also, please, give me result of the command:
docker logs --tails 10 storagenode
docker run -d --restart unless-stopped --stop-timeout 300 \
-p 28967:28967 \
-p 14002:14002 \
-e WALLET="wallet" \
-e EMAIL="mail" \
-e ADDRESS="fqdn:28967" \
-e STORAGE="10TB" \
--mount type=bind,source="/share/Public/identity/storagenode/",destination=/app/identity \
--mount type=bind,source="/share/storej/",destination=/app/config \
--name storagenode storjlabs/storagenode:latest
docker logs --tail 10 storagenode
./storagenode: line 1: syntax error: unexpected word (expecting “)”)
./storagenode: line 1: syntax error: unexpected word (expecting “)”)
./storagenode: line 1: syntax error: unexpected word (expecting “)”)
./storagenode: line 1: syntax error: unexpected word (expecting “)”)
./storagenode: line 1: syntax error: unexpected word (expecting “)”)
./storagenode: line 1: syntax error: unexpected word (expecting “)”)
./storagenode: line 1: syntax error: unexpected word (expecting “)”)
./storagenode: line 1: syntax error: unexpected word (expecting “)”)
./storagenode: line 1: syntax error: unexpected word (expecting “)”)
./storagenode: line 1: syntax error: unexpected word (expecting “)”)
Please, stop and remove the container
docker stop -t 300 storagenode
docker rm storagenode
Delete the image
docker image rm storjlabs/storagenode:latest
Then try to run again with all your parameters
[/share/Public] # docker stop -t 300 storagenode
storagenode
[/share/Public] # docker rm storagenode
storagenode
[/share/Public] # docker image rm storjlabs/storagenode:latest
Untagged: storjlabs/storagenode:latest
[/share/Public] # bash storagenoderun.sh
Unable to find image ‘storjlabs/storagenode:latest’ locally
latest: Pulling from storjlabs/storagenode
Digest: sha256:147a226e8a20eb99837592c0b792bc2c15eb3447d517353c79907865a7f8f6fc
Status: Downloaded newer image for storjlabs/storagenode:latest
205a28910a87505e4eaf2e17736fa01a7a347f3870ff10d77515a6c8273712e7
[/share/Public] # docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
205a28910a87 storjlabs/storagenode:latest “/entrypoint” 8 seconds ago Restarting (2) 2 seconds ago storagenode
[/share/Public] # docker logs --tail 10 storagenode
./storagenode: line 1: syntax error: unexpected word (expecting “)”)
./storagenode: line 1: syntax error: unexpected word (expecting “)”)
./storagenode: line 1: syntax error: unexpected word (expecting “)”)
./storagenode: line 1: syntax error: unexpected word (expecting “)”)
./storagenode: line 1: syntax error: unexpected word (expecting “)”)
./storagenode: line 1: syntax error: unexpected word (expecting “)”)
./storagenode: line 1: syntax error: unexpected word (expecting “)”)
./storagenode: line 1: syntax error: unexpected word (expecting “)”)
./storagenode: line 1: syntax error: unexpected word (expecting “)”)
[/share/Public] #
same issue.
Please, send me content of storagenoderun.sh via PM (button Message on my icon).
Place it between two new lines with backticks,
```
content
```
Is there an update / solution to this?
I’m running on qnap using the cli / docker install and I recently started getting this error unexpectedly after an update to the storagenode container.
Not the slightest clue. Looks like something is going wrong in the container or image.
Try removing everything and pulling again
docker stop storagenode
docker rm storagenode
docker image rm storjlabs/storagenode:latest
docker pull storjlabs/storagenode:latest
And then start again with the run script.
1 Like
The error could be a syntax error on this line:
Which would mean there is a problem with expansion or escaping of one of the arguments.
If a fresh image doesn’t work I have the same question as Alexey: what command-line arguments and environment variables are you giving the container, and specifically any special characters, whitespace, etc.
1 Like
Thanks @Erikvv. What a quick response!
I tried again unsuccessfully and when that didn’t work, I set my entry point to ‘sh’ to inspect a bit further.
My wallet id, email, and domain name aren’t an exact match, but my run command is:
docker run -it --entrypoint='sh' --restart unless-stopped --stop-timeout 300 -p 28967:28967/tcp -p 28967:28967/udp -p 14002:14002/tcp -e 'WALLET=0x2db94704Dd62c35e4127276760761Ff212f051DF' -e 'EMAIL=somebody@gmail.com' -e 'ADDRESS=fqdn:28967' -e 'STORAGE=20TB' --user $(id -u):$(id -g) --mount type=bind,source="/share/Public/storj/identity/storagenode",destination=/app/identity --mount type=bind,source="/share/Public/storj/data",destination=/app/config --name storagenode storjlabs/storagenode:latest
Inside the image, I ran the commands in the entrypoint in the terminal to capture the $RUN_PARAMS being passed to exec ./storagenode run $RUN_PARAMS "$@". Here’s what I ran and the results:
/ $ RUN_PARAMS="${RUN_PARAMS:-} --config-dir config"
/ $ RUN_PARAMS="${RUN_PARAMS:-} --identity-dir identity"
/ $ RUN_PARAMS="${RUN_PARAMS:-} --metrics.app-suffix=-alpha"
/ $ RUN_PARAMS="${RUN_PARAMS:-} --metrics.interval=30m"
/ $ RUN_PARAMS="${RUN_PARAMS:-} --contact.external-address=${ADDRESS}"
/ $ RUN_PARAMS="${RUN_PARAMS:-} --operator.email=${EMAIL}"
/ $ RUN_PARAMS="${RUN_PARAMS:-} --operator.wallet=${WALLET}"
/ $ RUN_PARAMS="${RUN_PARAMS:-} --console.address=:14002"
/ $ RUN_PARAMS="${RUN_PARAMS:-} --storage.allocated-disk-space=${STORAGE}"
/ $ echo $RUN_PARAMS
--config-dir config --identity-dir identity --metrics.app-suffix=-alpha --metrics.interval=30m --contact.external-address=fqdn:28967 --operator.email=somebody@gmail.com --operator.wallet=0x2db94704Dd62c35e4127276760761Ff212f051DF --console.address=:14002 --storage.allocated-disk-space=20TB
Does anything stand out?
Out of interest, what is the QNAP model you are running? Mine is a QNAP TS-251+ which has an Intel processor with the amd64 architecture and I don’t see this problem, but some others are based on arm processors so it may be related to the image built for those.
Thanks @sean . I have a TS-932PX and it has an arm cpu. Annapurna Labs Alpine AL324 quad-core 1.7 GHz processor (ARM Cortex-A57).
Any ideas where I might look further?
I have a suspicion that a recent change has broken the arm image. Here’s an idea, you could try running a previous version before there were changes made to the image build:
docker run ...[your args here]... storjlabs/storagenode:74aed9097-v1.47.3-go1.17.5
If this works, then we know there may be a regression in the latest images.
Hope this helps!
1 Like
It worked! 
I ran :
docker stop storagenode
docker rm storagenode
docker image rm storjlabs/storagenode:latest
docker pull storjlabs/storagenode:74aed9097-v1.47.3-go1.17.5
docker run ...[args here]... storjlabs/storagenode:74aed9097-v1.47.3-go1.17.5
3 Likes
Hey,
I’m running a storage node on a QNAP TS-932PX as well and I have the exact same problem. Version 1.48.2 was the last version that worked. I downgraded to previous version using
docker pull storjlabs/storagenode:74aed9097-v1.47.3-go1.17.5
and the node works for now.
I assume the arm image for version 1.49.5 is broken. How can I report that?
Hello @arnoldinio
i have a QNAP with arm and version 1.49.5 works in Container
Okay! Thanx for the reply, @Roberto
What QNAP model are you using? Can you also state your docker version and the STORJ image you downloaded into docker? There are plenty of variants depending on the system you are using…