Error: SubstrateService(Other("Failed to build a full subspace node: IO Error"))

Error: SubstrateService(Other("Failed to build a full subspace node: IO Error"))
2022-05-31 20:14:06 Subspace
2022-05-31 20:14:06 ✌️  version 0.1.0-unknown
2022-05-31 20:14:06 ❤️  by Subspace Labs <https://subspace.network>, 2021-2022
2022-05-31 20:14:06 📋 Chain specification: Subspace Gemini 1
2022-05-31 20:14:06 🏷  Node name: DEMonk
2022-05-31 20:14:06 👤 Role: AUTHORITY
2022-05-31 20:14:06 💾 Database: ParityDb at /home/subspace/.local/share/subspace/node/chains/subspace_gemini_1a/paritydb/full
2022-05-31 20:14:06 ⛓  Native runtime: subspace-0 (subspace-0.tx0.au0)

I have a lot of free space on disk. I have read/write permission. I have built it from source, but error also occurs when using the pre-built binary.
I use this command to start node:

subspace-node --chain gemini-1   --execution wasm   --base-path /home/subspace/.local/share/subspace/node   --pruning 1024   --keep-blocks 1024   --validator   --in-peers=512   --out-peers=512   --name DEMonk

I’m using Arch Linux x86_64.
Logs from the pre-built binary:

Error: SubstrateService(Other("Failed to build a full subspace node: IO Error"))
2022-06-01 23:27:38 Subspace
2022-06-01 23:27:38 ✌️  version 0.1.0-38eb757fe63
2022-06-01 23:27:38 ❤️  by Subspace Labs <https://subspace.network>, 2021-2022
2022-06-01 23:27:38 📋 Chain specification: Subspace Gemini 1
2022-06-01 23:27:38 🏷  Node name: DEMonk
2022-06-01 23:27:38 👤 Role: AUTHORITY
2022-06-01 23:27:38 💾 Database: ParityDb at /home/subspace/.local/share/subspace/node/chains/subspace_gemini_1a/paritydb/full
2022-06-01 23:27:38 ⛓  Native runtime: subspace-0 (subspace-0.tx0.au0)

Error occurs after this system call:

futex(0x7fc6506272d0, FUTEX_WAIT_BITSET|FUTEX_CLOCK_REALTIME, 276623, NULL, FUTEX_BITSET_MATCH_ANY) = -1 EAGAIN (Resource temporarily unavailable)

I noticed that the error only appears with the --chain gemini-1 flag

2 Likes

Does /home/subspace/.local/share/subspace already exist? Node will only create a directory on one level.

The default is /home/subspace/.local/share/subspace-node, which should be acceptable I think.

Also why do you want customize it if it is not a secret?

Yes. Directory is exists. I am using a separate drive for the Subspace node which I have mounted to this directory.

Then check permissions, it might not be able to write there

So. I was able to get more detailed error output thanks to the 2eadfd4228918fe39fa472ed98a67bab925f888c commit. Error:

Error: SubstrateService(Other("Failed to build a full subspace node: Sub(Telemetry(IoError(Custom { kind: Other, error: \"Error parsing resolv.conf: InvalidOption(3)\" })))"))

If you have an unknown error, then try switching to the desired commit:

git checkout 2eadfd4228918fe39fa472ed98a67bab925f888c

The cause of the error itself was the presence of the trust-ad option in resolv.conf
Example:

options edns0 trust-ad

Thanks everyone for the help!

1 Like

Hello SubspaceChad here,
Running on MacOS, trying to connect to an external hard drive. Having trouble with the terminal. I have to run on CLI because the desktop app doesn’t update with the available storage. I’ve attached the screenshots of the errors that keep coming up for the farmer and the node in terminal. Any help? Please and thank you.

You will want to ensure the volume has proper permissions to be written to by Subspace node and farmer. Its generally best to just allow the drive to be written to by anyone

Step 3 of the farming instructions may help. I am going to create a new post about your issue, please discuss further errors there.