this happens from time to time and only requires us to reboot the offending front end server. I did a reboot yesterday anyway which may have already fixed it. if not lmk asap.