[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] schedd keeps dying
- Date: Fri, 02 Dec 2011 15:30:59 -0500
- From: Sarah Williams <saewill@xxxxxxxxx>
- Subject: Re: [Condor-users] schedd keeps dying
UPDATE_COLLECTOR_WITH_TCP, HIGHPORT and LOWPORT are not set. As I
understand it, the default it to use TCP, and an unlimited number of
ports, is that right? I grepped ShadowLog for 'port' ( case insensitive
), and didn't see anything. In case it was a memory issue, I assigned
the KVM more RAM and rebooted. Schedd died once on startup, but it
staying up since then.
On 12/2/11 2:55 PM, Steven Timm wrote:
> Sarah, do you use the HIGHPORT and LOWPORT settings
> in the condor config file?
> You need 2 ports available for every condor_shadow process
> that is running. Also are you using udp or tcp to update
> the collector? The error in question is consistent
> with running out of ports. ShadowLog will tell you something
> about that too if your debug level is high enough.
> Steve Timm
> On Fri, 2 Dec 2011, Sarah Williams wrote:
>> Hi Condor users and experts,
>> I'm seeing my condor_schedd die repeatedly with the stack trace below.
>> I've put the core file up at:
>> The installation was stable previously at ~1000 cores, but because
>> unstable when increased to 4000 cores.
>> Stack dump for process 24238 at timestamp 1322852851 (22 frames)
>> Condor-users mailing list
>> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
>> subject: Unsubscribe
>> You can also unsubscribe by visiting
>> The archives can be found at: