If anyone think they can help and would like to pair with me on this it would be much appreciated. I would of course pay for the time spend even if we don’t get it working.
jdj_dk
Exadra37
Currently the info you have given seems to broad for the ones with experience in libcluster and releases may try to help you.
Try to make a simple repo where the problem is reproducible and then share the link to it here.
Also mention what hosting provider you are using and if you are using any special deployment strategy.
0
jdj_dk
I’m using AWS Lightsail instances.
Libcluster is not a part of the problem right now. It’s just getting rid of the error caused by the node getting the old hostname. I’ll try setting up a new instance and see if that fixes the issue.
0
jarimatti
This is a bit grasping for straws here, but are you sure the correct environment variable values reach the release startup scripts (and the application)? I’ve set up libcluster successfully in AWS Fargate using RELEASE_DISTRIBUTION and RELEASE_NODE and this was one of the hurdles. Unfortunately I don’t know Lightsail that much.
To debug this you can try to sprinkle echo statements in shell scripts and perhaps check the app environment if you have access to the Elixir shell.
Edit: not a bit for grasping straws, more a lot…
0
jdj_dk
I really appreciate your input. Thank you so much for taking the time to grasp for straws.
So I’ve looked a bit more into it. From what I can see, when I look at the process systemctl starts up using the environment variables, it seems to set the correct --name param to the domain that is reachable from the outside world.
But still, the app complains that another Hostname is set, which is not legal. I can’t connect to the running app because it never finishes starting.
I’m running Elixir 1.10.3 and erlang 23.0.2.
0
Exadra37
NobbZ
No, the s in sname is for “short”. Some check in the BEAM will even error if there is a dot in a sname.
1
fsa
More straw grasping - you can try to put this at the top/start of some/any scripts you would like to debug:
set -x
it echoes results of the commands in the script file as it executes…
( you can also run it as:
sh -x scriptname
if you can’t/don’t want to edit the scripts themselves)
Best of luck.
1
PaulOlukayode
export RELEASE_DISTRIBUTION=name
export RELEASE_NODE=bimip@wsone.local
export RELEASE_COOKIE=mysecret
what os are u using?. add the VPS info here and export and restart your server.
0