Re: [Chromium-users] crserver & crappfaker won't start

[Brian P. <bri...@tu...>]

RCCOP wrote:
> 
> Aashish Chaudhary wrote:
>> Hi,
>>
>> I was able to get to this point and I was getting the same error. I even
>> set
>> CRMOTHERSHIP to
>>
>> 1. localhost
>> 2. my machine name
>> 3. machine_name  + server
>>
>>
>> I even changed my /etc/hosts file so as to resolve ip to my network URL.
>> But
>> I as soon as I start crappfaker app and server crashes. I was trying to
>> run
>> atlantis with crdemo.conf file.
>>
>> ~Aashish
>>
>>
> 
> 
> I know it's been a few months, but I also am having the similar problems. 
> I've followed all the steps exactly, and I've also tried setting
> CRMOTHERSHIP to the three that the person I've quoted tried.  The errors I
> get occur after typing crserver and crappfaker.  They are as follows:
> 
> %  crserver
> CR Error(citadel:10787): Bad Mothership response: Never heard of server host
> citadel.*.  Expected one of: <this remains blank>
> 
> % crappfaker
> CR Error(citadel:10789): Bad Mothership response: Never heard of faker host
> citadel.*.  Expected one of:  <this also remains blank>
> 
> Note: I put an asterisk for privacy reasons.

This sort of thing usually comes from hostname misconfiguration.  Does 
running 'hostname' in your shell give you a fully qualified domain name?

If you ping the FQDN and 'citadel' do you get the sam address?


> Also, every time I type "python crdemo.conf atlantis" I get the following
> error, I'm not sure if this is normal or not but I've been ignoring it and
> have even gotten (and fixed) some of the errors mentioned previously in this
> thread.  So I assumed I was on the right track anyway...
> 
> % python crdemo.conf atlantis
> This is Chromium, Version 1.9
> Couldn't find/create local TCP port (make sure that another mothership isn't
> already running)
> 
> 
> MOTHERSHIP EXCEPTION!  TERRIBLE!
> Traceback (most recent call last):
>   File "../server/mothership.py", line 1068, in Go
>     Fatal( "Couldn't find/create local TCP port (make sure that another
> mothership isn't already running)")
>   File "../server/mothership.py", line 102, in Fatal
>     sys.exit(-1)
> SystemExit: -1


Does 'ps -elf' report any other python/mothership processes?

Maybe you have another service running that's using the default 
mothership port.  You can set the mothership port in the cr config file 
by passing the port number to the cr.Go() function.  You'll have to set 
CRMOTHERSHIP="hostname:portnumber" then.

-Brian