In general you need a third-party application to manage password policies as Bright doesn't provide this functionality.
simon.brennan.cu Bright Support Support & Deployment Engineer
To get started, use the search bar at the top and begin typing in what you are looking for, results will start to display almost immediately.
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:... (More)
There is a great article available on the Mellanox website.
The quick start version is once the Mellanox OFED is installed and the openidb service is running....
# service mst start
The easiest solution is to use the yum downgrade command to rollback the package versions.
You can change the TLS version by setting the SSLServerMethod advanced config in /cm/local/apps/cmd/etc/cmd.conf (on the head node) to the desired version of TLS such as "TLS 1.2". Then follow that with your cipher list options. For example:
AdvancedConfig =... (More)
There is no Bright specific way to configure sudoers, you would follow the standard Linux instructions to set this up.
On the headnode you would run the visudo command and add any users you wish to provide sudo access.
The "UP (restart required)" state explains that the node is currently up, however, the configuration was changed and a reboot of the node is required for the change to take affect.
An example of some configuration changes that can trigger... (More)
I guess one of the things to bear in mind is Bright uses shorewall to manage the underlying iptables firewall, so you might find the rules that get added directly to iptables by fail2ban may get removed when shorewall is... (More)
This is a known issue. You may resolve it by run running the following commands on the headnode.
# yum groupinstall GNOME # sed -i '/daemon/a InitialSetupEnable=false' /etc/gdm/custom.conf
Once complete, the startx command should start the GUI correctly.
As per the machine learning section of our manual:
"From Bright Cluster Manager version 9.0 onward the activation step via a wizard is not needed—the repository is automatically available and enabled."
After installation of Bright 9.0, the... (More)
As you have a support request open for this, we will work on the issue there.
However, for the benefit of the community, you may check the cm-upgrade.log file to determine the reason the upgrade failed.
On the... (More)
You would like to be able to make changes to the sdb filesystem on either the active or passive headnodes and that be automatically synchronised between the headnodes?
In general, the /etc/resolv.conf file on a compute node is managed by the node installer during provisioning.
Please see: https://support.brightcomputing.com/manuals/8.2/admin-manual.pdf#section.A.342
The "non-headnode" we're talking about, is that a login node perhaps? Else, what function does it serve?
If you wish... (More)
I can see you've opened a support request for this issue. We will investigate this for you as soon as possible. Once we have an outcome, we'll update this question for the benefit of everyone else in the... (More)
Could you confirm the Bright version and the distribution (CentOS, Ubuntu, SLES) you are trying to install as an Addon installation? Thank you.
Yes, the head node uses one license.
On the primary active head node, take a look in the /var/log/cloneinstalllog file. It should show the reason for the failure.
For future reference incase someone else comes across this issue, the Bright ISO comes with a 2 node trial license by default.
Installing your Easy8 license is documented here in the installation manual:
If the chassis is a standalone entry in Bright with each blade showing as separate compute nodes, you may close the device to disable monitoring.
% device use c6000-1
This will disable monitoring and... (More)