Hub stuck in tight loop

Discussion created by david.pippenger on Feb 20, 2010
Latest reply on Feb 25, 2010 by keith_k

We seem to have encountered a situation where the hub has gotten itself into a tight loop. I'm not sure what caused it, but looking at traces of the hub itself reveal that it's repeatedly attempting to perform a select() on a list of FD and at least one is bad. Where bad means the FD no longer maps to an open FD as indicated by the select call returning an EBADF. The recommended course of action in these cases is to break out of the select loop and test the FD in the list so you can weed out the bad one(s). Like I said, no idea how we are getting into this error condition, but here is a strace of the hub. Search for EBADF and you can see where the fun starts.

I'm hoping Carstien is out there :smileyhappy: We have been having bad luck going through support on this one and a large chunk of our hub infrastructure is crippled right now as a result.