Comment 1 for bug 32330

I'm also suffering exactly the same error (although I wasn't able to successfully use xinetd to get around it). Could you post the xinetd configuration that you are using? Or is there some debugging I could help with to fix the bug?