RE: [Condor-users] Slow response

["Sandy Spence" <axs@xxxxxxxxxx>]

Hi Alan and other respondents,

The only unusual item in the log is

Can't send UPDATE_COLLECTOR_AD to collector (condor.cs.wisc.edu): Failed to
send UDP update command to collector

I am puzzled by this as I thought I had disabled all communication with
condor.cs.wisc.edu

Cheers,

Sandy


Computer Officer, RA Certification Manager
Department of Computer Science - UWA
Llandinam Building
Penglais Campus
Aberystwyth
Ceredigion
Wales - UK
SY23 3DB
Tel: (01970)-622433
Fax: (01970)-628536


-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx
[mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Alain Roy
Sent: 12 May 2005 15:43
To: condor-users@xxxxxxxxxxx
Subject: RE: [Condor-users] Slow response


>[axs@wig-01 ~]$ time condor_status

>real    3m4.741s
>user    0m0.028s
>sys     0m0.011s

I've never seen condor_status so slow before for such a small Condor pool. 
This is definitely unusual behavior.

Can you watch the CollectorLog while you do the condor_status query? If I
was on a Unix system, I would do:

* [On the central manager]
   tail -f CollectorLog

* [On the client]
   condor_status

I'm curious if there are any interesting messages in the CollectorLog that
indicate problems. If there aren't, you can increase the amount of debugging
information and try again.

Are you using any of Condor's security options, like GSI or Kerberos? What
OS are you running on?

-alain


_______________________________________________
Condor-users mailing list
Condor-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/condor-users