Was difficult to reproduce this time. Took 15-20 tries. Once it happens, (almost?) every dispVM that is subsequently created experiences the issue.
tail -f /var/log/control-port-filter-python.log
On a working TBB,
New Identity results in:
CPFP log - DEBUG - Request: signal newnym
CPFP log - DEBUG - Answer: 250 OK
On a broken TBB, there is nothing logged after sending
While broken TBB is running, other TBB that send
New Identity also do not generate any output.
After closing offending TBB,
New Identity results in normal output for all TBB.
sudo service control-port-filter-python status
Status never changes.
I took one additional step. I monitored iptables for incoming packets and indeed,
New Identity on all TBB (working or broken) results in incrementing both:
REDIRECT tcp -- vif+ * 0.0.0.0/0 0.0.0.0/0 tcp dpt:9052 redir ports 9052
ACCEPT tcp -- vif+ * 0.0.0.0/0 0.0.0.0/0 tcp dpt:9052
So something is happening between iptables and cpfp in Gateway.
Is there a maximum number of control port connections?