Tips on installing XO
-
You may want to try removing the service and then installing it again.
-
Hi @Danp,
How? -
@jasonnix Documentation for
forever
can be found at https://github.com/zapty/forever-service -
@Danp, according to the XO documentation I ran the following command:
$ sudo forever-service install orchestra -r "Current_UserName" -s dist/cli.mjs
Is this wrong?
-
@jasonnix AFAIK it is correct. I've never personally used
forever
, so my advice is only based on what you've posted to this thread.This part looked suspicious, so that is why I recommended removal / recreation --
# forever start dist/cli.mjs warn: --minUptime not set. Defaulting to: 1000ms warn: --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms info: Forever processing file: dist/cli.mjs (node:742838) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency (Use `node --trace-warnings ...` to show where the warning was created) (node:742838) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency (node:742838) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
-
Hi @Danp,
I did:# sudo forever-service delete orchestra forever-service version 0.5.11 Platform - Debian GNU/Linux 12 (bookworm) Service orchestra deleted successfully
What is the next step? Should I run
$ sudo forever-service install orchestra -r "Current_UserName" -s dist/cli.mjs
command again? -
These are the steps shown in the documentation --
yarn global add forever yarn global add forever-service # Be sure to edit the path below to where your install is located! cd /home/username/xen-orchestra/packages/xo-server/ # Change the username below to the user owning XO forever-service install orchestra -r username -s dist/cli.mjs
I don't see where you previously ran the line to install
forever-service
. Is that no longer needed?To answer your question, Yes, you would rerun that command after switching to the correct directory as shown above.
-
Hi @Danp,
I did the following commands:# yarn global add forever yarn global v1.22.21 [1/4] Resolving packages... [2/4] Fetching packages... [3/4] Linking dependencies... [4/4] Building fresh packages... success Installed "forever@4.0.3" with binaries: - forever Done in 5.19s. # # yarn global add forever-service yarn global v1.22.21 [1/4] Resolving packages... [2/4] Fetching packages... [3/4] Linking dependencies... [4/4] Building fresh packages... success Installed "forever-service@0.5.11" with binaries: - forever-service - get-forever-config Done in 4.48s. # # forever-service install orchestra -r xo -s dist/cli.mjs forever-service version 0.5.11 Platform - Debian GNU/Linux 12 (bookworm) orchestra provisioned successfully Commands to interact with service orchestra Start - "sudo service orchestra start" Stop - "sudo service orchestra stop" Status - "sudo service orchestra status" Restart - "sudo service orchestra restart" # # sudo service orchestra start # # sudo service orchestra status ā orchestra.service - LSB: forever-service startup script for orchestra Loaded: loaded (/etc/init.d/orchestra; generated) Active: active (exited) since Thu 2024-03-28 08:38:18 EDT; 22s ago Docs: man:systemd-sysv-generator(8) Process: 199365 ExecStart=/etc/init.d/orchestra start (code=exited, status=0/SUCCESS) CPU: 19ms Mar 28 08:38:16 XO systemd[1]: Starting orchestra.service - LSB: forever-service startup script for orchestra... Mar 28 08:38:17 XO orchestra[199365]: Starting orchestra Mar 28 08:38:18 XO systemd[1]: Started orchestra.service - LSB: forever-service startup script for orchestra. # # systemctl enable orchestra.service orchestra.service is not a native service, redirecting to systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable orchestra
Then I rebooted the system, but XO is not running:
# ss -tupln Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process udp UNCONN 0 0 0.0.0.0:111 0.0.0.0:* users:(("rpcbind",pid=472,fd=5),("systemd",pid=1,fd=37)) udp UNCONN 0 0 [::]:111 [::]:* users:(("rpcbind",pid=472,fd=7),("systemd",pid=1,fd=39)) tcp LISTEN 0 4096 0.0.0.0:111 0.0.0.0:* users:(("rpcbind",pid=472,fd=4),("systemd",pid=1,fd=36)) tcp LISTEN 0 511 127.0.0.1:6379 0.0.0.0:* users:(("redis-server",pid=517,fd=6)) tcp LISTEN 0 511 [::1]:6379 [::]:* users:(("redis-server",pid=517,fd=7)) tcp LISTEN 0 4096 [::]:111 [::]:* users:(("rpcbind",pid=472,fd=6),("systemd",pid=1,fd=38))
The log shows me the following error:
2024-03-28T12:45:02.002Z xo:main WARN Access denied. 2024-03-28T12:45:02.003Z xo:main WARN Ports < 1024 are often reserved to privileges users. ā EACCES: permission denied, open '/home/xo/.config/xo-server/config.z-auto.json' Error: EACCES: permission denied, open '/home/xo/.config/xo-server/config.z-auto.json' {"level":"error","message":"Forever detected script exited with code: 1"} {"level":"error","message":"Script restart attempt #28"}
What should I do if I want to completely remove XO and use the script xenorchestra_installer?
-
2024-03-28T12:45:02.002Z xo:main WARN Access denied.
2024-03-28T12:45:02.003Z xo:main WARN Ports < 1024 are often reserved to privileges users.
EACCES: permission denied, open '/home/xo/.config/xo-server/config.z-auto.json'Did you read this part of the documentation? https://xen-orchestra.com/docs/installation.html#sudo
What should I do if I want to completely remove XO and use the script xenorchestra_installer?
I hope that was more of a rhetorical question, because your best option is to simply spin up a new VM and start over. There are other options as well --
- Revert to an existing snapshot that you took prior to all of the above
- Remove the
/home/username/xen-orchestra
directory and hope for the best
-
@Danp, Yes. I read.
These were questions that I had asked before and no one answered:
1- Should I run the commands as root or sudo?2- Which directory is suitable to clone XO? I want to clone it in the /usr/local/src directory and this requires administrative access.