Doug Holt
Doug Holt
I see this same issue immediately after launching @fauria's container with no user access
This is all I get; the error block is repeated in an infinite loop enough to peg the CPU core: ``` load items: ready to serve port 8080 char-whitespace?: contract...
I'm launching via Ansible: ``` --- - name: hackernews | launch container docker: name: "hackernews" hostname: "example.com" image: "fauria/hn" state: reloaded restart_policy: always ports: - "80:8080" volumes: - "/mnt/hackernews/static:/anarki/static" -...
I'm running into this same issue with UEFI clients. I've tried setting options 66/67 in my isc-dhcp-server config (which I think is what's happening in @wrouesnel's dnsmasq example) but still...
Thanks Dave- unfortunately I'm stuck with UEFI due to install media. I'm running into this on brand-new Supermicro and Quanta systems so it's not isolated to HP. I can give...
you can manually run `systemctl unmask nvidia-persistenced` and re-run the role
This is just for an HTTPS proxy. I can still make the connection and join the room, but whatever is different about fetching updates from the live stream is not...
try manually running the memory fact gathering script to see if it produces unexpected output: ``` bash roles/facts/files/memory.fact ```
does it work if you comment out the `memory` variable in your `hostvars` file?
In that case if you just want to work around it, you could comment out the lines in `slurm.conf` that reference `memory.total_mb`. I haven't been able to reproduce this issue,...