- Qlustar General - Qlustar Mailing Lists

MD5 and SHA256 hashes for the QluMan 12.0.7.5 Singularity image don't match those shown in the Download page
by Beethoven Santos 30 Nov '24

30 Nov '24

Hi, Whenever I download the file `qluman-12.0.7.5-singularity.sqsh` and use the `md5sum` and `sha256sum` commands to check its MD5 and SHA256 hashes, I find that they do not match the hash values shown on the [Download page](https://qlustar.com/download/) for this version (all others are ok). For this reason, I believe that using this file is not safe and I should avoid it. Is this something on Qlustar's side? Could anyone confirm this issue? Best B. Santos

2 2

How to add GrestTypes to slum.conf?
by uchida＠ulgs.jp 28 Nov '24

28 Nov '24

Hi, Now I'm using, qlustar management interface, but GPU wizard do delete the GresTypes=gpu to GresTypes=, then it caused an error as follows, ### beosrv-c ### writing /etc/qlustar/common/slurm-llnl/slurm.conf writing /etc/qlustar/common/slurm-llnl/gres.conf writing /etc/qlustar/common/slurm-llnl/cgroup.conf postcmd: service slurmctld restart; echo ' * Waiting for slurmd to be ready...'; sleep 5; scontrol reconfigure Job for slurmctld.service failed because the control process exited with error code. See "systemctl status slurmctld.service" and "journalctl -xeu slurmctld.service" for details. * Waiting for slurmd to be ready... scontrol: error: Parse error in file /etc/qlustar/common/slurm-llnl/slurm.conf line 169: "GresTypes=" scontrol: fatal: Unable to process configuration file 1 How to fix it and how to add GressTypes? Can I set as GresTypes=gpu,mps ? Regards, Morihisa

2 1

qluman-qt can't work
by uchida＠ulgs.jp 28 Nov '24

28 Nov '24

Hi, singularity image of qluman 13.7.0 and qluman-qt can't work to access at first time. It shows, File "/usr/lib/python3/dist-packages/qluman-13/client/qt/ConnectClusterDialog.py", line 846, in on_okButton_clicked cluster = ClusterInfo(alias=self.aliasLineEdit.text(), File "/usr/lib/python3/dist-packages/qluman-13/common/LoginData.py", line 169, in __init__ (self.client_pubkey, self.client_seckey) = zmq.curve_keypair() NameError: name 'zmq' is not defined Is there any workaround? Regards,

4 10

A new approach to Cluster High-Availability
by no-reply-list＠qlustar.org 20 Nov '24

20 Nov '24

The Qlustar team is pleased to announce the first public release of QluMan HA as the new driver of the Qlustar HA stack. Implemented on top of general Qlustar functionality, QluMan HA was *specifically designed for HPC, AI and Storage cluster solutions* where a scalable number of compute and storage nodes are controlled and managed by a pair of redundant head-nodes. Read the full announcement at https://qlustar.com/news/2024/2024-11-19-qluman-ha

1 0

Security/Bug fix releases 13.2.2, 12.0.3.8
by no-reply-list＠qlustar.org 19 Oct '24

19 Oct '24

The Qlustar releases 13.2.2 and 12.0.3.8 are ready including a number of security/bug fixes. Please check the following web pages for details about security fixes and special update instructions: https://qlustar.com/qsa/2024/1019241 https://qlustar.com/qsa/2024/1019242 The following non-security related updates/enhancements/bug fixes are included: For Qlustar 13 only: - Update to QluMan 13.7.0 + GUI improvement: Save open windows for each cluster tab and reopen them when reconnecting + Catch errors parsing LDAP user data and handle users without gecos field

1 0

Problem after upgrade to latest Qlustar 13
by Rolandas Naujikas 24 Aug '24

24 Aug '24

Hi, There are problem to create jammy chroot via qluman (3.6.0) GUI. As a workaround I tried to do that from cli with manage-qlustar-chroot. The problem is with version field. In qluman I can select only 13.1 or 13.2 - both don't work. Only 13.0 from cli works. I rechecked with freshly installation from 13.2-2 iso - the same problem. At least qlustar-initial-install script creates jammy chroot successfully. Regards Rolandas

2 1

Security/Bug fix releases 13.2.1, 12.0.3.7
by no-reply-list＠qlustar.org 24 Aug '24

24 Aug '24

The Qlustar releases 13.2.1 and 12.0.3.7 are ready including a number of security/bug fixes. Please check the following web pages for details about security fixes and special update instructions: https://qlustar.com/qsa/2024/0822241 https://qlustar.com/qsa/2024/0822242 The following non-security related updates/enhancements/bug fixes are included: For Qlustar 13 only: - Update to QluMan 13.6.3 + Fix jammy chroot creation + Make argument replacement in Remote Management Configs more powerful to also support IPMI addresses in networks where OS *AND* IPMI adapters are present.

1 0

Re: qlustar-general@qlustar.org post from praveen@aukcomputing.com requires approval
by Roland Fehrenbacher 31 Jul '24

31 Jul '24

On 7/24/24 14:37, Praveen Fernando wrote: > After the re-installation, I received the server, and I completed the > one-node installation, which is also operating properly. OK, very good. > How to sync with Slurm user During creating user, I can't see the > Slurm group management in the user creation page, thus I have to > enable anything or some configuration settings. Please consult the subsection 'LDAP Sync Groups' at https://docs.qlustar.com/Qlustar/13/ClusterOS/qluman-guide/components/slurm… > I need some additional help, like installing pbs in that cluster. > Could you please give the specifics if you have? Qlustar does not support PBS. Best, Roland

1 0

Problem, and Potential Long-Term Solution, when Replacing Nodes Related to dnsmasq.leases
by hereiam＠mit.edu 30 Jul '24

30 Jul '24

Dear Qlustar Users, I'm running what I think may be the world's worst supercomputer (for fun), composed entirely of different spec laptops. This was a pandemic project gone amok, just to see what is possible. I've used the opportunity to figure out how to do some strange things, one of which includes replacing nodes quickly and frequently on a Qlustar-based system, as laptops fail fairly often when used as HPCs. The Problem: When deleting a host from Qluman (13.6.0, and many previous versions), and trying to assign a new physical machine to the exact same hostname (an attempt at drop-in replacement), it never acquired a DHCP license. Everything looked good from Qluman's side, but the new node would never get a DHCP license to start loading/booting Qlustar. It would, however, after restarting the head node. I'd rather not do that after every drop-in replacement. The Solution: I found that each host has an entry in /var/lib/misc/dnsmasq.leases which blocks Qluman and such from truly assigning it as a new hosts. If instead I first delete that entry from dnsmasq.leases, restart the dnsmasq service by typing 'service dnsmasq restart,' and also rewrite the Slurm Config file (causing the slurmctl service to also restart), it works! The Request: Could the Qlustar mods please consider a line in the "Delete Hosts" menu option in the Enclosure Vire of Qluman's scripts, which greps dnsmasq.leases for any line with that host name and deletes it, and restarts the dnsmasq service? I think that would do the trick, but I may be mistaken. Happy to discuss more if you'd all like! Sincerely, -Mike

2 1

Need a help
by Praveen Fernando 24 Jul '24

24 Jul '24

Hi team, After installation, attempting to create the key results in the following error. can you help me qluman-cli --gencert ERROR:client.cli.network:client.cli.network.Cluster.__init__(): could not connect to server Error: No such user: 'admin' ERROR:qlunet.Channel:Channel[(b'qluman-cli', 1)].do_recv(): exception in request generator Traceback (most recent call last): File "/usr/lib/python3/dist-packages/qluman-13/qluman-cli.py", line 1546, in gencert db.users.lookup(field="name", val=user) File "/usr/lib/python3/dist-packages/qluman-13/common/types.py", line 2216, in lookup raise KeyError("{0}={1}".format(field, val)) KeyError: 'name=admin' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/qlunet/Channel.py", line 88, in do_recv args = next(self._generator) File "/usr/lib/python3/dist-packages/qluman-13/qluman-cli.py", line 1549, in gencert sys.exit(1) SystemExit: 1 how to create the User admin ? Regards DISCLAIMER: The information contained in this email is confidential and may be legally privileged. It is intended solely for the addressee and access by anyone else is unauthorized you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our customers, any information contained in this e-mail is subject to our standard terms and conditions. The views in this email may not necessarily reflect the views of the company.

2 2

2025

2024

2023

2022

2021

2020

2019

2018

Qlustar General