Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fatal: not a git repository #280

Open
ainsean opened this issue Mar 3, 2025 · 3 comments
Open

fatal: not a git repository #280

ainsean opened this issue Mar 3, 2025 · 3 comments

Comments

@ainsean
Copy link

ainsean commented Mar 3, 2025

Centos 9:
Node.js version: v20.18.3
Yarn version: 1.22.22

Server specs
1 vCPUs and 4GB RAM on the machine where I attempt to install

Issue
It is not installing and giving git error each time I run the script

Installation logfile
Attach complete log as a file.
Dependencies resolved.
Nothing to do.
Complete!

  • command -v node
    /usr/bin/node
  • node -v 2>/dev/null| grep -Eo '[0-9.]+' | cut -d'.' -f1
    20
  • command -v yarn
    /usr/bin/yarn
  • command -v vhdimount
  • /bin/systemctl enable redis && /bin/systemctl start redis
  • /bin/systemctl enable rpcbind && /bin/systemctl start rpcbind
  • cd "/opt/xo/xo-src/xen-orchestra" && git remote set-url origin "https://github.com/vatesfr/xen-orchestra" && git fetch --prune && git reset --hard origin/master && git clean -xdff
    fatal: not a git repository (or any of the parent directories): .git
    [root@centosstream9 XenOrchestraInstallerUpdater]#
@ainsean
Copy link
Author

ainsean commented Mar 3, 2025

Welcome to automated Xen Orchestra install

Following options will be used for installation:

OS: CentOS 9
Basedir: /opt/xo
User: root
Port: 80
HTTPS: false
Git Branch for source: master
Following plugins will be installed: all
Number of previous installations to preserve: 3
Node.js and yarn auto update: true

Errorlog is stored to /xoa/XenOrchestraInstallerUpdater/logs/xo-install.log-202503031236 for debug purposes

Depending on which installation is chosen:

Xen Orchestra configuration will be stored to /root/.config/xo-server/config.toml, if you don't want it to be replaced with every update, set CONFIGUPDATE to false in xo-install.cfg
Xen Orchestra Proxy configuration will be stored to /root/.config/xo-proxy/config.toml. Config won't be overwritten during update, ever

  1. Install
  2. Update
  3. Rollback
  4. Install proxy
  5. Update proxy
  6. Exit

: 1

[ok] Installing build dependencies, redis server, python3, git, nfs-utils, cifs-utils, lvm2, ntfs-3g, dmidecode patch

[info] Checking current node.js version

[info] node.js version already on 20

[ok] Enabling and starting redis service

[ok] Enabling and starting rpcbind service

[info] Fetching Xen Orchestra source code

[fail] Something went wrong, exiting. Check /xoa/XenOrchestraInstallerUpdater/logs/xo-install.log-202503031236 for more details and use rollback feature if needed
[root@centosstream9 XenOrchestraInstallerUpdater]# pwd
/xoa/XenOrchestraInstallerUpdater

@ainsean
Copy link
Author

ainsean commented Mar 3, 2025

increased cpu count to 2 but still same issue

@ronivay
Copy link
Owner

ronivay commented Mar 3, 2025

Run sudo rm -rf /opt/xo/xo-src and try again. Seems that the XO source directory clone has partially failed before.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants