https://www.umh.app logo
Join Discord
Powered by
I'm trying to install UMH Instance on
# umh-support
r
I'm trying to install UMH Instance on Rocky linux environment where password auth is removed and can only log in as non-root user. I try to run the command from the UMH default install command:
Copy code
sudo curl https://management.umh.app/static/automatic/install.sh ....
But then I get errors regarding the /tmp/ location as permission denied. I tried running the full set of commands as sudo:
Copy code
sudo bash -c "
curl https://management.umh.app/static/automatic/install.sh -o /tmp/install.sh &&
chmod +x /tmp/install.sh && 
....
But I'm getting:
Copy code
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0Warning: Failed to create the file /tmp/install.sh: Permission denied
  1  107k    1  1360    0     0   6238      0  0:00:17 --:--:--  0:00:17  6210
curl: (23) Failure writing output to destination
The only solution was to switch to a different folder under root:
Copy code
sudo bash -c "
curl https://management.umh.app/static/automatic/install.sh -o /root/install.sh &&
chmod +x /root/install.sh &&
...
But I'm not sure what the consequences of this are and if it will affect the stability of the installation. I can't seem to find any guidance on this. When I installed it without sudo as user rocky, I got a bunch of errors in the Management Console regarding the cluster infrastructure. What is the right solution here?
Actually I'm still getting the same errors even after installing as root user with sudo: Warning K3s Error: Unhealthy, Message: Liveness probe failed: Get "http://10.42.0.100:8080/health": dial tcp 10.42.0.100:8080: connect: connection refused K3s Error: Unhealthy, Message: Readiness probe failed: Get "http://10.42.0.100:8080/readiness": dial tcp 10.42.0.100:8080: connect: connection refused K3s Error: Unhealthy, Message: Liveness probe failed: Get "http://10.42.0.99:8080/health": dial tcp 10.42.0.99:8080: connect: connection refused K3s Error: Unhealthy, Message: Readiness probe failed: Get "http://10.42.0.99:8080/readiness": dial tcp 10.42.0.99:8080: connect: connection refused K3s Error: BackOff, Message: Back-off restarting failed container united-manufacturing-hub-packmlmqttsimulator in pod united-manufacturing-hub-packmlmqttsimulator-7d86c9474b-kmdxf_united-manufacturing-hub(039cebf2-208a-4f2c-994a-d560243f500a) K3s Error: Unhealthy, Message: Readiness probe failed: Get "http://10.42.0.84:3000/api/health": dial tcp 10.42.0.84:3000: connect: connection refused K3s Error: BackOff, Message: Back-off restarting failed container united-manufacturing-hub-kafkatopostgresqlv2 in pod united-manufacturing-hub-kafkatopostgresqlv2-55c4d85b56-hj4s9_united-manufacturing-hub(42de0f5f-e2e4-4227-8a84-5ac14a660425) K3s Error: BackOff, Message: Back-off restarting failed container grafana in pod united-manufacturing-hub-grafana-86d5df66c-7hg7s_united-manufacturing-hub(574dbf5b-930d-493d-aeee-5b49c461febb) K3s Error: Unhealthy, Message: Liveness probe failed: Get "http://10.42.0.66:8080/admin/health": dial tcp 10.42.0.66:8080: connect: connection refused
f
Try using 
sudo -i
to elevate yourself
as for the k3s events, these will appear at the beginning, our stack takes a while to fully start up
r
elevated with sudo -i, but having the same issues, it may be something on my VM's configuration, I'll look into it. And thank you I'll give it some time and wait for it to be up for a while
Turns out the issue is actually just downloading the install script to the /tmp directory, which is denied for root user for some reason.... https://unix.stackexchange.com/questions/503111/group-permissions-for-root-not-working-in-tmp https://askubuntu.com/a/1251030 I'm guessing it was a Linux wide change that occured a few years ago. So I'll just download the script as non root and install with sudo. I guess the error I was seeign was actually just due to not giving it enough time to get all of the cluster up and running
PreviousNext
Powered by