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

[RCCOP <ca...@sr...>]

Brian Paul wrote:
> 
>> %  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?
> 
Yes, I got the same address when I did this.

I just tried changing /etc/hosts so it now looks like this:
127.0.0.1       localhost.localdomain   localhost
192.168.0.1     citadel.xxx.xxx.xxx      citadel

It previously looked like this:
127.0.0.1       localhost.localdomain   localhost
::1     localhost.localdomain   localhost

I was trying to follow the FAQ in order to solve my problem, but this didn't
help me either.  The error I got when trying to run with /etc/hosts in this
format was, so I'm pretty sure changing the host file was the wrong thing to
do (I have since reverted back to the original hosts file):

CR Warning(citadel:19927): Couldn't connect to citadel.sr.unh.edu:10000,
Connection timed out
CR Warning(citadel:19927): Couldn't find any suitable way to connect to
citadel.sr.unh.edu
CR Error(citadel:19927): Couldn't connect to the mothership, I have no idea
what to do!



>> % 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.
> 


There are no other python/mothership processes running.  However, I think
it's due to the fact that I've already run the code once and it's not
shutting down/closing after the error?  Not sure how to shut it off... I
tried running it on two different ports and each time the first run through
didn't get the error, but the second time did.
-- 
View this message in context: http://www.nabble.com/crserver---crappfaker-won%27t-start-tp13563222p14598491.html
Sent from the Chromium - User mailing list archive at Nabble.com.