Ambassadors

People talking about XCP-ng/XO around them

Posts

  • RE: Facing some issue in copy Function of Xen Orchestra

    @irtaza9 i would look a the usual suspect,
    /var/log/SMlog
    /var/log/xensource.log

    see https://docs.xcp-ng.org/troubleshooting/

  • RE: Facing some issue in copy Function of Xen Orchestra

    @irtaza9 Hi !

    My instinct says it can be due to XAPI timeout: https://docs.xcp-ng.org/management/manage-locally/api/#24h-task-timeout

  • RE: [PACKER] soucis avec cd_files

    @jeremie1977 Ah, oui effectivement je n'ai pas testé avec plusieurs disques !

    Et j'ai du typo dans la doc, je vais faire une PR pour modifier 🤦

    Je pense que c'est du a la façon d'insérer les disques et les DVD coté XCP-ng. Je vais investiguer !

  • RE: Change default SSH port

    More options: to Prevent overwriting the file:
    Method 1: Probably the best option. Use a Configuration Directory. Modern OpenSSH versions (8.2+) support an include directive. This is the cleanest approach.
    Create a drop-in file: Put your custom settings in a separate file, such as /etc/ssh/sshd_config.d/custom.conf. The rule: Package updates will not touch files inside this directory. Verification: Ensure the line
    Include /etc/ssh/sshd_config.d/*.conf
    is active at the top of your main /etc/ssh/sshd_config file.
    Method 2: Lock the File (Alternative) You can force the filesystem to make the file immutable so nothing can change it.
    Lock the file: Run sudo chattr +i /etc/ssh/sshd_config
    Unlock for edits: Run sudo chattr -i /etc/ssh/sshd_config
    when you need to make intentional changes.
    Method 3: Tell Apt to Ignore Updates. If you are on a Debian-based system, you can force the package manager to always keep your local version. Add this line to /etc/apt/apt.conf.d/local: UCF_FORCE_CONFFOLD=true

    @stac00 Any progress or additional thoughts on any of this discussion?

  • RE: [PACKER] soucis avec cd_files

    Du coup j'ai testé avec RHEL 9, ça fonctionne aussi.

    Faut bien prendre l'iso "dvd", pas "boot" en revanche ! (je me suis fait avoir en téléchargeant l'image)

  • RE: Change default SSH port

    @poddingue The other option would be to be able to offer a different default /etc/ssh/sshd_config option but that's embedded in the Linux OS.
    One other possibility would be to create a startup job that runs out of /etc/rc.local and has a script that makes the changes after-the-fact. Just a thought...

  • RE: Change default SSH port

    @stac00 That's correct, it will not keep changes in the sshd_conf file.

    Instead,
    Step 1: Create a dedicated folder for custom OpenSSH daemon overrides. Systemd reads this folder to layer your custom preferences on top of the default package configurations.bashmkdir -p /etc/systemd/system/sshd.service.d

    Step 2: Write the Persistent Port OverrideCreate an override.conf file inside that new directory using nano:bashnano /etc/systemd/system/sshd.service.d/override.conf
    Use code with caution.
    Paste the following lines into the file (replace 2222 with your custom port number):ini[Service]
    ExecStart=
    ExecStart=/usr/sbin/sshd -D -p 2222 $OPTIONS
    (Note: The blank ExecStart= line is required; it instructs systemd to clear out the default command entirely before applying your custom command).

    Step 3: Update the Local Firewall (iptables)XCP-ng manages its firewall directly via iptables. You must insert a rule to accept traffic on the new port.bashiptables -I RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 2222 -j ACCEPT
    To ensure this rule survives host reboots, save the active rules:bashiptables-save > /etc/sysconfig/iptables
    Use code with caution.Step 4: Reload and TestTell systemd to reload its daemon configurations, and then restart the SSH service:bashsystemctl daemon-reload
    systemctl restart sshd
    Crucial Safety Check: Do not disconnect your current console window. Open a completely new terminal on your local machine and test the connection string using your new port number:bashssh -p 2222 root@<your-xcp-ng-ip>
    If you manage this host through an orchestrator, if you are using Xen Orchestra (XO) you may also need to update the custom management connection port inside your UI console.

    I hope this helps. I have not attempted this myself. so proceed with extreme caution! Again, be very careful to make sure it still works and is consistent everywhere it needs to be. The firewall rules are also critical.

  • RE: [PACKER] soucis avec cd_files

    @jeremie1977 j'ai un packer qui fonctionne avec RHEL 10 (c'est ce que j'avais sous la main), uefi, sans dhcp, et un cd file qui sert le ks

    Le code est ici: https://github.com/disruptivemindseu/xcpng-template-builder/tree/rhel-airgapped/packer/distros/rhel/10/uefi-airgapped

    Je vais essayer avec une RHEL 9 ce week-end, il y a peut-etre une subtilité entre les deux versions

  • RE: [PACKER] soucis avec cd_files

    @jeremie1977 Merci !

    Je teste ça de mon coté et je fais un feedback vite !

  • RE: [PACKER] soucis avec cd_files

    @jeremie1977 Bonjour !

    Pas de soucis pour les tutos, c'est normal de partager !

    Je vais essayer de reproduire votre soucis. Pour etre sur votre environnement:

    • RHEL (10?)
    • UEFI ?
    • Boot sans DHCP
    • Et un fichier Kickstart a passer sans la mĂ©thode HTTP ?