- Qlustar General - Qlustar Mailing Lists

Security/Bug fix releases 12.0.0.11-b547f1433 / 11.0.1.15-b543f1435
by Roland Fehrenbacher 25 May '22

25 May '22

The Qlustar releases 12.0.0.11-b547f1433 and 11.0.1.15-b543f1435 are ready including a number of security/bug fixes and improvements. Please check the following web pages for details about security fixes and special update instructions: https://qlustar.com/qsa/2022/0524221 https://qlustar.com/qsa/2022/0524222 https://qlustar.com/qsa/2022/0524223 The following non-security related enhancements/bug fixes are included: For 12.0 only: - Update to QluMan 12.0.7.1 - Update to slurm 21.08.8.2

1 0

login-c unknown hardware
by yohann.clement＠univ-lyon1.fr 23 May '22

23 May '22

Good morning, When installing qlustar, I choose the option front end via kom when I follow qluman, a message appears on login-c: unknown hardware. I can't connect to it via ssh what services should be activated/configured to connect to the front end thank you yohann

1 0

Qlustar 12 installation
by Jean-Luc Pons 19 Apr '22

19 Apr '22

Hello everyone First of all, thank you very much for the development of qlustar I am trying to reinstall qlustar 12.0 on my cluster and since the last update (04/14/22 on http://repo.qlustar.com) I have the following error: /usr/sbin/qlustar-initial-config ----------------------------- Fetched 186 MB in 29s (6364 kB/s) E: Failed to fetch http://repo.qlustar.com/repo/ubuntu-12.x/pool/main/q/qluman/qluman-slurmd_1… File has unexpected size (52504 != 52540). Mirror sync in progress? [IP: 188.68.35.17 80] Hashes of expected file: - SHA256:6668c331981204ba694ade94607acaddca6184cd664dde4085b0f80ca5879d85 - SHA1:eaf05531c795390221f58d6398a321baf68589b2 [weak] - MD5Sum:38b93670dfa3a41fde8de11b80c77a12 [weak] - Filesize:52540 [weak] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? qlustar-initial-config: Error while upgrading packages. Please make sure that package upgrade are possible. ----------------------------------- I am using the latest version of installer (gluster-installer-12.0.1-0.iso) Do you have an idea to fix it? cordially jluc -- Jean-Luc Pons Responsable du Service Informatique Centre de Biologie Structurale (http://www.cbs.cnrs.fr) CNRS UMR5048 - UM - INSERM U1054 29 rue de Navacelles 34090 - MONTPELLIER - France -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

2 1

Security/Bug fix releases 12.0.0.10-b547f1432 / 11.0.1.14-b543f1431
by Qlustar List 14 Apr '22

14 Apr '22

The Qlustar releases 12.0.0.10-b547f1432 and 11.0.1.14-b543f1431 are ready including a number of security/bug fixes and improvements. Please check the following web pages for details about security fixes and special update instructions: https://qlustar.com/qsa/2022/0413221 https://qlustar.com/qsa/2022/0413222 The following non-security related enhancements/bug fixes are included: For 12.0 only: - Update to Nvidia graphics driver version 510.47.03

1 0

No Bootable Device Found during post install boot
by ignas.bunikis＠scilifelab.uu.se 07 Apr '22

07 Apr '22

Hej, I was attempting to install Qlustar using latest installer (Qlustar Installer 12.0.1-0) on a few years old SuperMicro server. Installation seemed to go smooth, but after first reboot popped up boot error message that no bootable devices were found. During another installation attempt I noticed a couple of error message: * Failed to fetch file ..postfix... Hash sum mismatch * Failed to fetch file ..python-slurm... Hash sum mismatch * Failed to fetch file ..python3-slurm... Hash sum mismatch AND *GRUB/10-setup FAILED with exit code 127 After that installer says: Good news! No errors found in log files Do you have any ideas what could be an issue and what to do? Cheers, Iggy

2 1

Adding Users via QLUMAN
by yohann.clement＠univ-lyon1.fr 18 Mar '22

18 Mar '22

Hello, I am using the latest version of Qlustar 12.0 (FOCAL) I have a question about adding users. I use the qluman interface and I add an account via the menu component > ldap During the creation of the account, I have an error message which is the following: "Error 1 running add_user_hook /etc/qlustar/common/add-user-hook on beosrv-c: ('Unable to contact slurm controller (connect failure)', 1800) ('Unable to contact slurm controller (connect failure)', 1800) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/qluman-12/qluman-slurm-cli.py", line 66, in main slurm_acct = SlurmAcct(cf_file, dry_run=args.dryrun, reset_all_qos=args.reset_all_qos) File "/usr/lib/python3/dist-packages/qluman-12/components/slurm/cli.py", line 87, in __init__ self.get_slurm_ctl_info() File "/usr/lib/python3/dist-packages/qluman-12/components/slurm/cli.py", line 112, in get_slurm_ctl_info c = pyslurm.config() File "pyslurm/pyslurm.pyx", line 376, in pyslurm.pyslurm.config.__cinit__ File "pyslurm/pyslurm.pyx", line 432, in pyslurm.pyslurm.config.__load ValueError: ('Unable to contact slurm controller (connect failure)', 1800) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/qluman-12/qluman-slurm-cli.py", line 96, in <module> main() File "/usr/lib/python3/dist-packages/qluman-12/qluman-slurm-cli.py", line 69, in main sys.exit(1) NameError: name 'sys' is not defined Traceback (most recent call last): File "/usr/lib/python3/dist-packages/qluman-12/qluman-slurm-cli.py", line 66, in main slurm_acct = SlurmAcct(cf_file, dry_run=args.dryrun, reset_all_qos=args.reset_all_qos) File "/usr/lib/python3/dist-packages/qluman-12/components/slurm/cli.py", line 87, in __init__ self.get_slurm_ctl_info() File "/usr/lib/python3/dist-packages/qluman-12/components/slurm/cli.py", line 112, in get_slurm_ctl_info c = pyslurm.config() File "pyslurm/pyslurm.pyx", line 376, in pyslurm.pyslurm.config.__cinit__ File "pyslurm/pyslurm.pyx", line 432, in pyslurm.pyslurm.config.__load ValueError: ('Unable to contact slurm controller (connect failure)', 1800) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/qluman-12/qluman-slurm-cli.py", line 96, in <module> main() File "/usr/lib/python3/dist-packages/qluman-12/qluman-slurm-cli.py", line 69, in main sys.exit(1) NameError: name 'sys' is not defined" I delete the account and I recreate the same account. Qluman gives me a password and I can connect as a user. Or am I making a mistake thank you

2 1

users created with LDAP in QluMan can't connect to head node with ssh
by saeed.s.jahromi＠gmail.com 22 Feb '22

22 Feb '22

Greetings I have installed the qlustar on a small cluster with one head node and 15 compute nodes. I managed to add all nodes to the cluster and configure slurm on the cluster via QluMan. As the last step to make the cluster available to users, I started creating new groups and users with QluMan. after creating new users and syncing I tried to connect with users to the head node by ssh. However, all the users that I create can not connect to the head node because it says the user does not have premission. I also chose to create a virtual demo cluster during the installation and the demo user which is created during the installation also does not have permission to ssh login to the head node. I checked on the head node and all user's home directory is created in the /data/home/ directory but they can not connect to the cluster. I would be so thankful if you guide me on how should I resolve this issue or where in the qlustar config files should I look for the source of the problem. PS, this cluster was already using an older version of the qlustar from 6 years ago and we just updated it to the latest qlustar 12. Thanks in advance for your assistance. Saeed

3 5

AlmaLinux 8 substitutes CentOS 8
by Qlustar List 21 Feb '22

21 Feb '22

https://qlustar.com/news/2022/2022-02-21-almalinux-8

1 0

How to generate a image for tesla m2075 ?
by Gerhard W. Recher 21 Feb '22

21 Feb '22

Dear members, I just test transition from rocks cluster to qlustar. one point is our tesla m2075 nodes wont boot with nvidia driver due to not supportet by ubuntou-focal-nvidea. <snip> [ 60.417821] NVRM: The NVIDIA Tesla M2075 GPU installed in this system is NVRM: supported through the NVIDIA 390.xx Legacy drivers. Please NVRM: visit http://www.nvidia.com/object/unix.html for more NVRM: information. The 470.74 NVIDIA driver will ignore NVRM: this GPU. Continuing probe... [ 60.418062] NVRM: No NVIDIA GPU found. [ 60.418406] nvidia-nvlink: Unregistered the Nvlink Core, major device number 245 [ 65.107363] nvidia-nvlink: Nvlink Core is being initialized, major device number 245 <snap> so how can i achieve this on head-node to assemble a new boot image with older driver ? fail with this one: NVIDIA-Linux-x86_64-352.79.run nvidia-installer log file '/var/log/nvidia-installer.log' creation time: Sun Feb 20 13:33:54 2022 installer version: 352.79 PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin nvidia-installer command line: ./nvidia-installer Unable to load: nvidia-installer ncurses user interface Using built-in stream user interface -> Detected 4 CPUs online; setting concurrency level to 4. WARNING: You do not appear to have an NVIDIA GPU supported by the 352.79 NVIDIA Linux graphics driver installed in this system. For further details, please see the appendix SUPPORTED NVIDIA GRAPHICS CHIPS in the README available on the Linux driver download page at www.nvidia.com. -> License accepted. -> Installing NVIDIA driver version 352.79. -> Performing CC sanity check with CC="/usr/bin/cc". -> Kernel source path: '/lib/modules/5.4.167-ql-generic-12.0-13/build' -> Kernel output path: '/lib/modules/5.4.167-ql-generic-12.0-13/build' -> Performing rivafb check. -> Performing nvidiafb check. -> Performing Xen check. -> Performing PREEMPT_RT check. -> Cleaning kernel module build directory. executing: 'cd ./kernel; /usr/bin/make clean'... -> Building NVIDIA kernel module: executing: 'cd ./kernel; /usr/bin/make module SYSSRC=/lib/modules/5.4.167-ql-generic-12.0-13/build SYSOUT=/lib/modules/5.4.167-ql-generic-12.0-13/build -j4 NV_BUILD_MODULE_INSTANCES='... NVIDIA: calling KBUILD... make[1]: Entering directory '/usr/src/linux-headers-5.4.167-ql-generic-12.0-13' /usr/bin/make -f ./Makefile syncconfig /usr/bin/make -f ./scripts/Makefile.build obj=scripts/basic rm -f .tmp_quiet_recordmcount /usr/bin/make -f ./scripts/Makefile.build obj=scripts/kconfig syncconfig scripts/kconfig/conf --syncconfig Kconfig Kconfig:34: can't open file "Documentation/Kconfig" make[3]: *** [scripts/kconfig/Makefile:73: syncconfig] Error 1 make[2]: *** [Makefile:590: syncconfig] Error 2 make[1]: *** [Makefile:696: include/config/auto.conf.cmd] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.4.167-ql-generic-12.0-13' NVIDIA: left KBUILD. nvidia.ko failed to build! make: *** [nvidia-modules-common.mk:245: module] Error 1 -> Error. ERROR: Unable to build the NVIDIA kernel module. ERROR: Installation has failed. Please see the file '/var/log/nvidia-installer.log' for details. You may find suggestions on fixing installation problems in the README available on the Linux driver download page at www.nvidia.com. -- Gerhard W. Recher net4sec UG (haftungsbeschränkt) Leitenweg 6 86929 Penzing +49 8191 4283888 +49 171 4802507

1 0

tcsh segfault in Ubuntu 20.04 with external LDAP
by a.gabbana＠tue.nl 17 Feb '22

17 Feb '22

Dear Roland, we observe the following reproducible problem: - A fresh installation of qlustar 12 - A chroot with Ubuntu 20.04 - An external (fresh) ldap server (connection via shared conf files under /etc/qlustar/common/image-files) Calling tcsh returns segfault. The problem seems to be connected to libgssapi_krb5.so.2. The problem does not occur with a Ubuntu 18.04 chroot. Moreover, the problem does not occur with a fresh installation of Ubuntu 20.04 (without qlustar) connected to the same ldap Do you have any clue what could be triggering the problem / or can you suggest a possible workaround? best Alessandro

2 1

2025

2024

2023

2022

2021

2020

2019

2018

Qlustar General