Alain,
I don´t seem to be getting that error anymore, but when I try to submit to the queue this is what my negotiator log reads: 8/18 09:35:20 condor_write(): Socket closed when trying to write buffer 8/18 09:35:20 Buf::write(): condor_write() failed 8/18 09:35:20 Could not send PERMISSION 8/18 09:35:20 Error: Ignoring schedd for this cycle 8/18 09:35:20 ---------- Finished Negotiation Cycle ---------- 8/18 09:35:49 Getting state information from the accountant 8/18 09:40:20 ---------- Started Negotiation Cycle ---------- 8/18 09:40:20 Phase 1: Obtaining ads from collector ... 8/18 09:40:20 Getting all public ads ... 8/18 09:40:20 Sorting 7 ads ... 8/18 09:40:20 Getting startd private ads ... 8/18 09:40:20 Got ads: 7 public and 2 private 8/18 09:40:20 Public ads include 1 submitter, 2 startd 8/18 09:40:20 Phase 2: Performing accounting ... 8/18 09:40:20 Phase 3: Sorting submitter ads by priority ... 8/18 09:40:20 Phase 4.1: Negotiating with schedds ... 8/18 09:40:20 Negotiating with charris@BGLaptop03 at <192.168.0.12:1031> 8/18 09:40:20 Request 00008.00000: 8/18 09:40:41 Can't connect to <192.168.0.20:1031>:0, errno = 10060 8/18 09:40:41 Will keep trying for 10 seconds... 8/18 09:40:42 Connect failed for 10 seconds; returning FALSE 8/18 09:40:42 ERROR: SECMAN:2003:TCP connection to <192.168.0.20:1031> failed 8/18 09:40:42 condor_write(): Socket closed when trying to write buffer 8/18 09:40:42 Buf::write(): condor_write() failed 8/18 09:40:42 Could not send PERMISSION 8/18 09:40:42 Error: Ignoring schedd for this cycle And if I do a condor_q -analyze on the submited file this is what it reads: -- Submitter: BGLaptop03 : <192.168.0.12:1031> : BGLaptop03 ID OWNER SUBMITTED RUN_TIME ST PRI SIZE CMD 8.0 charris 8/18 09:34 0+00:00:00 I 0 0.0 printname.ba 1 jobs; 1 idle, 0 running, 0 held C:\TestCondor\examples\printname>condor_q 8 -analyze -- Submitter: BGLaptop03 : <192.168.0.12:1031> : BGLaptop03 ID OWNER SUBMITTED RUN_TIME ST PRI SIZE CMD --- 008.000: Run analysis summary. Of 2 machines, 0 are rejected by your job's requirements 0 reject your job because of their own requirements 0 match, but are serving users with a better priority in the pool 2 match, match, but reject the job for unknown reasons 0 match, but will not currently preempt their existing job 0 are available to run your job I checked the status of the submitted file, because it remains idle in the queue and never runs. Do you know what may be causing this error? Candace |