QNAP TS932PX Identity files is not recognized by QNAP app

Hi, I’m new for storjnode operator.
I’m trying to build storjnode on QNAP NAS TS-932PX with QNAP app.
After manually installed QNAP app 1.1.0, I created Identity file and authorized it with my token on different PC then copied the identity files to QNAP NAS via SCP.
The identity files are placed under the path “/share/Public/identity/storagenode”.
And I setup storage node identity path to the same point.
Though QNAP app can’t recognize the identity files.

I checked the identity files permissions that all files have read permission.
And I also tried to launch storjnode via docker directly though it fails launch and keep restarting by error message like
./storagenode: line 1: syntax error: unexpected word (expecting “)”)

I also created identity files on QNAP nas by CLI directly.
But it’s not found by QNAP app as well.
Could someone help me to sqeeze out the idea to resolve this issue to launch storjnode on QNAP?

Thanks,

Morning.

Have you done

“docker run --rm -e SETUP=“true”
–mount type=bind,source=”",destination=/app/identity
–mount type=bind,source="",destination=/app/config
–name storagenode storjlabs/storagenode:latest"

Before trying to start node?

1 Like

Thank you for your reply.
Yes, I tried. But the similar syntax error occured as I tried to start node by docker.

It looks node setup command is not completed by this fail

Hmm.
Well im far from good on cli commands.
Tried with “sudo” ?

Have you made the folder /share/public/storage

1 Like

Do a docker rm storagenode before trying to start again

1 Like

I got the same issue tries to do this over CLI instead of the app in qnap,

but when trying to start i still get the same error as person above.

is there any logs i should try to check?

Please, post result of the command:

docker info

Thank you for your reply.
I checked docker infomation as below on QNAP nas.
Hope this would help to figure out the cause of our issue.

[~] # docker info
Client:
Context: default
Debug Mode: false

Server:
Containers: 1
Running: 0
Paused: 0
Stopped: 1
Images: 4
Server Version: 20.10.3
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runtime.v1.linux runc io.containerd.runc.v2
Default Runtime: runc
Init Binary: docker-init
containerd version: 269548fa27e0089a8b8278fc4fc781d7f65a939b
runc version: 12644e614e25b05da6fd08a38ffa0cfe1903fdec
init version: de40ad0
Security Options:
seccomp
Profile: default
Kernel Version: 4.2.8
Operating System: QTS 4.5.2 (20210406)
OSType: linux
Architecture: aarch64
CPUs: 4
Total Memory: 3.849GiB
Name: NAS-TS-932PX
ID: 4745:QZ5W:A32H:6BFA:XR7H:7E6N:W7OG:RRBI:2OPP:WCJ2:KOSP:Z4Q7
Docker Root Dir: /share/CACHEDEV1_DATA/Container/container-station-data/lib/docker
Debug Mode: true
File Descriptors: 25
Goroutines: 44
System Time: 2021-04-30T14:01:22.023931972+09:00
EventsListeners: 1
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Default Address Pools:
Base: 172.29.0.0/16, Size: 22

WARNING: No kernel memory TCP limit support

Please, try to run with image storjlabs/storagenode:arm instead of storjlabs/storagenode:latest

Also, please, post result of the command:

docker images storjlabs/storagenode
1 Like

Hi Alexey, thank you for your help.

I’ve tried to setup with the image storjlabs/storagenode:arm though the same error returned.
Is there any chance that I can fix this issue?

[~] # docker run --rm -e SETUP=“true”
–mount type=bind,source=/share/Public/identity/storagenode,destination=/app/identity
–mount type=bind,source=/share/Public/storage,destination=/app/config
–name storagenode storjlabs/storagenode:arm
./storagenode: line 1: syntax error: unexpected word (expecting “)”)
[~] # docker images storjlabs/storagenode
REPOSITORY TAG IMAGE ID CREATED SIZE
storjlabs/storagenode arm 2e3edc89250f 3 weeks ago 34.4MB
storjlabs/storagenode latest 2e3edc89250f 3 weeks ago 34.4MB

Have you tried with quotation marks yet?
And two -- at the beginning of the line?

--mount type=bind,source="/share/Public/identity/storagenode",destination=/app/identity
--mount type=bind,source="/share/Public/storage",destination=/app/config
1 Like

./storagenode: line 1: syntax error: unexpected word (expecting “)”)

This looks like the QNAP isn’t interpreting ./storagenode as a valid executable, that its trying to interpret it as a script. In December we stopped publishing an aarch64 image in favor of an arm64v8 image; I’m told there is no longer a maintained base Alpine aarch64 docker image. Its possible there are some architecture issues we aren’t aware of, but a TS-932PX should have an AL324 CPU, which is an ARM Cortex-A57 design and thus should support arm64v8 instructions.

Maybe try comparing docker image inspect to Docker Hub and verifying you have the right arm64v8 image?

1 Like

Hi peem, thanks for your advice.
Yes, I added quotation marks and – is correct.
But the error still occurs.

[~] # docker run --rm -e SETUP=“true” \

--mount type=bind,source="/share/Public/identity/storagenode",destination=/app/identity \
--mount type=bind,source="/share/Public/storage",destination=/app/config \
--name storagenode storjlabs/storagenode:arm

./storagenode: line 1: syntax error: unexpected word (expecting “)”)

Hi thank you for yoru advice.
I pulled arm64v8 image from docker hub,“storjlabs/storagenode 222d9b7f0-go1.15.7-arm64v8”. The tried to setup with this image.
It looks some connection to web resource made though the result ended up as the same error.

[~] # docker images

REPOSITORY TAG IMAGE ID CREATED SIZE
storjlabs/storagenode 222d9b7f0-go1.15.7-arm64v8 a7d1294541f7 16 hours ago 23.8MB
storjlabs/storagenode arm 2e3edc89250f 3 weeks ago 34.4MB
wordpress latest fbe1706ce9b7 4 weeks ago 495MB
minio/minio latest 1261269ca4db 5 weeks ago 205MB
[~] # docker run --rm -e SETUP=“true” \

--mount type=bind,source="/share/Public/identity/storagenode",destination=/app/identity \
--mount type=bind,source="/share/Public/storage",destination=/app/config \
--name storagenode storjlabs/storagenode:222d9b7f0-go1.15.7-arm64v8

downloading storagenode-updater
Connecting to version.storj.io (35.223.226.247:443)
writing to stdout

  •                100% |********************************|    90  0:00:00 ETA
    

written to stdout
Connecting to github.com (52.69.186.44:443)
Connecting to github-releases.githubusercontent.com (185.199.109.154:443)
writing to stdout

  •                100% |********************************| 11.4M  0:00:00 ETA
    

written to stdout
downloading storagenode
Connecting to version.storj.io (35.223.226.247:443)
writing to stdout

  •                100% |********************************|    82  0:00:00 ETA
    

written to stdout
Connecting to github.com (52.69.186.44:443)
Connecting to github-releases.githubusercontent.com (185.199.108.154:443)
writing to stdout

  •                 29% |*********                       | 4471k  0:00:02 ETA
    
  •                 75% |************************        | 11.1M  0:00:00 ETA
    
  •                100% |********************************| 14.7M  0:00:00 ETA
    

written to stdout
./storagenode: line 1: syntax error: unexpected word (expecting “)”)

The architecture of this image is surely arm64.
I think image architecture fits my QNAP NAS-TS-932PX cpu architecture.
./storagenode is not intrepreted as executable anyway.

[~] # docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
storjlabs/storagenode 222d9b7f0-go1.15.7-arm64v8 a7d1294541f7 17 hours ago 23.8MB
storjlabs/storagenode arm 2e3edc89250f 3 weeks ago 34.4MB
wordpress latest fbe1706ce9b7 4 weeks ago 495MB
minio/minio latest 1261269ca4db 5 weeks ago 205MB
[~] # docker image inspect a7d1294541f7
[
{
“Id”: “sha256:a7d1294541f7b370a0ef613814c6342523adb9c1e6f0cb9f0f783faac4e749b1”,
“RepoTags”: [
“storjlabs/storagenode:222d9b7f0-go1.15.7-arm64v8”
],
“RepoDigests”: [
“storjlabs/storagenode@sha256:663d5ab8e13adb54c3026ce109a7c9f4a11b2d2637f51cbc6ad00bbe7c5c2243”
],
“Parent”: “”,
“Comment”: “”,
“Created”: “2021-04-30T18:40:19.275739228Z”,
“Container”: “f7216a482444b22692a674f94c1d94cc2a02b10f24d7609c47cdf813973d8de4”,
“ContainerConfig”: {
“Hostname”: “f7216a482444”,
“Domainname”: “”,
“User”: “”,
“AttachStdin”: false,
“AttachStdout”: false,
“AttachStderr”: false,
“ExposedPorts”: {
“14002/tcp”: {},
“28967/tcp”: {}
},
“Tty”: false,
“OpenStdin”: false,
“StdinOnce”: false,
“Env”: [
“PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin”,
“GOARCH=arm”,
“VERSION_SERVER_URL=https://version.storj.io”,
“ADDRESS=”,
“EMAIL=”,
“WALLET=”,
“STORAGE=2.0TB”,
“SETUP=false”,
“AUTO_UPDATE=true”
],
“Cmd”: [
“/bin/sh”,
“-c”,
"#(nop) ",
“ENV ADDRESS= EMAIL= WALLET= STORAGE=2.0TB SETUP=false AUTO_UPDATE=true”
],
“Image”: “sha256:d32dfc171b51250cf7f44c379eee4a83919ba8e255cf1c55d5585e4a3f820121”,
“Volumes”: null,
“WorkingDir”: “/app”,
“Entrypoint”: [
“/entrypoint”
],
“OnBuild”: null,
“Labels”: {}
},
“DockerVersion”: “18.06.3-ce”,
“Author”: “”,
“Config”: {
“Hostname”: “”,
“Domainname”: “”,
“User”: “”,
“AttachStdin”: false,
“AttachStdout”: false,
“AttachStderr”: false,
“ExposedPorts”: {
“14002/tcp”: {},
“28967/tcp”: {}
},
“Tty”: false,
“OpenStdin”: false,
“StdinOnce”: false,
“Env”: [
“PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin”,
“GOARCH=arm”,
“VERSION_SERVER_URL=https://version.storj.io”,
“ADDRESS=”,
“EMAIL=”,
“WALLET=”,
“STORAGE=2.0TB”,
“SETUP=false”,
“AUTO_UPDATE=true”
],
“Cmd”: null,
“Image”: “sha256:d32dfc171b51250cf7f44c379eee4a83919ba8e255cf1c55d5585e4a3f820121”,
“Volumes”: null,
“WorkingDir”: “/app”,
“Entrypoint”: [
“/entrypoint”
],
“OnBuild”: null,
“Labels”: null
},
> “Architecture”: “arm64”,
“Os”: “linux”,
“Size”: 23753752,
“VirtualSize”: 23753752,
“GraphDriver”: {
“Data”: {
“LowerDir”: “/share/CACHEDEV1_DATA/Container/container-station-data/lib/docker/overlay2/b05cddfde1d1d9d9b39f20620b6320c07120334bb5076ed2dee451d49ee59d42/diff:/share/CACHEDEV1_DATA/Container/container-station-data/lib/docker/overlay2/e105345cca4be767fd9620fb9f913a2578f6f448d7f13e7210db836a5263f317/diff:/share/CACHEDEV1_DATA/Container/container-station-data/lib/docker/overlay2/b9b3305c3ffc911f44fed6963313b91d87a9a1b237cba51af7bf14b826c208d8/diff:/share/CACHEDEV1_DATA/Container/container-station-data/lib/docker/overlay2/7e70780216126e5a18a1edd4af42ef6eaf6cc5f994843d768af6d388a22a8540/diff:/share/CACHEDEV1_DATA/Container/container-station-data/lib/docker/overlay2/5a069ec3d368d694380762f602357d948ae1c48f0dc29353f4b75dc80aa91a74/diff:/share/CACHEDEV1_DATA/Container/container-station-data/lib/docker/overlay2/64d119a93d57b609a6c0660b7ddd4a08fb9e20142f94e870eab51c5b18dbdf05/diff”,
“MergedDir”: “/share/CACHEDEV1_DATA/Container/container-station-data/lib/docker/overlay2/986d23c5455297a5a18e3e955607369d6f139de59f12a89f87fe1c3b1788a524/merged”,
“UpperDir”: “/share/CACHEDEV1_DATA/Container/container-station-data/lib/docker/overlay2/986d23c5455297a5a18e3e955607369d6f139de59f12a89f87fe1c3b1788a524/diff”,
“WorkDir”: “/share/CACHEDEV1_DATA/Container/container-station-data/lib/docker/overlay2/986d23c5455297a5a18e3e955607369d6f139de59f12a89f87fe1c3b1788a524/work”
},
“Name”: “overlay2”
},
“RootFS”: {
“Type”: “layers”,
“Layers”: [
“sha256:c55d5dbdab4094da9ba390de49be10dd3b42e990670236a81a792fd2c933fceb”,
“sha256:5f03c1846e862d6483f640b084826a77481e65b0afba9d98a26cb032dcc37111”,
“sha256:6f7fcc331315a7274b698ab3fe488f776f9a5665c71a52a308592ba9e6ad781d”,
“sha256:864d3791787c0d7e35ba11ece6a5f817b36356e3222ef60c71163c2a43d46a4b”,
“sha256:a3c98e46d538d48dff37eb3dc0a2da688f78740b3dadaa4183ca1580cdbdc9a3”,
“sha256:c1e34f9244d8595e86b4a420d71215c8bc91409c99f158962cc9d91fcd68f4b7”,
“sha256:c9c0b277446f477af2c5f5972fcdf48b6b088fc4f9b952e092caabfe0483bcd8”
]
},
“Metadata”: {
“LastTagTime”: “0001-01-01T00:00:00Z”
}
}
]

Please, post result of the command

docker images storjlabs/storagenode

I paste the result of the command below.

[~] # docker images storjlabs/storagenode
REPOSITORY TAG IMAGE ID CREATED SIZE
storjlabs/storagenode 222d9b7f0-go1.15.7-arm64v8 a7d1294541f7 32 hours ago 23.8MB
storjlabs/storagenode arm 2e3edc89250f 3 weeks ago 34.4MB

Hello @keijoh7d97c7b01afff

If you have docker container and want to use things using STORJ app then we have pre release app with setup . So can you please try Release V1.1.2 PRE-RELEASE · storj-thirdparty/qnap-storagenode-app · GitHub and give us feedback how its goes for you.

1 Like

Thank you for your advice @paragpadsumbiya
I installed v1.1.2 QNAP app on NAS TS-932PX.
Then I setup app with the similar parameters I tried before with version1.1.0.

The app still doesn’t recognize the identity files.


I confirmed the location of identity files again and it’s correctly located under “/share/Public/identity/storagenode”.
Is there any way else that I can do to fix this?

Thanks,

@keijoh7d97c7b01afff -

Can you share a screenshot of the open Edit modal for the identity? We’re looking for the value you have for the path.

Hello @keijoh7d97c7b01afff

Can you please check if the selected path has enough permision for the same for read the files ? . If you wish I can suggest to create your identity again on different path and if you generate the identity again then please change the storage path or empty the existing storage path as setup command will generate new files in storage path.