LIGO Support Ticket 2237
Ticket Information
Number: support 2237
User: dabrown@physics.syr.edu
Email: anderson__AT__ligo.caltech.edu,skoranda__AT__gravity.phys.uwm.edu
Status: resolved
Assigned To: gthain
CC: Stuart Anderson <anderson__AT__ligo.caltech.edu>, Scott Koranda
<skoranda__AT__gravity.phys.uwm.edu>
From: Duncan Brown <dabrown__AT__physics.syr.edu>
Subject: LIGO: condor_schedd exited (4)
Date: Mon, 28 Apr 2008 11:22:22 -0400
To: condor-support response tracking system <condor-support__AT__cs.wisc.edu>
X-Scanner: InterScan AntiVirus for Sendmail
X-Seen-BY: mailfromd 4.1 obsidian.cs.wisc.edu
Hi all,
This weekend I has 4 schedd exits, all with the error message
Assertion ERROR on (mrec->request_claim_sock == sock)" at line 1361
in file dedicated_scheduler.C
Has anyone seen this before? Log is attached.
Cheers,
Duncan.
Begin forwarded message:
> From: Condor <condor__AT__sugar-dev1.phy.syr.edu>
> Date: April 27, 2008 1:50:40 AM EDT
> To: dabrown__AT__physics.syr.edu
> Subject: [Condor] Problem sugar-dev1.phy.syr.edu: condor_schedd
> exited (4)
>
> This is an automated email from the Condor system
> on machine "sugar-dev1.phy.syr.edu". Do not reply.
>
> "/usr/sbin/condor_schedd" on "sugar-dev1.phy.syr.edu" exited with
> status 4.
> Condor will automatically restart this process in 17 seconds.
>
> *** Last 20 line(s) of file /usr1/condor/log/SchedLog:
> 4/27 01:50:33 (pid:16491) Return from Handler <to startd
> <10.20.2.61:41326>>
> 4/27 01:50:33 (pid:16491) Calling Handler <to startd
> <10.20.2.61:41326>>
> 4/27 01:50:33 (pid:16491) Response problem from startd on #...
> (match #...).
> 4/27 01:50:33 (pid:16491) Return from Handler <to startd
> <10.20.2.61:41326>>
> 4/27 01:50:33 (pid:16491) Calling Handler <to startd
> <10.20.2.61:41326>>
> 4/27 01:50:33 (pid:16491) Response problem from startd on #...
> (match #...).
> 4/27 01:50:33 (pid:16491) Return from Handler <to startd
> <10.20.2.61:41326>>
> 4/27 01:50:33 (pid:16491) Calling Handler <to startd
> <10.20.2.61:41326>>
> 4/27 01:50:33 (pid:16491) Response problem from startd on #...
> (match #...).
> 4/27 01:50:33 (pid:16491) Return from Handler <to startd
> <10.20.2.61:41326>>
> 4/27 01:50:33 (pid:16491) Calling Handler
> <DaemonCore::HandleReqSocketHandler>
> 4/27 01:50:33 (pid:16491) Calling HandleReq <handle_q> (0)
> 4/27 01:50:33 (pid:16491) ZKM: setting default map to lbuchman@sugar
> 4/27 01:50:33 (pid:16491) Return from HandleReq <handle_q>
> 4/27 01:50:33 (pid:16491) Return from Handler
> <DaemonCore::HandleReqSocketHandler>
> 4/27 01:50:33 (pid:16491) Calling HandleReq <handle_q> (0)
> 4/27 01:50:33 (pid:16491) ZKM: setting default map to lbuchman@sugar
> 4/27 01:50:33 (pid:16491) Return from HandleReq <handle_q>
> 4/27 01:50:33 (pid:16491) Calling Handler <to startd
> <10.20.2.61:41326>>
> 4/27 01:50:33 (pid:16491) ERROR "Assertion ERROR on (mrec-
> >request_claim_sock == sock)" at line 1361 in file
> dedicated_scheduler.C
> *** End of file SchedLog
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Questions about this message or Condor in general?
> Email address of the local Condor administrator:
> dabrown__AT__physics.syr.edu
> The Official Condor Homepage is http://www.cs.wisc.edu/condor
--
Duncan Brown Room 263-1, Department of Physics,
Assistant Professor of Physics Syracuse University, NY 13244, USA
Phone: (315) 443 5993 http://www.gravity.phy.syr.edu/~duncan
===========================================================================
Date of creation: Mon Apr 28 10:22:26 2008 (1209396149)
Subject: Actions
Assigned to gthain by gquinn
===========================================================================
Date of actions: Mon Apr 28 13:02:54 2008 (1209405775)
Date: Mon, 28 Apr 2008 13:58:17 -0500
From: Greg Thain <gthain__AT__cs.wisc.edu>
To: condor-support__AT__cs.wisc.edu
Subject: Re: [condor-support #2237] LIGO: condor_schedd exited (4)
>
> This weekend I has 4 schedd exits, all with the error message
>
> Assertion ERROR on (mrec->request_claim_sock == sock)" at line 1361
> in file dedicated_scheduler.C
>
I have not seen this before -- can you please send me the snippet of the
StartLog for the startds that are sending the response, e.g.:
4/27 01:50:33 (pid:16491) Calling Handler <to startd
> <10.20.2.61:41326>>
> 4/27 01:50:33 (pid:16491) Response problem from startd on #...
> (match #...).
> 4/27 01:50:33 (pid:16491) Return from Handler <to startd
> <10.20.2.61:41326>>
-Greg
===========================================================================
Date mail was appended: Mon Apr 28 14:56:51 2008 (1209412611)
Subject: Actions
Status changed from open to pending by tannenba
===========================================================================
Date of actions: Fri May 23 12:57:32 2008 (1211565452)
To: condor-support response tracking system <condor-support__AT__cs.wisc.edu>
From: Duncan Brown <dabrown__AT__physics.syr.edu>
Subject: Re: [condor-support #2237] LIGO: condor_schedd exited (4)
Date: Wed, 18 Jun 2008 10:13:14 -0400
X-Scanner: InterScan AntiVirus for Sendmail
X-Seen-BY: mailfromd 4.1 obsidian.cs.wisc.edu
> >
> > This weekend I has 4 schedd exits, all with the error message
> >
> > Assertion ERROR on (mrec->request_claim_sock == sock)" at line 1361
> > in file dedicated_scheduler.C
> >
>
> I have not seen this before -- can you please send me the snippet
> of the
> StartLog for the startds that are sending the response, e.g.:
>
>
> 4/27 01:50:33 (pid:16491) Calling Handler <to startd
> > <10.20.2.61:41326>>
> > 4/27 01:50:33 (pid:16491) Response problem from startd on #...
> > (match #...).
> > 4/27 01:50:33 (pid:16491) Return from Handler <to startd
> > <10.20.2.61:41326>>
>
> -Greg
Hi Greg,
Sorry for the delay getting back to this one. It's still happening
with 7.0.2. Here's the email message and the corresponding StartLog.
Cheers,
Duncan.
This is an automated email from the Condor system
on machine "sugar.phy.syr.edu". Do not reply.
"/usr/sbin/condor_schedd" on "sugar.phy.syr.edu" exited with status 4.
Condor will automatically restart this process in 17 seconds.
*** Last 20 line(s) of file /usr1/condor/log/SchedLog:
6/17 16:27:03 (pid:7516) Return from Handler <to startd
<10.20.2.44:53647>>
6/17 16:27:03 (pid:7516) Calling Handler <to startd <10.20.2.44:53647>>
6/17 16:27:03 (pid:7516) Return from Handler <to startd
<10.20.2.44:53647>>
6/17 16:27:03 (pid:7516) Calling Handler <to startd <10.20.2.72:57998>>
6/17 16:27:03 (pid:7516) Return from Handler <to startd
<10.20.2.72:57998>>
6/17 16:27:03 (pid:7516) Calling Handler <to startd <10.20.2.79:58810>>
6/17 16:27:03 (pid:7516) Return from Handler <to startd
<10.20.2.79:58810>>
6/17 16:27:03 (pid:7516) Calling Handler <to startd <10.20.2.79:58810>>
6/17 16:27:03 (pid:7516) Return from Handler <to startd
<10.20.2.79:58810>>
6/17 16:27:03 (pid:7516) Calling Handler <to startd <10.20.2.44:53647>>
6/17 16:27:03 (pid:7516) Return from Handler <to startd
<10.20.2.44:53647>>
6/17 16:27:03 (pid:7516) Inserting new attribute Scheduler into non-
active cluster cid=49958 acid=-1
6/17 16:27:03 (pid:7516) Inserting new attribute Scheduler into non-
active cluster cid=49959 acid=-1
6/17 16:27:03 (pid:7516) Inserting new attribute Scheduler into non-
active cluster cid=49960 acid=-1
6/17 16:27:03 (pid:7516) Inserting new attribute Scheduler into non-
active cluster cid=49961 acid=-1
6/17 16:27:03 (pid:7516) Inserting new attribute Scheduler into non-
active cluster cid=49963 acid=-1
6/17 16:27:04 (pid:7516) Calling Handler <to startd <10.20.2.72:57998>>
6/17 16:27:04 (pid:7516) Return from Handler <to startd
<10.20.2.72:57998>>
6/17 16:27:04 (pid:7516) Calling Handler <to startd <10.20.2.79:58810>>
6/17 16:27:04 (pid:7516) ERROR "Assertion ERROR on (mrec-
>request_claim_sock == sock)" at line 1361 in file
dedicated_scheduler.C
*** End of file SchedLog
6/17 16:26:32 State change: BOINC client running for slot1
6/17 16:26:32 slot1: Changing activity: Idle -> Busy
6/17 16:26:32 State change: BOINC client running for slot2
6/17 16:26:32 slot2: Changing activity: Idle -> Busy
6/17 16:26:32 State change: BOINC client running for slot3
6/17 16:26:32 slot3: Changing activity: Idle -> Busy
6/17 16:26:32 State change: BOINC client running for slot4
6/17 16:26:32 slot4: Changing activity: Idle -> Busy
6/17 16:26:32 Calling HandleReq <HandleChildAliveCommand> (0)
6/17 16:26:32 Return from HandleReq <HandleChildAliveCommand>
6/17 16:27:03 DaemonCore: Command received via UDP from host
<10.20.1.25:33376>, access level NEGOTIATOR
6/17 16:27:03 DaemonCore: received command 440 (MATCH_INFO), calling
handler (command_match_info)
6/17 16:27:03 Calling HandleReq <command_match_info> (0)
6/17 16:27:03 slot1: match_info called
6/17 16:27:03 slot1: Received match <10.20.2.72:57998>#1213733586#17#...
6/17 16:27:03 slot1: State change: match notification protocol
successful
6/17 16:27:03 slot1: Changing activity: Busy -> Killing
6/17 16:27:03 slot1: State change: starter exited
6/17 16:27:03 slot1: Changing state and activity: Backfill/Killing ->
Matched/Idle
6/17 16:27:03 Return from HandleReq <command_match_info>
6/17 16:27:03 DaemonCore: Command received via UDP from host
<10.20.1.25:33376>, access level NEGOTIATOR
6/17 16:27:03 DaemonCore: received command 440 (MATCH_INFO), calling
handler (command_match_info)
6/17 16:27:03 Calling HandleReq <command_match_info> (0)
6/17 16:27:03 slot2: match_info called
6/17 16:27:03 slot2: Received match <10.20.2.72:57998>#1213733586#18#...
6/17 16:27:03 slot2: State change: match notification protocol
successful
6/17 16:27:03 slot2: Changing activity: Busy -> Killing
6/17 16:27:03 slot2: State change: starter exited
6/17 16:27:03 slot2: Changing state and activity: Backfill/Killing ->
Matched/Idle
6/17 16:27:03 Return from HandleReq <command_match_info>
6/17 16:27:03 DaemonCore: Command received via UDP from host
<10.20.1.25:33376>, access level NEGOTIATOR
6/17 16:27:03 DaemonCore: received command 440 (MATCH_INFO), calling
handler (command_match_info)
6/17 16:27:03 Calling HandleReq <command_match_info> (0)
6/17 16:27:03 slot3: match_info called
6/17 16:27:03 slot3: Received match <10.20.2.72:57998>#1213733586#19#...
6/17 16:27:03 slot3: State change: match notification protocol
successful
6/17 16:27:03 slot3: Changing activity: Busy -> Killing
6/17 16:27:03 slot3: State change: starter exited
6/17 16:27:03 slot3: Changing state and activity: Backfill/Killing ->
Matched/Idle
6/17 16:27:03 Return from HandleReq <command_match_info>
6/17 16:27:03 DaemonCore: Command received via UDP from host
<10.20.1.25:33376>, access level NEGOTIATOR
6/17 16:27:03 DaemonCore: received command 440 (MATCH_INFO), calling
handler (command_match_info)
6/17 16:27:03 Calling HandleReq <command_match_info> (0)
6/17 16:27:03 slot4: match_info called
6/17 16:27:03 slot4: Received match <10.20.2.72:57998>#1213733586#20#...
6/17 16:27:03 slot4: State change: match notification protocol
successful
6/17 16:27:03 slot4: Changing activity: Busy -> Killing
6/17 16:27:03 Return from HandleReq <command_match_info>
6/17 16:27:03 Calling Handler <receiveJobClassAdUpdate>
6/17 16:27:03 Return from Handler <receiveJobClassAdUpdate>
6/17 16:27:03 DaemonCore: pid 7625 exited with status 0, invoking
reaper 2 <BOINC_BackfillMgr::reaper()>
6/17 16:27:03 BOINC client (pid 7625) exited with status 0
6/17 16:27:03 slot4: State change: starter exited
6/17 16:27:03 DaemonCore: return from reaper for pid 7625
6/17 16:27:03 Calling Handler <DaemonCore::HandleReqSocketHandler>
6/17 16:27:03 DaemonCore: Command received via TCP from host
<10.20.1.23:55814>, access level DAEMON
6/17 16:27:03 DaemonCore: received command 442 (REQUEST_CLAIM),
calling handler (command_request_claim)
6/17 16:27:03 Calling HandleReq <command_request_claim> (0)
6/17 16:27:03 slot1: Request accepted.
6/17 16:27:03 slot1: Remote owner is
DedicatedScheduler__AT__sugar.phy.syr.edu
6/17 16:27:03 slot1: State change: claiming protocol successful
6/17 16:27:03 slot1: Changing state: Matched -> Claimed
6/17 16:27:03 Return from HandleReq <command_request_claim>
6/17 16:27:03 Return from Handler <DaemonCore::HandleReqSocketHandler>
6/17 16:27:03 Calling Handler <DaemonCore::HandleReqSocketHandler>
6/17 16:27:03 DaemonCore: Command received via TCP from host
<10.20.1.23:38930>, access level DAEMON
6/17 16:27:03 DaemonCore: received command 442 (REQUEST_CLAIM),
calling handler (command_request_claim)
6/17 16:27:03 Calling HandleReq <command_request_claim> (0)
6/17 16:27:03 slot2: Request accepted.
6/17 16:27:03 slot2: Remote owner is
DedicatedScheduler__AT__sugar.phy.syr.edu
6/17 16:27:03 slot2: State change: claiming protocol successful
6/17 16:27:03 slot2: Changing state: Matched -> Claimed
6/17 16:27:03 Return from HandleReq <command_request_claim>
6/17 16:27:03 Return from Handler <DaemonCore::HandleReqSocketHandler>
6/17 16:27:03 Calling Handler <DaemonCore::HandleReqSocketHandler>
6/17 16:27:03 DaemonCore: Command received via TCP from host
<10.20.1.23:44411>, access level DAEMON
6/17 16:27:03 DaemonCore: received command 442 (REQUEST_CLAIM),
calling handler (command_request_claim)
6/17 16:27:03 Calling HandleReq <command_request_claim> (0)
6/17 16:27:03 slot4: Request accepted.
6/17 16:27:03 slot4: Remote owner is
DedicatedScheduler__AT__sugar.phy.syr.edu
6/17 16:27:03 slot4: State change: claiming protocol successful
6/17 16:27:03 slot4: Changing state: Matched -> Claimed
6/17 16:27:03 Return from HandleReq <command_request_claim>
6/17 16:27:03 Return from Handler <DaemonCore::HandleReqSocketHandler>
6/17 16:27:03 Calling Handler <DaemonCore::HandleReqSocketHandler>
6/17 16:27:03 DaemonCore: Command received via TCP from host
<10.20.1.23:38158>, access level DAEMON
6/17 16:27:03 DaemonCore: received command 442 (REQUEST_CLAIM),
calling handler (command_request_claim)
6/17 16:27:03 Calling HandleReq <command_request_claim> (0)
6/17 16:27:03 slot3: Request accepted.
6/17 16:27:03 slot3: Remote owner is
DedicatedScheduler__AT__sugar.phy.syr.edu
6/17 16:27:03 slot3: State change: claiming protocol successful
6/17 16:27:03 slot3: Changing state: Matched -> Claimed
6/17 16:27:03 Return from HandleReq <command_request_claim>
6/17 16:27:03 Return from Handler <DaemonCore::HandleReqSocketHandler>
6/17 16:57:03 slot1: State change: claim lease expired (condor_schedd
gone?)
6/17 16:57:03 slot1: Changing state and activity: Claimed/Idle ->
Preempting/Killing
6/17 16:57:03 slot1: State change: No preempting claim, returning to
owner
6/17 16:57:03 slot1: Changing state and activity: Preempting/Killing -
> Owner/Idle
6/17 16:57:03 slot1: State change: IS_OWNER is false
6/17 16:57:03 slot1: Changing state: Owner -> Unclaimed
6/17 16:57:03 slot1: State change: START_BACKFILL is TRUE
6/17 16:57:03 slot1: Changing state: Unclaimed -> Backfill
6/17 16:57:03 slot2: State change: claim lease expired (condor_schedd
gone?)
6/17 16:57:03 slot2: Changing state and activity: Claimed/Idle ->
Preempting/Killing
6/17 16:57:03 slot2: State change: No preempting claim, returning to
owner
6/17 16:57:03 slot2: State change: IS_OWNER is false
6/17 16:57:03 slot2: Changing state: Owner -> Unclaimed
6/17 16:57:03 slot2: State change: START_BACKFILL is TRUE
6/17 16:57:03 slot2: Changing state: Unclaimed -> Backfill
6/17 16:57:03 slot4: State change: claim lease expired (condor_schedd
gone?)
6/17 16:57:03 slot4: Changing state and activity: Claimed/Idle ->
Preempting/Killing
6/17 16:57:03 slot4: State change: No preempting claim, returning to
owner
6/17 16:57:03 slot4: Changing state and activity: Preempting/Killing -
> Owner/Idle
6/17 16:57:03 slot4: State change: IS_OWNER is false
6/17 16:57:03 slot4: Changing state: Owner -> Unclaimed
6/17 16:57:03 slot4: State change: START_BACKFILL is TRUE
6/17 16:57:03 slot4: Changing state: Unclaimed -> Backfill
6/17 16:57:03 slot3: State change: claim lease expired (condor_schedd
gone?)
6/17 16:57:03 slot3: Changing state and activity: Claimed/Idle ->
Preempting/Killing
6/17 16:57:03 slot3: State change: No preempting claim, returning to
owner
6/17 16:57:03 slot3: Changing state and activity: Preempting/Killing -
> Owner/Idle
6/17 16:57:03 slot3: State change: IS_OWNER is false
6/17 16:57:03 slot3: Changing state: Owner -> Unclaimed
6/17 16:57:03 slot3: State change: START_BACKFILL is TRUE
6/17 16:57:03 slot3: Changing state: Unclaimed -> Backfill
6/17 16:57:06 State change: BOINC client running for slot1
6/17 16:57:06 slot1: Changing activity: Idle -> Busy
6/17 16:57:06 State change: BOINC client running for slot2
6/17 16:57:06 slot2: Changing activity: Idle -> Busy
6/17 16:57:06 State change: BOINC client running for slot3
6/17 16:57:06 slot3: Changing activity: Idle -> Busy
6/17 16:57:06 State change: BOINC client running for slot4
6/17 16:57:06 slot4: Changing activity: Idle -> Busy
6/17 16:57:06 Calling HandleReq <HandleChildAliveCommand> (0)
6/17 16:57:06 Return from HandleReq <HandleChildAliveCommand>
6/17 16:57:13 DaemonCore: Command received via UDP from host
<10.20.1.25:33394>, access level NEGOTIATOR
6/17 16:57:13 DaemonCore: received command 440 (MATCH_INFO), calling
handler (command_match_info)
6/17 16:57:13 Calling HandleReq <command_match_info> (0)
6/17 16:57:13 slot1: match_info called
6/17 16:57:13 slot1: Received match <10.20.2.72:57998>#1213733586#25#...
6/17 16:57:13 slot1: State change: match notification protocol
successful
6/17 16:57:13 slot1: Changing activity: Busy -> Killing
6/17 16:57:13 slot1: State change: starter exited
6/17 16:57:13 slot1: Changing state and activity: Backfill/Killing ->
Matched/Idle
6/17 16:57:13 Return from HandleReq <command_match_info>
6/17 16:57:13 DaemonCore: Command received via UDP from host
<10.20.1.25:33394>, access level NEGOTIATOR
6/17 16:57:13 DaemonCore: received command 440 (MATCH_INFO), calling
handler (command_match_info)
6/17 16:57:13 Calling HandleReq <command_match_info> (0)
6/17 16:57:13 slot2: match_info called
6/17 16:57:13 slot2: Received match <10.20.2.72:57998>#1213733586#26#...
6/17 16:57:13 slot2: State change: match notification protocol
successful
6/17 16:57:13 slot2: Changing activity: Busy -> Killing
6/17 16:57:13 slot2: State change: starter exited
6/17 16:57:13 slot2: Changing state and activity: Backfill/Killing ->
Matched/Idle
6/17 16:57:13 Return from HandleReq <command_match_info>
6/17 16:57:13 DaemonCore: Command received via UDP from host
<10.20.1.25:33394>, access level NEGOTIATOR
6/17 16:57:13 DaemonCore: received command 440 (MATCH_INFO), calling
handler (command_match_info)
--
Duncan Brown Room 263-1, Department of Physics,
Assistant Professor of Physics Syracuse University, NY 13244, USA
Phone: (315) 443 5993 http://www.gravity.phy.syr.edu/~duncan
===========================================================================
Date mail was appended: Wed Jun 18 9:13:21 2008 (1213798401)
CC: Stuart Anderson <anderson__AT__ligo.caltech.edu>
From: Duncan Brown <dabrown__AT__physics.syr.edu>
Subject: Re: [condor-support #2237] LIGO: condor_schedd exited (4)
Date: Wed, 18 Jun 2008 10:14:51 -0400
To: condor-support response tracking system <condor-support__AT__cs.wisc.edu>
X-Scanner: InterScan AntiVirus for Sendmail
X-Seen-BY: mailfromd 4.1 granite.cs.wisc.edu
X-MIME-Autoconverted: from quoted-printable to 8bit by chopin.cs.wisc.edu
id m5IEEssP019090
Hi Greg,
Here is one of the other messages. Notice that the message "Response
problem from startd on..." contains binary garbage.
Cheers,
Duncan.
Begin forwarded message:
> *** Last 20 line(s) of file /usr1/condor/log/SchedLog:
> 6/17 16:26:31 (pid:5886) Response problem from startd on šER
> (match #...).
> 6/17 16:26:31 (pid:5886) Return from Handler <to startd
> <10.20.2.79:58810>>
> 6/17 16:26:31 (pid:5886) Calling Handler <to startd
> <10.20.2.79:58810>>
> 6/17 16:26:31 (pid:5886) Response problem from startd on P[N
> (match #...).
> 6/17 16:26:31 (pid:5886) Return from Handler <to startd
> <10.20.2.79:58810>>
> 6/17 16:26:31 (pid:5886) Calling Handler <to startd
> <10.20.2.79:58810>>
> 6/17 16:26:31 (pid:5886) Response problem from startd on šER
> (match #...).
> 6/17 16:26:31 (pid:5886) Return from Handler <to startd
> <10.20.2.79:58810>>
> 6/17 16:26:31 (pid:5886) Calling Handler <to startd
> <10.20.2.79:58810>>
> 6/17 16:26:31 (pid:5886) Response problem from startd on P[N
> (match #...).
> 6/17 16:26:31 (pid:5886) Return from Handler <to startd
> <10.20.2.79:58810>>
> 6/17 16:26:31 (pid:5886) Calling Handler <to startd
> <10.20.2.79:58810>>
> 6/17 16:26:32 (pid:5886) Response problem from startd on šER
> (match #...).
> 6/17 16:26:32 (pid:5886) Return from Handler <to startd
> <10.20.2.79:58810>>
> 6/17 16:26:32 (pid:5886) Inserting new attribute Scheduler into non-
> active cluster cid=49959 acid=-1
> 6/17 16:26:32 (pid:5886) Inserting new attribute Scheduler into non-
> active cluster cid=49960 acid=-1
> 6/17 16:26:32 (pid:5886) Inserting new attribute Scheduler into non-
> active cluster cid=49961 acid=-1
> 6/17 16:26:32 (pid:5886) Inserting new attribute Scheduler into non-
> active cluster cid=49963 acid=-1
> 6/17 16:26:32 (pid:5886) Calling Handler <to startd
> <10.20.2.79:58810>>
> 6/17 16:26:32 (pid:5886) ERROR "Assertion ERROR on (mrec-
> >request_claim_sock == sock)" at line 1361 in file
> dedicated_scheduler.C
> *** End of file SchedLog
--
Duncan Brown Room 263-1, Department of Physics,
Assistant Professor of Physics Syracuse University, NY 13244, USA
Phone: (315) 443 5993 http://www.gravity.phy.syr.edu/~duncan
===========================================================================
Date mail was appended: Wed Jun 18 9:14:57 2008 (1213798497)
Subject: Actions
Ticket resolved by wenger
===========================================================================
Date of actions: Fri Aug 15 14:03:40 2008 (1218827021)