SSHing into build VM a second time stalls then panics

I recently SSHed into a buildvm running Arch and tried to start a service (Docker). It stalled, so I attempted to create a second SSH connection so that I could tail the logs and see what was going on. The second session gives me the text about the VM terminating 4 hours from now, but then never gives me a shell. If I send a SIGINT and try to cancel connecting, it panics with:

^CTraceback (most recent call last):
  File "/usr/bin/buildsrht-shell", line 111, in <module>
    connect(job_id, info)
  File "/usr/bin/buildsrht-shell", line 77, in connect
    "build@localhost", "bash"
  File "/usr/lib/python3.7/subprocess.py", line 341, in call
    return p.wait(timeout=timeout)
  File "/usr/lib/python3.7/subprocess.py", line 1019, in wait
    return self._wait(timeout=timeout)
  File "/usr/lib/python3.7/subprocess.py", line 1653, in _wait
    (pid, sts) = self._try_wait(0)
  File "/usr/lib/python3.7/subprocess.py", line 1611, in _try_wait
    (pid, sts) = os.waitpid(self.pid, wait_flags)
Connection to azusa.runners.sr.ht closed.

If multiple connections aren't supported, I would expect it to tell me instead of panicing. If they are supported and the shell can't be launched because of my process eating file descriptors or some other thing that's my fault, I would still not expect to get a panic dumped to me.

Assigned to
a month ago
a month ago
No labels applied.