*******************************************************************************************************************
*******************************************************************************************************************
█████╗░░█████╗░░█████╗░██╗░░██╗███████╗███╗░░██╗██████╗░██╗░░░░░███████╗░██████╗░██████╗ ██████╗░██████╗░░█████╗░
██╔══██╗██╔══██╗██╔══██╗██║░██╔╝██╔════╝████╗░██║██╔══██╗██║░░░░░██╔════╝██╔════╝██╔════╝ ██╔══██╗██╔══██╗██╔══██╗
██████╦╝███████║██║░░╚═╝█████═╝░█████╗░░██╔██╗██║██║░░██║██║░░░░░█████╗░░╚█████╗░╚█████╗░ ██████╔╝██████╔╝██║░░██║
██╔══██╗██╔══██║██║░░██╗██╔═██╗░██╔══╝░░██║╚████║██║░░██║██║░░░░░██╔══╝░░░╚═══██╗░╚═══██╗ ██╔═══╝░██╔══██╗██║░░██║
██████╦╝██║░░██║╚█████╔╝██║░╚██╗███████╗██║░╚███║██████╔╝███████╗███████╗██████╔╝██████╔╝ ██║░░░░░██║░░██║╚█████╔╝
╚═════╝░╚═╝░░╚═╝░╚════╝░╚═╝░░╚═╝╚══════╝╚═╝░░╚══╝╚═════╝░╚══════╝╚══════╝╚═════╝░╚═════╝░ ╚═╝░░░░░╚═╝░░╚═╝░╚════╝░
Copyright 2012-2023, Backendless Corp. All rights reserved.
Congratulations, the initial part of the Backendless Pro installation is complete. To proceed with the installation,
open a web browser and navigate to <instance IP address>:5050
server@server-OptiPlex:~$ journalctl -u pro-manager.service -f
Jan 19 11:50:09 server-OptiPlex systemd[1]: pro-manager.service: Failed with result 'exit-code'.
Jan 19 11:50:09 server-OptiPlex systemd[1]: pro-manager.service: Scheduled restart job, restart counter is at 4.
Jan 19 11:50:09 server-OptiPlex systemd[1]: Started pro-manager.service - Backendless Pro Manager.
Jan 19 11:50:09 server-OptiPlex (bash)[20995]: pro-manager.service: Changing to the requested working directory failed: No such file or directory
Jan 19 11:50:09 server-OptiPlex systemd[1]: pro-manager.service: Main process exited, code=exited, status=200/CHDIR
Jan 19 11:50:09 server-OptiPlex systemd[1]: pro-manager.service: Failed with result 'exit-code'.
Jan 19 11:50:09 server-OptiPlex systemd[1]: pro-manager.service: Scheduled restart job, restart counter is at 5.
Jan 19 11:50:09 server-OptiPlex systemd[1]: pro-manager.service: Start request repeated too quickly.
Jan 19 11:50:09 server-OptiPlex systemd[1]: pro-manager.service: Failed with result 'exit-code'.
Jan 19 11:50:09 server-OptiPlex systemd[1]: Failed to start pro-manager.service - Backendless Pro Manager.
Status
> server@server-OptiPlex:~$ sudo systemctl status pro-manager.service
[sudo] password for server:
× pro-manager.service - Backendless Pro Manager
Loaded: loaded (/etc/systemd/system/pro-manager.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Sun 2025-01-19 11:50:09 EST; 2min 5s ago
Duration: 1ms
Docs: https://github.com/Backendless/pro-manager#readme
Process: 20995 ExecStart=/bin/bash -c PATH=/home/bl-pro-manager/.nvm/versions/node/v14.18.2/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/b>
Main PID: 20995 (code=exited, status=200/CHDIR)
CPU: 445us
Jan 19 11:50:09 server-OptiPlex systemd[1]: pro-manager.service: Scheduled restart job, restart counter is at 5.
Jan 19 11:50:09 server-OptiPlex systemd[1]: pro-manager.service: Start request repeated too quickly.
Jan 19 11:50:09 server-OptiPlex systemd[1]: pro-manager.service: Failed with result 'exit-code'.
Jan 19 11:50:09 server-OptiPlex systemd[1]: Failed to start pro-manager.service - Backendless Pro Manager.
lines 1-13/13 (END)
Looks like they are the same command. It also looks like it makes a few assumptions.
Lets assume a vanilla Ubuntu install, which is missing curl
sudo apt install curl
Which then allows me to run your script
curl -o- https://raw.githubusercontent.com/Backendless/pro-manager/main/install-ubuntu.sh | bash -s -- main
This is the output
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 5744 100 5744 0 0 41276 0 --:–:-- --:–:-- --:–:-- 41323
Passed branch is ‘main’
creating user bl-pro-manger
passwd: password changed.
info: Adding user bl-pro-manager' to group sudo’ …
info: Adding user bl-pro-manager' to group adm’ …
info: Adding user bl-pro-manager' to group systemd-journal’ …
Backendless Pro Manager installation started at Tue Jan 21 05:02:49 PM EST 2025
in working folder /home/bl-pro-manager
installing nvm to /home/bl-pro-manager/.nvm …
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 15037 100 15037 0 0 796k 0 --:–:-- --:–:-- --:–:-- 815k
Downloading nvm as script to ‘/home/bl-pro-manager/.nvm’
Failed to download ‘https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.1/bash_completion’
Failed to download ‘https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.1/nvm-exec’
Failed to download ‘https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.1/nvm.sh’
Appending nvm source string to /home/bl-pro-manager/.bashrc
Appending bash_completion source string to /home/bl-pro-manager/.bashrc
main: line 435: /home/bl-pro-manager/.nvm/nvm.sh: No such file or directory
Close and reopen your terminal to start using nvm or run the following to use it now:
export NVM_DIR=“$HOME/.nvm”
[ -s “$NVM_DIR/nvm.sh” ] && . “$NVM_DIR/nvm.sh” # This loads nvm
[ -s “$NVM_DIR/bash_completion” ] && . “$NVM_DIR/bash_completion” # This loads nvm bash_completion
nvm installed
bash: line 21: nvm: command not found
bash: line 22: nvm: command not found
installing k3s…
[INFO] Finding release for channel stable
[INFO] Using v1.31.4+k3s1 as release
[INFO] Downloading hash https://github.com/k3s-io/k3s/releases/download/v1.31.4+k3s1/sha256sum-amd64.txt
[ERROR] Download failed
k3s installed
sudo: k3s: command not found
saved k3s config to work dir
cloning main
bash: line 37: git: command not found
bash: line 39: cd: pro-manager: No such file or directory
bash: line 41: git: command not found
bash: line 43: npm: command not found
systemd: Creating service file pro-manager
system daemon reloaded. Starting pro manager
Created symlink /etc/systemd/system/multi-user.target.wants/pro-manager.service → /etc/systemd/system/pro-manager.service.
pro-manager.service enabled
● pro-manager.service - Backendless Pro Manager
Loaded: loaded (/etc/systemd/system/pro-manager.service; enabled; preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Tue 2025-01-21 17:02:50 EST; 5ms ago
Docs: GitHub - Backendless/pro-manager
Process: 12000 ExecStart=/bin/bash -c PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/bl-pro-manager/.nvm/versions/node/v14.18.2/bin exec /home/bl-pro-manager/.nvm/versions/node/v14.18.2/bin/node ./src (code=exited, status=200/CHDIR)
Main PID: 12000 (code=exited, status=200/CHDIR)
CPU: 436us
installing ingress
bash: line 72: kubectl: command not found
bash: line 74: kubectl: command not found
installing cert manager
bash: line 78: kubectl: command not found
list Issuers,ClusterIssuers,Certificates,CertificateRequests,Orders,Challenges
bash: line 81: kubectl: command not found
list kubernetes events
bash: line 84: kubectl: command not found
It looks like the Github Doc was removed. That had some commands to check the status of pro manager which are missing from the docs you linked to here. Can you add them?