- Qlustar General - Qlustar Mailing Lists

[Qlustar-General] Ganglia stop monitoring compute nodes, qlustar 10.1
by kwinten.nelissen＠gmail.com 15 Jan '19

15 Jan '19

Dear, Ganglia stops monitoring the compute nodes after a couple minutes after restart of the service. However the head node is monitored fine. Has anyone an idea what can cause this. There is nothing reported in the error logs what so ever. Thanks for help. Best regards, Kwinten

2 3

[Qlustar-General] Alternative to NTP?
by clavila＠gmail.com 09 Jan '19

09 Jan '19

Dear all, I was wondering if there is an alternative to using NTP to synchronize the clock. I am behind a proxy firewall and I cannot access NTP servers on the internet. Cheers, Cesar

2 1

[Qlustar-General] Add edge platform without QluMan Qt?
by Hernán Morales Durand 18 Dec '18

18 Dec '18

Hi, Inadvertently during installation I chose CentOS 7 as my edge platform and installing the QluMan GUI proves to be difficult on CentOS 7 due to missing Qt dependencies. Now I am stuck trying to install an alternative platform: root@plato:~ # schroot -l chroot:centos7 root@plato:~ # chroot-centos7 (centos7) root@plato:~ # yum update yum install qt-10 qt5-qtbase-devel mesa-libGL-devel mesa-libGLU-devel yum install qluman-qt Loaded plugins: keys, post-transaction-actions, protectbase 0 packages excluded due to repository protections Resolving Dependencies --> Running transaction check ---> Package qluman-qt.noarch 0:10.1.0.37-1.ql.el7 will be installed --> Processing Dependency: qt-10 = 10.1.0.37-1.ql.el7 for package: qluman-qt-10.1.0.37-1.ql.el7.noarch --> Finished Dependency Resolution Error: Package: qluman-qt-10.1.0.37-1.ql.el7.noarch (qlustar-10.1) Requires: qt-10 = 10.1.0.37-1.ql.el7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest I couldn't find how to install additional edge platform for my chroot environment **without** requiring QluMan, in the documentation : https://www.qlustar.com/book/docs/install-guide : "Note that you can always add support for a previously unselected edge platform later on by creating corresponding chroots and Qlustar images using QluMan." Is there an alternative way to add a platofrm without requiring the QluMan GUI? Is better to re-run the initial config again? /usr/sbin/qlustar-initial-config Best regards, Hernán

2 3

[Qlustar-General] Unsigned repository (NO_PUBKEY)
by Hernán Morales Durand 18 Dec '18

18 Dec '18

Hi, Trying to install qluman-qt on a clean (recently installed) Debian 9.2 workstation: # dpkg -l | grep python-software-properties > /dev/null 2>&1 || apt-get install python3-software-properties # apt-get install software-properties-common # add-apt-repository 'deb http://repo.qlustar.com/repo/qluman 9.2-wheezy-proposed-updates main non-free' # add-apt-repository 'deb http://repo.qlustar.com/repo/qluman 9.2-wheezy main non-free' Problems start here : # apt-get update Ign:1 http://ftp.ccc.uba.ar/pub/linux/debian/debian stretch InRelease Des:2 http://ftp.ccc.uba.ar/pub/linux/debian/debian stretch-updates InRelease [91,0 kB] Des:3 http://ftp.ccc.uba.ar/pub/linux/debian/debian stretch Release [118 kB] Obj:4 http://security.debian.org/debian-security stretch/updates InRelease Des:6 http://repo.qlustar.com/repo/qluman 9.2-wheezy-proposed-updates InRelease [9.567 B] Ign:6 http://repo.qlustar.com/repo/qluman 9.2-wheezy-proposed-updates InRelease Des:7 http://repo.qlustar.com/repo/qluman 9.2-wheezy InRelease [9.548 B] Ign:7 http://repo.qlustar.com/repo/qluman 9.2-wheezy InRelease Des:8 http://repo.qlustar.com/repo/qluman 9.2-wheezy-proposed-updates/main amd64 Packages [2.653 B] Des:9 http://repo.qlustar.com/repo/qluman 9.2-wheezy-proposed-updates/non-free amd64 Packages [2.779 B] Des:10 http://repo.qlustar.com/repo/qluman 9.2-wheezy/main amd64 Packages [7.888 B] Des:11 http://repo.qlustar.com/repo/qluman 9.2-wheezy/non-free amd64 Packages [2.094 B] Descargados 244 kB en 2s (103 kB/s) Leyendo lista de paquetes... Hecho W: Error de GPG: http://repo.qlustar.com/repo/qluman 9.2-wheezy-proposed-updates InRelease: Las firmas siguientes no se pudieron verificar porque su clave pública no está disponible: NO_PUBKEY E6BA110F3C0BC307 W: El repositorio «http://repo.qlustar.com/repo/qluman 9.2-wheezy-proposed-updates InRelease» no está firmado. N: Los datos de un repositorio como este no se pueden autenticar y por tanto su uso es potencialmente peligroso. N: Vea la página de manual apt-secure(8) para los detalles sobre la creación de repositorios y la configuración de usuarios. W: Error de GPG: http://repo.qlustar.com/repo/qluman 9.2-wheezy InRelease: Las firmas siguientes no se pudieron verificar porque su clave pública no está disponible: NO_PUBKEY E6BA110F3C0BC307 W: El repositorio «http://repo.qlustar.com/repo/qluman 9.2-wheezy InRelease» no está firmado. N: Los datos de un repositorio como este no se pueden autenticar y por tanto su uso es potencialmente peligroso. N: Vea la página de manual apt-secure(8) para los detalles sobre la creación de repositorios y la configuración de usuarios. # apt-get install qluman-qt Leyendo lista de paquetes... Hecho Creando árbol de dependencias Leyendo la información de estado... Hecho No se pudieron instalar algunos paquetes. Esto puede significar que usted pidió una situación imposible o, si está usando la distribución inestable, que algunos paquetes necesarios aún no se han creado o se han sacado de «Incoming». La siguiente información puede ayudar a resolver la situación: Los siguientes paquetes tienen dependencias incumplidas: qluman-qt : Depende: qluman-qt-3 pero no va a instalarse E: No se pudieron corregir los problemas, usted ha retenido paquetes rotos. It seems qlustar repository cannot be authenticated. Are there any additional steps to configure? Should I self-sign the qlustar repository? Cheers, Hernán

2 1

[Qlustar-General] API
by Ansgar Esztermann-Kirchner 10 Dec '18

10 Dec '18

Hello List, there's a few areas of configuration where we'd welcome more automation (e.g. creating a lot of nodes). Therefore, I'd like to develop some tools that interface with the central daemon. Is there any API documentation available? Thanks, A. -- Ansgar Esztermann Sysadmin http://www.mpibpc.mpg.de/grubmueller/esztermann

2 5

[Qlustar-General] Hardware config incomplete
by Ansgar Esztermann-Kirchner 03 Dec '18

03 Dec '18

Hello List, I've just added a few nodes to the cluster, and they're marked with the empty wrench icon "Hardware config incomplete". How do I find out what's missing? Thanks, A. -- Ansgar Esztermann Sysadmin http://www.mpibpc.mpg.de/grubmueller/esztermann

2 1

[Qlustar-General] Kernel panic - not syncing: Attempted to kill init! exit code=0x00000100
by Hernán Morales Durand 27 Nov '18

27 Nov '18

Hello, Tyring a new installation here from USB using the current installer https://www.qlustar.com/sites/default/files/downloads/qlustar-installer-10.… My server started to boot correctly, however a kernel panic happened. You can view kernel dump details here: https://imgur.com/a/7jSCHuJ I tried to make a memory area for the kdump kernel with crashkernel and debug parameters, however I don't know if it is possible to export the kernel dump. Any hints? Cheers, Hernán

3 3

[Qlustar-General] can not retrive Qlustar PGP archive key
by Lloyd Jennings 26 Nov '18

26 Nov '18

Qlustar 10.1 can not find key. root@workstation:~# dpkg -l software-properties-common > /dev/null 2>&1 || apt install software-properties-common root@workstation:~# gpg --no-default-keyring --primary-keyring /etc/apt/trusted.gpg --recv-keys E6BA110F3C0BC307 gpg: no keyserver known (use option --keyserver) gpg: keyserver receive failed: bad URI root@workstation:~#

2 1

[Qlustar-General] qlustar 10.1: chroot-xenial doesnt sync /var/lib
by kwinten.nelissen＠gmail.com 18 Oct '18

18 Oct '18

Hi, I am testing singularity and I encountered the problem that /var/lib is not synchronized with the chroot environment at the node. I am looking now into the unionfs -fuse of the init.qlustar script but I can not find any problem here. Is there a configuration file somewhere for the chroot environment? Best regards, Kwinten

2 7

[Qlustar-General] Slurm failed to detect properly CPU-cores and RAM when adding new nodes.
by kwinten.nelissen＠gmail.com 15 Oct '18

15 Oct '18

Hi, Something went from when adding new nodes. The configuration file was somehow not fully written. So I wrote them again and restarted the slurm on all nodes. All nodes were affected but the problem seems to be resolved now. The Error read as follows: K> 2018-10-10T09:14:43.306] error: _slurm_rpc_node_registration K> node=beo-02: Invalid argument [2018-10-10T09:14:43.306] error: K> Node beo-01 appears to have a different slurm.conf than the K> slurmctld. This could cause issues with communication and K> functionality. Please review both files and make sure they are K> the same. If this is expected ignore, and set K> DebugFlags=NO_CONF_HASH in your slurm.conf. K> [2018-10-10T09:14:43.306] error: Node beo-01 has low K> socket*core*thread count (16 < 32) [2018-10-10T09:14:43.306] K> error: Node beo-01 has low cpu count (16 < 32) K> [2018-10-10T09:14:43.306] error: _slurm_rpc_node_registration K> node=beo-01: Invalid argument Moreover it seems when a node is added, at the first boot time slurm detect the RAM, etc wrongly. This can be resolved by simply restarting slurm at the new added node. Perhaps the update would indeed resolve this issue. Best regards, Kwinten

2 1

2024

2023

2022

2021

2020

2019

2018

Qlustar General