- 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

[Qlustar-General] IMPI
by ignas.bunikis＠scilifelab.uu.se 05 Sep '18

05 Sep '18

Hej, How to correctly set up IMPI? I guess this one is a bit more tricky to trouble shoot, but here's what I have: * IMPI network was set up during installation; * cabling done; * anything to check in BIOS? * following QluMan guide "3.7. IPMI settings" I set "Initialize IPMI: true" in "Generic Property Set" assigned to nodes; * nodes "Hardware Property Set" has "IPMI Adapter: true"; Rebooted everything, started "console-login", but see only headnode. What did I miss? Cheers, Iggy

2 3

[Qlustar-General] SGE
by ignas.bunikis＠scilifelab.uu.se 05 Sep '18

05 Sep '18

Hej, I would like to set up SGE on freshly installed cluster. Could you please briefly describe necessary steps. Cheers, Iggy

2 2

[Qlustar-General] Open file limit
by ignas.bunikis＠scilifelab.uu.se 05 Sep '18

05 Sep '18

Hej, I need to increase Open file limit on the nodes. Should I use customized "limits.conf" and follow admin guide "4.2.5. Adding directories, files, links"? cat /etc/qlustar/common/image-files/my/limits.conf * soft nproc 10024 * hard nproc 10024 * soft nofile 50024 * hard nofile 50024 * soft memlock 255707144 * hard memlock 255707144 cat /etc/qlustar/common/image-files/destinations my/limits.conf /etc/security root:root 644 Is that a good way? Cheers, Iggy

2 2

[Qlustar-General] limit network access
by ignas.bunikis＠scilifelab.uu.se 05 Sep '18

05 Sep '18

Hej, I would like to limit access to the cluster via hosts.allow and hosts.deny. What is the best way to do it? I could create a script in /etc/qlustar/common/rc.boot/ that looks like this: #!/bin/bash echo 'sshd: ALL' >> /etc/hosts.deny echo 'sshd: localhost' >> /etc/hosts.allow echo 'sshd: xxx.xxx.xxx.xxx' >> /etc/hosts.allow Is that ok? Cheers, Iggy

2 2

[Qlustar-General] QluMan & Hardware Property Sets
by Ansgar Esztermann-Kirchner 30 Aug '18

30 Aug '18

Hello List, here's a question that cropped up during my search for HW Threads (see other message), but is actually unrelated: how do I edit HW property sets? If I use the pop-up menu to, say, change the number of cores from 10 to 20, the change reverts upon closing the property sets window. The context menu of the property has "Delete Property", but that has no effect; the context menu of the property set has "Edit Property Set", but that pertains only to the set's name and description, not the contained properties. Any ideas? Thanks a lot, A. -- Ansgar Esztermann Sysadmin http://www.mpibpc.mpg.de/grubmueller/esztermann

3 6

[Qlustar-General] HW Threads/Hyperthreading
by Ansgar Esztermann-Kirchner 24 Aug '18

24 Aug '18

Hello List, does Qlustar handle hardware threads? SLURM has the triple sockets/cores/threads, so I'd expect to be able to configure this somewhere. However, I couldn't find anything in the docs (or in QluMan). A. -- Ansgar Esztermann Sysadmin http://www.mpibpc.mpg.de/grubmueller/esztermann

2 3

[Qlustar-General] installing Qluman on workstation
by xyzemail19＠gmail.com 09 Jul '18

09 Jul '18

Reinstalling Qluman interface on my VM Virtualbox workstation. All worked fine then I needed to reload Virtualbox. Did a clean install on Ubuntu 16.04 and I received the following error message will trying to access the public 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:~# 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

2 8

[Qlustar-General] Re: Qluman questions
by goswin-v-b＠web.de 30 May '18

30 May '18

2 1

[Qlustar-General] Qluman questions
by Ansgar Esztermann-Kirchner 29 May '18

29 May '18

Hello List, a couple of question regarding Qluman: -As far as I understand the docs, the hierarchy for nodes is supposed to be host < enclosure < rack. Putting a node inside an enclosure can be done easily via the node's enclosure pop-up, but I have been unable to put the enclosure inside the rack. The only method I did find (drag and drop inside the tree view) lead to an error: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/qluman-10/client/qt/TreeWidget.py", line 980, in dropEvent updates[slot.id] = {"child_enclosure_id": w.id} AttributeError: 'int' object has no attribute 'id' -How do I define rack types? We have 42U racks without any special slots, and 47U racks with a couple of special slots, and neither is present in Qluman by default. -How do I diagnose hardware mismatch problems? In the right hand pane of the Enclosure View, my test node shows a red wrench with tool tip "Hardware config doesn't match host". The wrench is shown on a clickable button, but when I click it, nothing happens. I couldn't find anything in the menus, either. A. -- Ansgar Esztermann Sysadmin http://www.mpibpc.mpg.de/grubmueller/esztermann

1 0

[Qlustar-General] When/How is slurm.conf generated
by Ansgar Esztermann-Kirchner 28 May '18

28 May '18

Hello List, next question: how is slurm.conf generated? On my fresh installation, slurmctld won't start, and there are no NodeName entries in slurm.conf except for "DEFAULT". I've added a dummy node via qluman in order to test general slurm functionality, but it doesn't appear in slurm.conf. Am I missing something? Do I need to boot the node in order for it to appear in the config? Thanks, A. -- Ansgar Esztermann Sysadmin http://www.mpibpc.mpg.de/grubmueller/esztermann

2 3

[Qlustar-General] Unable to generate one-time token
by Ansgar Esztermann-Kirchner 24 May '18

24 May '18

Hello List, after installing Qlustar 10, I've tried to connect to the cluster via the GUI. However, I am unable to generate the necessary token: # qluman-cli --gencert -o cert ERROR:client.cli.network:client.cli.network.Cluster.__init__(): could not connect to server Error: No such user: 'admin' ERROR:qlunet4.Node:Channel[('zmq_version_info', 1)].do_recv(): exception in request generator Traceback (most recent call last): File "/usr/lib/python3/dist-packages/qluman-10/qluman-cli.py", line 1274, in gencert db.users.lookup(field="name", val=user) File "/usr/lib/python3/dist-packages/qluman-10/common/types.py", line 1678, in lookup raise KeyError KeyError Checking the logs, there seems to be something wrong with qlumand and/or its database (see below). Any ideas? Thanks a lot, A. syslog excerpt: May 9 15:03:52 cl-head systemd[1]: qluman-server.service: Service hold-off time over, scheduling restart. May 9 15:03:52 cl-head systemd[1]: Stopped Qlustar Management server. May 9 15:03:52 cl-head systemd[1]: Started Qlustar Management server. May 9 15:03:52 cl-head qlumand[4428]: 2018-05-09 15:03:52,718 [4429] INFO#011__main__ May 9 15:03:52 cl-head qlumand[4428]: - Starting Qluman main server: qlumand. May 9 15:03:52 cl-head qlumand[4428]: 2018-05-09 15:03:52,719 [4429] INFO#011server.admin May 9 15:03:52 cl-head qlumand[4428]: - Qlumand running with address beosrv-c / external cl-head May 9 15:03:52 cl-head qlumand[4428]: 2018-05-09 15:03:52,823 [4429] INFO#011server.db.DBData May 9 15:03:52 cl-head qlumand[4428]: - DbVersion = 10.0.0 [expected 10.0.1] May 9 15:03:52 cl-head qlumand[4428]: 2018-05-09 15:03:52,824 [4429] ERROR#011server.db.DBData#011 Probably already have column: May 9 15:03:52 cl-head qlumand[4428]: Traceback (most recent call last): May 9 15:03:52 cl-head qlumand[4428]: File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1139, in _execute_context May 9 15:03:52 cl-head qlumand[4428]: context) May 9 15:03:52 cl-head qlumand[4428]: File "/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py", line 450, in do_execute May 9 15:03:52 cl-head qlumand[4428]: cursor.execute(statement, parameters) May 9 15:03:52 cl-head qlumand[4428]: File "/usr/lib/python3/dist-packages/mysql/connector/cursor.py", line 507, in execute May 9 15:03:52 cl-head qlumand[4428]: self._handle_result(self._connection.cmd_query(stmt)) May 9 15:03:52 cl-head qlumand[4428]: File "/usr/lib/python3/dist-packages/mysql/connector/connection.py", line 722, in cmd_query May 9 15:03:52 cl-head qlumand[4428]: result = self._handle_result(self._send_cmd(ServerCmd.QUERY, query)) May 9 15:03:52 cl-head qlumand[4428]: File "/usr/lib/python3/dist-packages/mysql/connector/connection.py", line 640, in _handle_result May 9 15:03:52 cl-head qlumand[4428]: raise errors.get_exception(packet) May 9 15:03:52 cl-head qlumand[4428]: mysql.connector.errors.ProgrammingError: 1060 (42S21): Duplicate column name 'net_config_name_id' May 9 15:03:52 cl-head qlumand[4428]: The above exception was the direct cause of the following exception: May 9 15:03:52 cl-head qlumand[4428]: Traceback (most recent call last): May 9 15:03:52 cl-head qlumand[4428]: File "/usr/lib/python3/dist-packages/qluman-10/server/db/DBData.py", line 190, in add_column May 9 15:03:52 cl-head qlumand[4428]: engine.execute("ALTER TABLE {0} ADD COLUMN {1} {2} NOT NULL DEFAULT '{3}'".format(table_name, column_name, column_type, default)) May 9 15:03:52 cl-head qlumand[4428]: File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1991, in execute May 9 15:03:52 cl-head qlumand[4428]: return connection.execute(statement, *multiparams, **params) May 9 15:03:52 cl-head qlumand[4428]: File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 906, in execute May 9 15:03:52 cl-head qlumand[4428]: return self._execute_text(object, multiparams, params) May 9 15:03:52 cl-head qlumand[4428]: File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1054, in _execute_text May 9 15:03:52 cl-head qlumand[4428]: statement, parameters May 9 15:03:52 cl-head qlumand[4428]: File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1146, in _execute_context May 9 15:03:52 cl-head qlumand[4428]: context) May 9 15:03:52 cl-head qlumand[4428]: File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1341, in _handle_dbapi_exception May 9 15:03:52 cl-head qlumand[4428]: exc_info May 9 15:03:52 cl-head qlumand[4428]: File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 189, in raise_from_cause May 9 15:03:52 cl-head qlumand[4428]: reraise(type(exception), exception, tb=exc_tb, cause=exc_value) May 9 15:03:52 cl-head qlumand[4428]: File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 182, in reraise May 9 15:03:52 cl-head qlumand[4428]: raise value.with_traceback(tb) May 9 15:03:52 cl-head qlumand[4428]: File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1139, in _execute_context May 9 15:03:52 cl-head qlumand[4428]: context) May 9 15:03:52 cl-head qlumand[4428]: File "/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py", line 450, in do_execute May 9 15:03:52 cl-head qlumand[4428]: cursor.execute(statement, parameters) May 9 15:03:52 cl-head qlumand[4428]: File "/usr/lib/python3/dist-packages/mysql/connector/cursor.py", line 507, in execute May 9 15:03:52 cl-head qlumand[4428]: self._handle_result(self._connection.cmd_query(stmt)) May 9 15:03:52 cl-head qlumand[4428]: File "/usr/lib/python3/dist-packages/mysql/connector/connection.py", line 722, in cmd_query May 9 15:03:52 cl-head qlumand[4428]: result = self._handle_result(self._send_cmd(ServerCmd.QUERY, query)) May 9 15:03:52 cl-head qlumand[4428]: File "/usr/lib/python3/dist-packages/mysql/connector/connection.py", line 640, in _handle_result May 9 15:03:52 cl-head qlumand[4428]: raise errors.get_exception(packet) May 9 15:03:52 cl-head qlumand[4428]: sqlalchemy.exc.ProgrammingError: (mysql.connector.errors.ProgrammingError) 1060 (42S21): Duplicate column name 'net_config_name_id' [SQL: "ALTER TABLE Nic2NicProps ADD COLUMN net_config_name_id INTEGER UNSIGNED NOT NULL DEFAULT '1'"] May 9 15:03:52 cl-head qlumand[4428]: 2018-05-09 15:03:52,835 [4429] ERROR#011server.db.DBData#011Don't know how to update database format 10.0.0 to 10.0.1 May 9 15:03:52 cl-head qlumand[4428]: Traceback (most recent call last): May 9 15:03:52 cl-head qlumand[4428]: File "/usr/lib/python3/dist-packages/qluman-10/server/db/DBData.py", line 369, in __init__ May 9 15:03:52 cl-head qlumand[4428]: self.sess = db_updates[db_version.params](self.DB, self.sess, global_props) May 9 15:03:52 cl-head qlumand[4428]: File "/usr/lib/python3/dist-packages/qluman-10/server/db/DBData.py", line 337, in db_update_10_0_0 May 9 15:03:52 cl-head qlumand[4428]: db_set_version(global_props, "10.0.1") May 9 15:03:52 cl-head qlumand[4428]: File "/usr/lib/python3/dist-packages/qluman-10/server/db/DBData.py", line 174, in db_set_version May 9 15:03:52 cl-head qlumand[4428]: entry = global_props.lookup(field="name", val="DbVersion") May 9 15:03:52 cl-head qlumand[4428]: File "/usr/lib/python3/dist-packages/qluman-10/common/types.py", line 1678, in lookup May 9 15:03:52 cl-head qlumand[4428]: raise KeyError May 9 15:03:52 cl-head qlumand[4428]: KeyError -- Ansgar Esztermann Sysadmin http://www.mpibpc.mpg.de/grubmueller/esztermann

2 9

[Qlustar-General] PXE boot
by Bob Johnson 02 May '18

02 May '18

The nodes will not PXE boot. I see the standard install loads the Realtek r8169 driver. Based on past experience, my hardware requires the r8168 driver. Can the NIC driver be changed in qlustar? Do I execute the following commands at the root@cl-head~# prompt. Or from a different location? apt-get install r8168 -dkms rmmod r8169 lspci -s 3:00.0 -vv (verifies the r8168 driver is loaded) reboot thanks

3 5

[Qlustar-General] Install questions - #2
by Bob Johnson 23 Apr '18

23 Apr '18

Reviewing my notes from a few years ago, it appears that I am having some of the same issues with loading Slurm and creating a chroot file during the FAI install Do I need to preload anything before the Qlustar install? Thanks

2 1

[Qlustar-General] Qlustar 10.0 install issues
by Bob Johnson 23 Apr '18

23 Apr '18

Having a few issues during the initial install of Qlustar. - Started with a clean install of Qlustar. - All was going well and then the error "failed to start rng-tools.service." - The installed continued on its own to the "Welcome to Qlustar 10..... " screen. - At the root@cl-head~# prompt I entered /usr/sbin/qlustar-inital-config command. - Next error message encountered was during the gluman bootstrap - couldn't determine IP address.... Install continued to the configure slurmbd section - Entered my slurm password twice and and I receive this error after several minutes of waiting - "sacctmgr: Can't connect do slurmbd - exiting" Any thoughts?

2 1

[Qlustar-general] Welcome to the Qlustar mailing list
by Roland Fehrenbacher 06 Mar '18

06 Mar '18

Dear Qlustar users, we're moving discussions about Qlustar from our forum on qlustar.com to this mailing list. Please note that the list allows posting only for list members. Until there is a need for more, this will be the only mailing list about Qlustar. And please respect common mailing list netiquette rules like described at https://en.opensuse.org/openSUSE:Mailing_list_netiquette e.g. Looking forward to many interesting posts, Roland

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

Qlustar General