Hello everyone, i have 2 x86(i686) linux machines running client V.6.6.36(and beta 6.10.4, i like to test beta's :D)
Im am no noob when it comes to Linux, Boinc, or networks...

im running all my clients on daemon processes for i can manage them remotely... problem is...

when ever i try to add a project(any for that matter) Via the GUI or boinccmd(locally or via SSH)i get the following.

=================

Sun 13 Sep 2009 02:11:19 PM EDT||Fetching configuration file from http://spin.fh-bielefeld.de/get_project_config.php
Sun 13 Sep 2009 02:11:57 PM EDT||Fetching configuration file from http://setiathome.berkeley.edu/get_project_config.php
Sun 13 Sep 2009 02:12:57 PM EDT||Project communication failed: attempting access to reference site
Sun 13 Sep 2009 02:12:58 PM EDT||Internet access OK - project servers may be temporarily down.
Sun 13 Sep 2009 02:20:03 PM EDT||Fetching configuration file from http://einstein.phys.uwm.edu/get_project_config.php
Sun 13 Sep 2009 02:21:23 PM EDT||Project communication failed: attempting access to reference site
Sun 13 Sep 2009 02:21:24 PM EDT||Internet access OK - project servers may be temporarily down.
========================================

i cant seem to figure it out(i know the project servers are up for sure, so thats not the problem) and im at a loss.

ill post full stdout logs here... http://kingtiger01.dyndns.org/BOINC/logs/

Server1 is my wifes laptop(not really a server, but dubbed it for simplicity)

Server2 is my actual Server(older P4-478)

both are running Ubuntu-9.10(Karmic), and everything is in functioning order... again, leaving me confused and at a loss.

im in the process of attempting to attach SETI@HOME to my x64 windows workstation to find-out if its relative to just these two boxes.

--

Any and all assistance and/or Suggestions welcomed!

---

~Seems like nothing ever changes~

windows box attached fine...(X64 6.10.4)

---

~Seems like nothing ever changes~

Did you allow BOINC to pass through the firewall on ports 80 and 443?

---

yes, ofcourse. one of the first things i made sure of.

---

~Seems like nothing ever changes~

i'll post full stdout logs here... http://kingtiger01.dyndns.org/BOINC/logs/

I made your link active, but you should turn on some debug log_flags.

13-Sep-2009 13:37:18 [---] log flags: task, file_xfer, sched_ops

is a bit meagre.

Also I read in another thread that ubuntu might need the <http_1_0>1</http_1_0> clause in the <options> section of cc_config.xml.

Gruß,
Gundolf
[edit]I just found my answer at Einstein. I thought I had missed to press "Post reply" before quitting the browser, so I "invented" it again :-)[/edit]

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

SETI@home classic workunits 3,758
SETI@home classic CPU time 66,520 hours

already did, was just getting around to putting it in there.

same place, just debug folder now...

---

as far as HTTP-1.0, compatibility. i tried that already, before posting anything here. thinking it could be a possibility.

realised fast though it made no difference.

--

on as side note, i tested this on a development server(Debian Sid) and same affect... so its got me puzzeled even more, im going to see if i can find my old ubuntu hardy disc's and run it on a old workstation to detirmine if its a problem with libcurl or zlib, as there may of been a patch in the last 6 months that have caused this issue.

---

~Seems like nothing ever changes~