Join GitHub today
rare quads-daemon traceback #188
Very rarely (but now twice over the past year) we see this pop up, restarting the daemon "fixes" it. I'm not sure what's causing it but it seems load / connection related.
After some investigation there was nothing wrong with the code nor anything evident in the tcpdumps taken.
This seemed to be system related, we had prior XFS corruption on the hypervisor as well as CPU soft lockup on the VM which was most likely contributing to the timeouts experienced (and subsequent tracebacks). I am closing this now but we can re-open.