RE: [condor-users] Windows NT Problem

["Lewis, Gareth (UK)" <gareth.lewis@xxxxxxxxxxxxxx>]

I had been following this thread but thought it didn't apply to us because we weren't using Novell for networking. However, it appears that it does. We are running Windows NT (SP6) in a domain with most of the machines on 6.4.7 but have just started to introduce some new machines running 6.6.1. As in the other cases reported, STARTD on these new machines keeps failing/restarting with the error: "GetCursorInfo() failed (err=1402)". See the log file below.

Is there a workaround for this, until the problem is fixed (6.6.3?)? Or should we go back to 6.4.7 for now? Any suggestions gratefully received.

Regards,
Gareth.

*** Last 20 line(s) of file StartLog:
4/5 11:48:18 ******************************************************
4/5 11:48:18 ** condor_startd.exe (CONDOR_STARTD) STARTING UP
4/5 11:48:18 ** $CondorVersion: 6.6.1 Feb  5 2004 $
4/5 11:48:18 ** $CondorPlatform: INTEL-WINNT40 $
4/5 11:48:18 ** PID = 212
4/5 11:48:18 ******************************************************
4/5 11:48:18 Using config file: C:\Condor\condor_config
4/5 11:48:18 Using local config files: C:\Condor/condor_config.local
4/5 11:48:18 DaemonCore: Command Socket at <deleted>
4/5 11:48:18 New machine resource allocated
4/5 11:48:23 About to run initial benchmarks.
4/5 11:48:28 Completed initial benchmarks.
4/5 11:53:28 GetCursorInfo() failed (err=1402)
*** End of file StartLog

*** Last entry in core file core.STARTD.WIN32

=======================
Exception code: C0000005 ACCESS_VIOLATION
Fault address:  00406C47 01:00005C47 C:\Condor\bin\condor_startd.exe

Registers:
EAX:00C5A1B0
EBX:00486398
ECX:000002C9
EDX:0000001C
ESI:00000020
EDI:00447108
CS:EIP:001B:00406C47
SS:ESP:0023:0012FE94  EBP:0012FEA4
DS:0023  ES:0023  FS:0038  GS:0000
Flags:00010206

Call stack:
Address   Frame
00406C47  0012FEA4  MachAttributes::compute+193
00408E18  0012FEBC  ResMgr::compute+2E
00408D7F  0012FEC8  ResMgr::eval_and_update_all+A
004425D1  00000004  TimerManager::Timeout+F9

*** End of file core.STARTD.WIN32

-----Original Message-----
From: Colin Stolley [mailto:stolley@xxxxxxxxxxx]
Sent: 24 March 2004 17:27
To: condor-users@xxxxxxxxxxx
Subject: Re: [condor-users] Windows NT Problem


> Since we are a Novell site, we have Microsoft Network turned off (disabled). We
> tried turning things like the Workstation Service on.
> 
> Although startd still "crashed" we get a lot less errors.
> 
> How much Microsoft networking components do we need enabled, before startd
> stops "crashing"?

I suspect this is a red herring, but I'm not sure. You certainly need
TCP/IP enabled, but I don't believe you need anything besides that. Could
you add:

STARTD_DEBUG = $(STARTD_DEBUG) D_FULLDEBUG

to your config file, and repost your StartLog?

thanks for assisting in debugging this!

Colin
Condor Support Information:
http://www.cs.wisc.edu/condor/condor-support/
To Unsubscribe, send mail to majordomo@xxxxxxxxxxx with
unsubscribe condor-users <your_email_address>



********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************
Condor Support Information:
http://www.cs.wisc.edu/condor/condor-support/
To Unsubscribe, send mail to majordomo@xxxxxxxxxxx with
unsubscribe condor-users <your_email_address>