Re: [condor-users] Segmentation Fault

["A. Garbino" <agarbino@xxxxxx>]

Erik Paulson wrote:

> On Tue, Oct 28, 2003 at 11:01:11AM -0600, A. Garbino wrote:
>  
>
> > I'm trying to run condor on a gentoo system with Glibc 2.3, and after 
> > building the system I either get:
> >
> > seth sbin $ ./condor_master
> >
> > Neither the environment variable CONDOR_CONFIG,
> > /etc/condor/, nor ~condor/ contain a condor_config file.
> > Either set CONDOR_CONFIG to point to a valid config file,
> > or put a "condor_config" file in /etc/condor or ~condor/
> > Exiting.
> >
> > Or, when I link to the config file from one of the locations it suggests, I simply get Segmentation Fault.
> >
> > Any ideas?
> >
> >    
>
> Which version of Condor?
>
> Two things to try:
>
> 1. Make sure you're using the dynamically-linked version
> 2. Try the Redhat 9 version.
>
> -Erik
>
> 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>
>
>  
Ok, I've deleted everything from condor and reinstalled the 
dynamically-linked version, and no seg fault!.
However, when I start condor_master, only startd and schedd follow; the 
collector and negotiator daemons don't start up. After manually starting 
them, I tried running condor_status, and i get the following:

CEDAR:6001:Failed to connect to <192.168.101.9:9618>
Error: Couldn't contact the condor_collector on seth.phys.uh.edu.

Extra Info: the condor_collector is a process that runs on the central
manager of your Condor pool and collects the status of all the machines and
jobs in the Condor pool. The condor_collector might not be running, it 
might
be refusing to communicate with you, there might be a network problem, or
there may be some other problem. Check with your system administrator to 
fix
this problem.

If you are the system administrator, check that the condor_collector is
running on seth.phys.uh.edu, check the HOSTALLOW configuration in your
condor_config, and check the MasterLog and CollectorLog files in your log
directory for possible clues as to why the condor_collector is not
responding. Also see the Troubleshooting section of the manual.


And a grep from the config file gives:

HOSTALLOW_ADMINISTRATOR = $(CONDOR_HOST)
HOSTALLOW_OWNER = $(FULL_HOSTNAME), $(HOSTALLOW_ADMINISTRATOR)
HOSTALLOW_READ = *
#HOSTALLOW_READ = *.your.domain, *.cs.wisc.edu
##  HOSTALLOW_READ above as well.
HOSTALLOW_WRITE = *
#HOSTALLOW_WRITE = *.your.domain, your-friend's-machine.other.domain
HOSTALLOW_NEGOTIATOR = $(NEGOTIATOR_HOST)
HOSTALLOW_NEGOTIATOR_SCHEDD = $(NEGOTIATOR_HOST), $(FLOCK_NEGOTIATOR_HOSTS)
#HOSTALLOW_CONFIG = trusted-host.your.domain
HOSTALLOW_WRITE_COLLECTOR = $(HOSTALLOW_WRITE), $(FLOCK_FROM)
HOSTALLOW_WRITE_STARTD    = $(HOSTALLOW_WRITE), $(FLOCK_FROM)
HOSTALLOW_READ_COLLECTOR  = $(HOSTALLOW_READ), $(FLOCK_FROM)
HOSTALLOW_READ_STARTD     = $(HOSTALLOW_READ), $(FLOCK_FROM)



So what's wrong???


Alex



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>