Qlustar General

Download

qlustar-general@qlustar.org

November 2021

3 participants
2 discussions

Stack Smashing Detected During qlustar-image-reconfigure
by hereiam＠mit.edu 25 Nov '21

25 Nov '21

Hi everyone, I've got a new one for you all... I was updating my chroot image successfully using qlustar-image-reconfigure, and all was well. However, when I updated qlustar using apt-get upgrade as usual (I haven't done so since July), now I get this error whenever I try to reconfigure the chroot image: 0 root@geb /var/lib/qlustar/images/Standard-focal # qlustar-image-reconfigure Standard-focal Reconfiguring image Standard-focal focal/12.0 - creating squashfs for download using kernel flavour ql-generic-* *** stack smashing detected ***: terminated /usr/sbin/qlustar-image-create: line 661: 8766 Aborted DEBIAN_FRONTEND=noninteractive chroot "$IMAGE_DIR" pam-auth-update --package --force Building image Standard-focal focal/12.0 failed. Any idea what might have happened? I'm all ears, and can't seem to figure it out on my own. Thanks! -Mike

1 0

[Qlustar-General] Node Replacement Issue - Infinite DNSMasq Lease in /var/lib/misc/dnsmasq.leases
by hereiam＠mit.edu 25 Nov '21

25 Nov '21

Hi everyone, I've run into what may be an uncommon issue when replacing nodes in Qluman. Say I have a node all configured, then I completely remove that machine and replace it with a new one (may or may not be different specs). I have noticed that Qluman allows one to make the new node in the configs, but it never boots Qlustar. I also found the fix - the file /var/lib/misc/dnsmasq.leases doesn't appear to get updated *only when deleting a node.* Adding new nodes works perfectly, as does changing MAC addresses. However, I've had to go in and manually delete the corresponding entries from the file on the headnode, after which Qluman works perfectly adding a New Host with the old IP address. Can anyone else reproduce this issue, and if so, would an addition to the scripts to the tune of deleting the line matching the hostname or MAC address in /var/lib/misc/dnsmasq.leases be required for the next round of updates? It makes sense that leases should have infinite lifetime in a cluster (nodes should sit tight for years), though in this rare situation it requires a bit of extra manual tweaking. Thanks, -Mike

4 5