Closed Bob-The-Marauder closed 3 years ago
The riak-admin script doesn't appear to know about $ERTS_PATH (so this will impact other riak-admin commands like reip, backup and restore).
However, even after setting this I can't get it to work - it gets a connection error trying to connect to the Erlang VM.
More investigation required. @martincox any ideas?
One of the problems is resolved by adding observer to the list of applications. This doesn't resolve the path issue, but now etop will run (e.g. from remote_console)
The relx script uses $BINDIR as the ERTS_PATH, and export this - so the path issue is resolvable I think by adding
ERTS_PATH=$BINDIR
to the top of the riak-admin script.
Now fails with:
init terminating in do_boot ({cannot get bootfile,[PATH]/riak/rel/riak/bin/start.boot})
What is looking for start.boot (and not start_clean.boot which is there)?
using the -boot switch on the erl
command gets passed this - but still it fails:
Error Couldn't connect to node 'riak@127.0.0.1'
This is the right node name (as we're just running riak locally after make rel
). The bookie is being set. There is an issue with the naming of the hidden node (as $NAME_PARAM is not set to "-name" in the riak-admin script), but the error persists after resolving this.
I re-did these changes, and everything now appears to work. The connection error has not re-occurred in OTP20, OTP21 or OTP22.
https://github.com/basho/riak/pull/1049
@Bob-The-Marauder - can you review and test this PR please?
Tested and working. Thank you
Expected behaviour (from KV 2.9.8):
OR
Actual behaviour from KV 3.0.1:
OR