Comment 4 for bug 727148

Did the start of this problem coincide with the introduction of haproxy?
Is it possible that it's doing something strange that's causing the port to sometimes not be listening, or perhaps only on a specific ip that's not reached by the route from lillypilly?