Important note: This process is generally used to recover a primary headnode from a failure state (filesystem corruption for example). This process doesn’t replace a good backup regime. If you intend to use this process to recover a primary headnode, we recommend contacting Bright Support first so we may assess…
*Please note:* Shorewall provides a NAT Masquerade rule that allows the compute nodes to access networks that are outside the cluster via the headnode. If you are okay with the compute nodes not having access to external networks or aren’t using the headnode as the default gateway for the compute…
During the installation of a bare metal headnode using the Bright Installation ISO written to a USB drive, you may find both the GUI and text installation modes fail or get stuck at the Rootfs step. The message from systemd on the server console may look like this: “A start…
The Linux Kernel ABI compatibility appears to have been broken in newer Linux kernel releases.This appears to affect the kernels in SLES12 SP5, RHEL/CentOS 7.7 onwards, RHEL/Centos 8.1 onwards. There may be other versions affected as well. For example: SLES 15 The issue shows up as follows when attempting to…
We recommend not using Rufus to create a bootable USB drive from the Bright ISO.Rufus changes the ISO Hybrid disk format which results in the Bright installer failing at the rootfs part of the Bright installer.
The “Failed to initialize NVML: Driver/library version mismatch?” error generally means the CUDA Driver is still running an older release that is incompatible with the CUDA toolkit version currently in use. Rebooting the compute nodes will generally resolve this issue. If you do not wish to reboot the compute node,…
Here is an example of enabling QOS (Quality of Service) in SchedMD Slurm and applying the QOS to a partition using Bright. *Please note this is valid for Bright 8.2 and earlier releases. Finally update the options for the partition in Bright to use this new QOS configuration.