No. There is nothing bad in any of the event logs, except the couple of times I killed the condor_master process. One thing I didn't mention is, I'm not able to stop the condor process/service using the 'services' control panel. I have to use the task manager and kill the condor_master.exe process. Then I am able to start the condor service using the 'services' control panel. I have left condor_master running for an hour now, and I have some more information in my logs. I actually have a SchedLog now, and condor_schedd seems to be running. There are lots of errors though. I have attached all 4 files that are currently in my condor/log dir. Any help appreciated. Thanks. John Alberts Technical Assistant for EMS Purdue University Calumet 219-989-2083 http://public.xdi.org/=john.alberts -----Original Message----- From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Matt Hope Sent: Tuesday, July 19, 2005 1:08 PM To: Condor-Users Mail List Subject: Re: [Condor-users] Condor on Windows 2003 Server On 7/19/05, John Alberts <alberts@xxxxxxxxxxxxxxxxxx> wrote: > > My MasterLog file only shows: > 7/19 12:04:23 > ****************************************************** > 7/19 12:04:23 ** Condor (CONDOR_MASTER) STARTING UP > 7/19 12:04:23 ** d:\Condor\bin\condor_master.exe > 7/19 12:04:23 ** $CondorVersion: 6.7.9 Jul 14 2005 $ > 7/19 12:04:23 ** $CondorPlatform: INTEL-WINNT50 $ > 7/19 12:04:23 ** PID = 2640 > 7/19 12:04:23 > ****************************************************** > 7/19 12:04:23 Using config file: d:\Condor/condor_config > 7/19 12:04:23 Using local config files: d:\Condor/condor_config.local > 7/19 12:04:23 DaemonCore: Command Socket at <205.215.68.70:2545> > 7/19 12:10:25 > ****************************************************** > 7/19 12:10:25 ** Condor (CONDOR_MASTER) STARTING UP > 7/19 12:10:25 ** d:\Condor\bin\condor_master.exe > 7/19 12:10:25 ** $CondorVersion: 6.7.9 Jul 14 2005 $ > 7/19 12:10:25 ** $CondorPlatform: INTEL-WINNT50 $ > 7/19 12:10:25 ** PID = 2652 > 7/19 12:10:25 > ****************************************************** > 7/19 12:10:25 Using config file: d:\Condor\condor_config > 7/19 12:10:25 Using local config files: d:\Condor\condor_config.local > 7/19 12:10:25 DaemonCore: Command Socket at <205.215.68.70:2565> > > As you can see, there is not much to go on here. Notice from the first > startup message the mixture of forward and backslashes in the condor_config > file that I had to correct. Since the other services aren't started, no > logs are generated for them. > > I'm not sure what else to do. Any help would be appreciated. I think the next thing the master does after creating the command socket is attempt to sort out the windows firewall - is this failing and causing a crash? Certainly seems like the master is simply dying... No core dump (on windows more of a stack dump) file is being written out is it? Also check the windows EventLog... Matt _______________________________________________ Condor-users mailing list Condor-users@xxxxxxxxxxx https://lists.cs.wisc.edu/mailman/listinfo/condor-users
Attachment:
.master_address
Description: Binary data
Attachment:
.schedd_address
Description: Binary data
Attachment:
MasterLog
Description: Binary data
Attachment:
SchedLog
Description: Binary data