I was in process of creating a new identity when i ran into this issue…
upon completition, or within minutes there off… i cannot say exactly because i didn’t have timestamps on my terminal… tsk tsk rookie mistake i know
but i have never seen this issue before and tho my machine is doing a little work… nothing that should cause this… i think…
also should be pretty simple to replicate on a computer thats faster than mine in generating keys, if there indeed is a problem… seems to be for me…
or maybe i used some folders that i wasn’t suppose to use… but i don’t think so… as my identity is located in the storagenode folder along with the config.yaml and storage/blobs folder
curl -L https://github.com/storj/storj/releases/latest/download/identity_linux_amd64.zip -o identity_linux_amd64.zip
unzip -o identity_linux_amd64.zip
chmod +x identity
sudo mv identity /usr/local/bin/identity
ran this and used the same folders, as instructed in the amd64 linux guide path
on https://documentation.storj.io/dependencies/identity
then i ran this, as instructed
identity create storagenode
and it started generating keys just fine… and green lights across the board
identity create storagenode
Generating key with a minimum a difficulty of 36...
Generated 123683548 keys; best difficulty so far: 37
Found a key with difficulty 37!
Unsigned identity is located in "/root/.local/share/storj/identity/storagenode"
Please *move* CA key to secure storage - it is only needed for identity management and isn't needed to run a storage node!
/root/.local/share/storj/identity/storagenode/ca.key
when finished i noticed that the storagenode log was flashing red, and i shut it down, and after checking the logs started it back up again… with seemly no issues.
and is now 20 minutes later still running with out issues…
i duno what happened, but i can only somehow assume that the creation of the new identity disrupted my existing identity running on the storagenode…
i’m running proxmox (debian buster) which hosts docker directly on the host where i also generated the identity, tho i will state again… the identity locations are completely unrelated to each other, afaik… and i did after all configure it so…
pretty sure this could have killed a node… but i can only speculate, happy i caught it…
i suppose this isn’t a troubleshooting, but more of a bug report…
would be nice if somebody else can confirm this issue.