Ah ok, here’s a few things to try. First, you could install hs-client globally: npm i hs-client -g
(Or clone from github and npm i -g from inside the repo)
This will make hsd-cli available from the command line, and you can start following the api docs at https://handshake-org.github.io/api-docs/
I realize hs-client is not well advertised in the docs right now, I’ll open an issue about that.
Second, it’s interesting that your getinfo reports a chain height of 11189 and progress 1 – that is a fully synced chain!
This leads me to believe that the cause of the LOCK: Resource temporarily unavailable error is… you already have hsd running!
To start clean, just execute killall hsd, then try to run hsd again.
Cloned the repo and installed (looks like i had to be sudo). So I now have ‘hsd-cli’
Restarted hsd, and it’s looking a LOT different. Looks like hsd is now actually ‘doing’ something via the output.
I am getting a lot of: Connection timed out…
I see that “refilling peers” I seem to be getting somewhere with this… looks like I’ve got (7/8) peers…
Basically, this ‘connection timed out’ can be ignored? Also, what else can I look at to double check I’m fully up?
Yeah it’s hard to find consistently reliable peers on a young network like this, so expect to see a lot of messages about stalling peers. Even on the Bitcoin network it can take a few minutes of runtime to fill the pool (of peers) to the default size of 8.
Check out the api-docs site I linked, lots to play with there. As far as “fully up” – the progress percentage in hsd-cli info is your answer to that. There’s also a few guides to get you started at https://handshake-org.github.io/