...bump...On Fri, May 2, 2014 at 6:47 AM, Keith Brown <keith6014@xxxxxxxxx> wrote:
i don't believe this is a permission issue because the job actually executes fine and runs for hours and then suddenly I see "CEDAR:6001:Failed to connect to ..."Âi am at a loss here.ÂOn Wed, Apr 30, 2014 at 6:48 AM, Keith Brown <keith6014@xxxxxxxxx> wrote:
has anyone seen this?On Tue, Apr 29, 2014 at 7:02 AM, Keith Brown <keith6014@xxxxxxxxx> wrote:
On a large pool I noticed several of my job are keep getting rescheduled.ÂBy looking at the ShadowLog I noticed,ÂSock::bind failed: errno = 98 Address already in useRemoteResource::killStarter(): Could not send command to startdSock::bind failed: errno = 98 Address already in useCan't connect to queue manager: CEDAR:6001:Failed to connect to <scheduler>Failed to perform final update to job queue!By checking the mailing list, I have these settings:NO_DNS = falseAnything I should be looking at?Â