Hi,

I have boinc software installed on
FreeBSD-5.4RELEASE and FreeBSD-6.0RELEASE
from ports.

But all the time I try to run it, I get
message that communication is deferred
for almost 24h. After 24 communication gets deferred
again :-(

---

I have boinc software installed on FreeBSD-5.4RELEASE and FreeBSD-6.0RELEASE
from ports.

But all the time I try to run it, I get message that communication is deferred
for almost 24h. After 24 communication gets deferred again :-(

It could be normal, if you use the anonymous plaftorm mechanism.
Could you please post the output from the boinc client here.

---

Let me jump in on this thread. I am now running boincmgr (and boinc-client in the background) on a FreeBSD-6.0 system and I too am getting the incessant "deferring communication for 23 hrs, 59 mins" messages. I also get this message (not verbatim because the 'copy messages' is not copying them anywhere a paste can get to, like this text box):

Message from server:platform 'i386-portbuild-freebsd6.0' not found

---

Let me jump in on this thread. I am now running boincmgr (and boinc-client in the background) on a FreeBSD-6.0 system and I too am getting the incessant "deferring communication for 23 hrs, 59 mins" messages. I also get this message (not verbatim because the 'copy messages' is not copying them anywhere a paste can get to, like this text box):

Message from server:platform 'i386-portbuild-freebsd6.0' not found

As i understand this message you only build boinc from the "port" stuff but missed to build the actual setiathome application.

This is a common mistake. BOINC is NOT SETI@Home !
BOINC is just a "frontend" which controls various distrubuted projects like SETI@Home or Rosetta etc.

---

Join BOINC United now!

Let me jump in on this thread. I am now running boincmgr (and boinc-client in the background) on a FreeBSD-6.0 system and I too am getting the incessant "deferring communication for 23 hrs, 59 mins" messages. I also get this message (not verbatim because the 'copy messages' is not copying them anywhere a paste can get to, like this text box):

Message from server:platform 'i386-portbuild-freebsd6.0' not found

As i understand this message you only build boinc from the "port" stuff but missed to build the actual setiathome application.

This is a common mistake. BOINC is NOT SETI@Home !
BOINC is just a "frontend" which controls various distrubuted projects like SETI@Home or Rosetta etc.

You're right! I just decided to 'make deinstall' and I found out that

/var/db/boinc/projects/setiathome.berkeley.edu/app_info.xml and
/var/db/boinc/projects/setiathome.berkeley.edu/setiathome

were both missing. So I did a 'make deinstall' in both

/usr/ports/net/boinc-client and
/usr/ports/astro/boinc-setiathome

Then I did a 'make install' in boinc-client first followed by 'make install' in boinc-setiathome and things began to work. Then went back to both and did a 'make clean' For whatever reason, if I ran the boincmgr GUI it would crash after a couple seconds (made sure boinc-client was not running first). But if I started the boinc-client from the command line _then_ started boincmgr everything seemed to be fine.

This was all with 6.0-STABLE, buildworld-ed on 2005-12-04 and ports cvsup-ed on 2005-12-27.

In my case this solved my problem:
1) Use "http://setiathome.ssl.berkeley.edu" as the project URL.
2) Stop boinc and exit boincmgr
3) Create app_info.xml as instructed in http://boinc.berkeley.edu/anonymous_platform.php
4) Restart boinc and boincmgr

I had been waiting for 3 days without any work... now it's time to make this dual-core mobo sweat :)

---

In my case this solved my problem:
1) Use "http://setiathome.ssl.berkeley.edu" as the project URL.
2) Stop boinc and exit boincmgr
3) Create app_info.xml as instructed in http://boinc.berkeley.edu/anonymous_platform.php
4) Restart boinc and boincmgr

I had been waiting for 3 days without any work... now it's time to make this dual-core mobo sweat :)

Seems like I spoke too soon. Ok, I reinstalled several times boinc-setiathome from ports and eventually it worked, seems like the trick was installing, attaching to project, deinstalling, and reinstalling again and then starting again. Duh.

---