Couldn't resolve host name

Questions and Answers : Unix/Linux : Couldn't resolve host name

To post messages, you must log in.

AuthorMessage
chanueting
Volunteer tester

Send message
Joined: 24 May 08
Posts: 3
Credit: 2,162
RAC: 0
Hong Kong
Message 769155 - Posted: 16 Jun 2008, 17:26:54 UTC

I am using FC9, and I have followed the instruction from Official BOINC WIKI. And read many articles and ask many people on IRCs, I still couldn't find the answers of that: 'Couldn't resolve host name'. I would like to know the solution, here is the error message:

Mon 16 Jun 2008 10:05:06 PM HKT||Contacting account manager at http://bam.boincstats.com/
Mon 16 Jun 2008 10:05:06 PM HKT|SETI@home|Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 1 completed tasks
Mon 16 Jun 2008 10:05:09 PM HKT||Account manager error: can't resolve hostname
Mon 16 Jun 2008 10:05:09 PM HKT||Project communication failed: attempting access to reference site
Mon 16 Jun 2008 10:05:10 PM HKT||Access to reference site failed - check network connection or proxy configuration.
Mon 16 Jun 2008 10:05:12 PM HKT|SETI@home|Scheduler request failed: Couldn't resolve host name
ID: 769155 · Report as offensive
Dotsch
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 2422
Credit: 881,130
RAC: 42
Germany
Message 769190 - Posted: 16 Jun 2008, 19:01:11 UTC

Looks like something with the setup of the nameresolution on your system is not correctly.
What does a "nslookup setiathome.berkeley.edu" say.
Do you use a proxy server to connect to the internet ?
ID: 769190 · Report as offensive
chanueting
Volunteer tester

Send message
Joined: 24 May 08
Posts: 3
Credit: 2,162
RAC: 0
Hong Kong
Message 769507 - Posted: 17 Jun 2008, 14:27:19 UTC
Last modified: 17 Jun 2008, 15:09:02 UTC

I get following message:

[chanueting@localhost ~]$ nslookup setiathome.berkeley.edu
Server: 203.168.223.202
Address: 203.168.223.202#53

Non-authoritative answer:
setiathome.berkeley.edu canonical name = setiathome.SSL.berkeley.edu.
Name: setiathome.SSL.berkeley.edu
Address: 128.32.18.150

And I don't use any proxy, sounds strange.

Besides these, it is likely that I wrongly made the boinc client run on root. And there may be the problem. However, either do my account and root can show the above nslookup result.
ID: 769507 · Report as offensive
chanueting
Volunteer tester

Send message
Joined: 24 May 08
Posts: 3
Credit: 2,162
RAC: 0
Hong Kong
Message 770830 - Posted: 20 Jun 2008, 14:43:24 UTC
Last modified: 20 Jun 2008, 14:44:22 UTC

I don't know what was happening, after I have built a cc_config.xml includes:


<cc_config>
<log_flags>
<http_debug>1</http_debug>
</log_flags>
</cc_config>

BOINC client suddenly worked again. I don't know if the http_debug solve the problem, but it may help the others who can do nothing besides waiting for DNS recovery.

You may also have a look for http://boinc.berkeley.edu/wiki/Client_configuration
ID: 770830 · Report as offensive

Questions and Answers : Unix/Linux : Couldn't resolve host name


 
©2016 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.