[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] Test of Execute Machine into Multiple pools




Hi Dan,

I have upgraded one pool (PoolA) to V7.2.4 and it worked correctly. SCHEDD have not exited with that error code. Job run to completion accordingly.
I will be making the change to all other machines to perform additional tests.

Find attached the new log files for reference.

Thanks for yous help,

Klaus Schwarzmeier




Klaus Schwarzmeier/ENGENHARIA/SJK/EMBRAER

09/07/2009 13:04

To
Dan Bradley <dan@xxxxxxxxxxxx>
cc
Subject
Re: [Condor-users] Test of Execute Machine into Multiple poolsLink




Dan,

I forgot to mention that there were no "core" files. All the files that were present in the Log directory I have posted.
I am working on the upgrade right now and I will let you know when I end the test again.

Klaus

Klaus Otto Schwarzmeier
Senior Engineer, R&T - Systems Modeling & Simulation
Embraer - São José dos Campos
Phone: +55 (12) 3927-3947 - Fax: +55 (12) 3927-6600 ext 1730




Dan Bradley <dan@xxxxxxxxxxxx>

09/07/2009 12:02

To
kschwarz@xxxxxxxxxxxxxx
cc
Subject
Re: [Condor-users] Test of Execute Machine into Multiple pools





Klaus,

I took a look at the new logs you sent. Where there any files in your
log directory with "core" in their name? I was hoping the schedd would
produce a core file.

I am very curious to know whether you still have this problem with a
schedd from 7.2.4. If it is easier for you to test just an upgraded
schedd, leaving the rest alone, that should be good enough to tell
whether the problem has been fixed.

--Dan

kschwarz@xxxxxxxxxxxxxx wrote:
>
> Hi Dan,
>
> I have set the debuging parameters, restarted the daemons from
> scratch, submitted the job again and waited for the SCHEDD exit and
> turned all daemons off.
> Find attached the resulting log files.
>
> I will be installing the V7.2.4 and rerun the test again.
>
> Thanks and regards,
> Klaus Schwarzmeier
>
>
>
>
> *Dan Bradley <dan@xxxxxxxxxxxx>*
> Sent by: condor-users-bounces@xxxxxxxxxxx
>
> 08/07/2009 19:45
> Please respond to
> Condor-Users Mail List <condor-users@xxxxxxxxxxx>
>
>
>                  
> To
>                  Condor-Users Mail List <condor-users@xxxxxxxxxxx>
> cc
>                  
> Subject
>                  Re: [Condor-users] Test of Execute Machine into Multiple pools
>
>
>
>                  
>
>
>
>
>
>
> To collect more information about why your schedd is crashing, I
> recommend setting the following configuration variables:
>
> SCHEDD_DEBUG = D_ALL
> CREATE_CORE_FILES = True
>
> After the schedd crashes, there should be a file in the log directory
> with "core" in its name.
>
> It would also help if you could upgrade to the latest 7.2 release. It's
> always possible that the problem you are having has already been fixed.
>
> --Dan
>
> kschwarz@xxxxxxxxxxxxxx wrote:
> >
> > Hi folks,
> >
> > I am trying to test the Condor Admin How-To Recipe "How to have
> > execute machines belong to multiple pools". I am running Condor v7.2.1
> > on all machines that are running Windows XP.
> > The condor_status command to the PoolA and PoolB are showing their
> > execute machines and the SuperPool is showing all machines from PoolA
> > and PoolB as expected.
> > When I submit a simple job to PoolA or to PoolB or to SuperPool their
> > corresponding SCHEDD daemon exits with the following message in the
> > MasterLog of the machine running SCHEDD.
> >
> > 7/8 14:56:43 The SCHEDD (pid 3192) exited with status -1073740777
> > 7/8 14:56:43 Sending obituary for "C:\Condor/bin/condor_schedd.exe"
> > 7/8 14:57:04 restarting C:\Condor/bin/condor_schedd.exe in 10 seconds
> > 7/8 14:57:14 Started DaemonCore process
> > "C:\Condor/bin/condor_schedd.exe", pid and pgroup = 2596
> > 7/8 14:57:44 The SCHEDD (pid 2596) exited with status -1073740777
> > 7/8 14:57:44 Sending obituary for "C:\Condor/bin/condor_schedd.exe"
> > 7/8 14:58:05 restarting C:\Condor/bin/condor_schedd.exe in 11 seconds
> > 7/8 14:58:16 Started DaemonCore process
> > "C:\Condor/bin/condor_schedd.exe", pid and pgroup = 1108
> >
> > Could someone help me to fix that?
> >
> > Find attached the configuration files of PoolA or PoolB and SuperPool,
> > the condor_config_val -name <Poolsubmit machine> -dump output, and the
> > log files of the submit machine that is in the PoolA.
> >
> >
> >
> > Klaus/
> > /
> > ------------------------------------------------------------------------
> > /This message is intended solely for the use of its addressee and may
> > contain privileged or confidential information. All information
> > contained herein shall be treated as confidential and shall not be
> > disclosed to any third party without Embraer’s prior written approval.
> > If you are not the addressee you should not distribute, copy or file
> > this message. In this case, please notify the sender and destroy its
> > contents immediately.
> > Esta mensagem é para uso exclusivo de seu destinatário e pode conter
> > informações privilegiadas e confidenciais. Todas as informações aqui
> > contidas devem ser tratadas como confidenciais e não devem ser
> > divulgadas a terceiros sem o prévio consentimento por escrito da
> > Embraer. Se você não é o destinatário não deve distribuir, copiar ou
> > arquivar a mensagem. Neste caso, por favor, notifique o remetente da
> > mesma e destrua imediatamente a mensagem./
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Condor-users mailing list
> > To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx
> with a
> > subject: Unsubscribe
> > You can also unsubscribe by visiting
> > https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> >
> > The archives can be found at:
> > https://lists.cs.wisc.edu/archive/condor-users/
> >
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/condor-users/
>
> /
> /
> ------------------------------------------------------------------------
> /This message is intended solely for the use of its addressee and may
> contain privileged or confidential information. All information
> contained herein shall be treated as confidential and shall not be
> disclosed to any third party without Embraer’s prior written approval.
> If you are not the addressee you should not distribute, copy or file
> this message. In this case, please notify the sender and destroy its
> contents immediately.
> Esta mensagem é para uso exclusivo de seu destinatário e pode conter
> informações privilegiadas e confidenciais. Todas as informações aqui
> contidas devem ser tratadas como confidenciais e não devem ser
> divulgadas a terceiros sem o prévio consentimento por escrito da
> Embraer. Se você não é o destinatário não deve distribuir, copiar ou
> arquivar a mensagem. Neste caso, por favor, notifique o remetente da
> mesma e destrua imediatamente a mensagem./
> ------------------------------------------------------------------------
>
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/condor-users/
>  



This message is intended solely for the use of its addressee and may contain privileged or confidential information. All information contained herein shall be treated as confidential and shall not be disclosed to any third party without Embraer’s prior written approval. If you are not the addressee you should not distribute, copy or file this message. In this case, please notify the sender and destroy its contents immediately.
Esta mensagem é para uso exclusivo de seu destinatário e pode conter informações privilegiadas e confidenciais. Todas as informações aqui contidas devem ser tratadas como confidenciais e não devem ser divulgadas a terceiros sem o prévio consentimento por escrito da Embraer. Se você não é o destinatário não deve distribuir, copiar ou arquivar a mensagem. Neste caso, por favor, notifique o remetente da mesma e destrua imediatamente a mensagem.



This message is intended solely for the use of its addressee and may contain privileged or confidential information. All information contained herein shall be treated as confidential and shall not be disclosed to any third party without Embraer’s prior written approval. If you are not the addressee you should not distribute, copy or file this message. In this case, please notify the sender and destroy its contents immediately.
Esta mensagem é para uso exclusivo de seu destinatário e pode conter informações privilegiadas e confidenciais. Todas as informações aqui contidas devem ser tratadas como confidenciais e não devem ser divulgadas a terceiros sem o prévio consentimento por escrito da Embraer. Se você não é o destinatário não deve distribuir, copiar ou arquivar a mensagem. Neste caso, por favor, notifique o remetente da mesma e destrua imediatamente a mensagem.

Attachment: super-pool_log_files-3.zip
Description: Zip archive