RE: [Condor-users] Bad file descriptors

["Michael Yoder" <yoderm@xxxxxxxxxx>]

> I'm having trouble starting up the Condor daemons on some of my nodes.
> The MasterLog says:
> 
> 8/24 10:48:58 ******************************************************
> 8/24 10:48:58 ** condor_master (CONDOR_MASTER) STARTING UP
> 8/24 10:48:58 ** /usr/local/condor/sbin/condor_master
> 8/24 10:48:58 ** $CondorVersion: 6.6.10 Jun 13 2005 $
> 8/24 10:48:58 ** $CondorPlatform: I386-LINUX_RH9 $
> 8/24 10:48:58 ** PID = 5595
> 8/24 10:48:58 ******************************************************
> 8/24 10:48:58 Using config file: /etc/condor/condor_config
> 8/24 10:48:58 Using local config files:
> /usr/local/condor/local/condor_config.local
> 8/24 10:48:58 DaemonCore: Command Socket at <131.111.73.227:9653>
> 8/24 10:48:58 Started DaemonCore process
> "/usr/local/condor/sbin/condor_schedd", pid and pgroup = 5621
> 8/24 10:48:58 Started DaemonCore process
> "/usr/local/condor/sbin/condor_startd", pid and pgroup = 5629
> 8/24 10:48:58 ERROR "DaemonCore: select() returned an unexpected
error: 9
> (Bad file descriptor)
> " at line 1840 in file daemon_core.C
> 8/24 10:49:18 condor_read(): timeout reading buffer.
> 8/24 10:49:18 Sent SIGTERM to SCHEDD (pid 5621)
> 8/24 10:49:35 Sent SIGTERM to STARTD (pid 5629)
> 
> On other seemingly identical nodes, there's no problem.  Any thoughts
on
> what's going on?

Wow, that's an interesting one.  That error is way down in the bowels of
DaemonCore, and might be some sort of internal problem.  Try setting 

MASTER_DEBUG = D_ALL

and see if there is more information that can be used to track this
down.  Usually I don't like D_ALL because it's such an overwhelming
amount of output, but this is a special case. :-)  Good luck,

Mike Yoder
Principal Member of Technical Staff
Ask Mike: http://docs.optena.com
Direct  : +1.408.321.9000
Fax     : +1.408.321.9030
Mobile  : +1.408.497.7597
yoderm@xxxxxxxxxx

Optena Corporation
2860 Zanker Road, Suite 201
San Jose, CA 95134
http://www.optena.com