Jeff Geerling

For comparison, my files: ``` # Inside /opt/top500/tmp/hpl-2.3/bin/top500/cluster-hosts 10.0.2.21:192 # Inside /etc/hosts 127.0.0.1 localhost 127.0.1.1 ubuntu # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0...

Another idea, since you have Hyperthreading... can you modify `/opt/top500/tmp/hpl-2.3/bin/top500/cluster-hosts` and change the 512 to 256 and try again running the manual command?

It sounds like my script needs a little updating, specifically the `hostvars[host].ansible_processor_vcpus` is incorporating threads, not cores, resulting in the errant `512` parameter in your `cluster-hosts` file. https://github.com/geerlingguy/top500-benchmark/blob/53ae3f35f2cb1c7f00f9b948ceae082fadf01560/templates/mpi-node-config.j2#L2 I'll look...

Opened a follow-up issue: https://github.com/geerlingguy/top500-benchmark/issues/46 For now, we can just act like Ansible doesn't exist anymore and run the command manually :)

So this is during the initial connection? Or is it happening during a specific task or when you hit the 'Run the benchmark" task?

@jere19 Ah... sometimes on first connection, Ansible gets picky about that — I usually sit there and enter "yes" and hit "return" a bunch of times if I see that...

Definitely would like to get this fixed up. If I forget about this please ping me ;)

@tonistiigi - In a downstream issue where I was finding this same behavior on Docker for Mac, I added a `/var/lib/mysql` volume and the error went away. (See https://github.com/geerlingguy/drupal-vm/issues/1497). That's...

Yes, unfortunately. See: https://www.jeffgeerling.com/blog/2020/enabling-stale-issue-bot-on-my-github-repositories

Thanks! I will take a look at this soon, hopefully—I actually just upgraded my own Drupal VPS and had to make a few similar modifications, but in a different playbook.