Alright, I have been having trouble getting my FreeBSD machine working with BOINC.

My first question: Is there a difference between the RPC scheduler at http://setiboincdata.ssl.... and http://setiboinc.ssl...?

I just noticed that on my other two machines its the second URL but for the BSD machine it was the first.

If I use the second one it says that my platform isn't found. (i386-portbld-freebsd5.3)

I've been trying to get it working for the past two days and I still haven't been able to get work units even though my other two machines are running fine.

---

Hi I had kind of the same problems

<a>http://setiweb.ssl.berkeley.edu/forum_thread.php?id=11990[/url]

Make sure you have the compiled
setiathome_4.7_i386-portbld-freebsd5.3 executable
and app_info.xml in your
/var/db/boinc/projects/setiathome.berkeley.edu/ folder

---

Alright, I am totally confused. I'm new with freebsd, and I have the files there, though I have no clue how they got there. I was trying to run it out of my /usr/local/boinc directory, and I'm pretty sure it was a different version then 4.7.

And what looks to be the executable file there doesn't do anything.

Edit: Yeah, I had been trying to run version 4.19.

Does only 4.7 work with freebsd?

---

I am having the same issue: "platform 'i386-portbld-freebsd5.4' not found"
All files appear to be in the correct location...

The latest versions of the boinc and seti ports for FreeBSD can be found here:

http://opal.com/boinc/

These versions have also been submitted as FreeBSD port updates and are awaiting commits to the CVS.

Just wonder if anyone has had any luck with bsd 5.3 or high and boinc yet?

Tried numerious suggestions only to lead to the "not found" problem still coming from the schedulers.

Tried writing my own app_info.xml which failed horribly, anyone have one they could send me that works with bsd 5.3 so that I can look at to see as to what I did wrong?

---

Yes, boinc and seti work on FreeBSD 5.3. They work on all of FreeBSD 4.x, 5.x and 6.x and on all FreeBSD platforms (i386, alpha, sparc64, amd64 and ia64), although the GUI does not work on 4.x.

The latest ported boinc and seti versions are now in the FreeBSD ports tree. If you want to run boinc and seti on FreeBSD, you should get the latest FreeBSD port.

Instructions for how to get them, install them properly, and use them are here: http://opal.com/boinc/.

You don't need to be writing your own app_info.xml. One is included in the port.

These are not the absolute latest available from the nightly builds on the boinc and seti web sites, but they are the latest versions which are known to run properly on FreeBSD. From time to time, there can be problems with the recent nightly versions that cause them not to work properly. I am therefore only updating the FreeBSD port every few months, once I have been able to verify that a new version does work OK, and then only if there have been any significant changes in the code to make a new port worthwhile.

As of 2005/04/14, the latest FreeBSD ports are:
net/boinc-client.4.67.20050320
astro/boinc-setiathome.4.07.20050218
To get these, you will need to cvsup the latest port and compile it (see the instructions) to get the current port version. The binary packages are still one port version behind. By next week or so, the binary package will have been updated too.

For those interested in the port update process, it is this.

- The boinc or seti folk make changes to their code on an ongoing basis. Those changes are immediately available from their CVS and in their nightly tarballs.

- Every couple of months or so, I take a look at the latest code and compare it to the last FreeBSD port. If there are significant changes, I go ahead and make a new FreeBSD port.

- Making a new port involves figuring out what patches, if any, are needed to get the latest code to work on FreeBSD. Such patches are sent back to the boinc and seti folk for inclusion in the main code. This iterative patching and testing process can take anything from a day or so, to several weeks, depending on what problems are found. During this time, development versions of the new port are available on the opal.com web site.

- Once the new FreeBSD port is ready, I submit it to the FreeBSD GNATS system. It will wait there until a FreeBSD Committer gets to it, usually 1-2 weeks. During this time, the new port is available on the opal.com web site.

- The FreeBSD Committer reviews the port changes and commits them to the FreeBSD CVS tree. Within a day or so, the new port becomes available on all FreeBSD mirrors. It is then available for download using cvsup.

- The FreeBSD compilation engine will subsequently produce binary packages for all supported FreeBSD platforms. It takes another 1-2 weeks before all binary packages are updated to the latest port version. These can then be installed using pkg_add.

Enjoy.

> I am having the same issue: "platform 'i386-portbld-freebsd5.4' not found"
> All files appear to be in the correct location...
>

Hi,

here are the same problems using the current-ports (4.67 & 4.07):

2005-04-15 17:42:46 [---] Starting BOINC client version 4.67 for i386-portbld-freebsd5.4
2005-04-15 17:42:46 [http://setiathome.berkeley.edu/] Using your default project prefs
2005-04-15 17:42:46 [http://setiathome.berkeley.edu/] Host ID not assigned yet
2005-04-15 17:42:46 [---] No general preferences found - using BOINC defaults
2005-04-15 17:42:46 [---] Insufficient work; requesting more
2005-04-15 17:42:48 [---] Insufficient work; requesting more
2005-04-15 17:42:48 [http://setiathome.berkeley.edu/] Requesting 8640.00 seconds of work
2005-04-15 17:42:48 [http://setiathome.berkeley.edu/] Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2005-04-15 17:42:50 [http://setiathome.berkeley.edu/] Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
2005-04-15 17:42:50 [SETI@home] Message from server: platform 'i386-portbld-freebsd5.4' not found
2005-04-15 17:42:50 [SETI@home] Deferring communication with project for 23 hours, 59 minutes, and 59 seconds
2005-04-15 17:42:50 [SETI@home] Deferring communication with project for 23 hours, 59 minutes, and 59 seconds

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

<app_info>
<app>
<name>setiathome</name>
</app>
<file_info>
<name>setiathome</name>
</file_info>
<app_version>
<app_name>setiathome</app_name>
<version_num>407</version_num>
<file_ref>
<file_name>setiathome</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>

---

The reason this is happening is because boinc is looking in the directory you are currently in (pwd) for the projects folder and other files. For this to work, you need to cd to the folder that contains the project folder for setiathome, i.e. /var/db/boinc BEFORE you execute the boinc-client commands.

Just remember - all paths for boinc are relative to the directory you are in when you execute the client command.

Once you are in that directory, execute boinc-client and it should pick up the app_info.xml file and set your platform to be anonymous.

If you want to have boinc run from the same directory as the other 10 machines you run it on (like me) then you simply need to set up symbolic links. I run the client from a directory called /boinc (how imaginitive right?). When I run it and attach to the setiathome project I end up with:

/boinc/projects

In there you have the URL of the project - in my case it is:

/boinc/projects/setiathome.berkeley.edu

cd to that folder and do the following:

ln -s /usr/local/lib/boinc/setiathome
ln -s /var/db/boinc/projects/setiathome.berkeley.edu/app_info.xml

Now - cd back to /boinc

And run boinc-client as before.

Hope it helps.....

A

---

One more thing - in the scenario I describe above, the following shell script allows you to start and stop this thing as a service - just stic this in your /etc/rc.d directory (for Linux it is /etc/init.d):

#!/bin/sh
# Script to start and stop the boinc client
BOINC_PATH="/boinc"

case "$1" in
start)
echo -n "Starting boinc client"
cd $BOINC_PATH
/usr/local/lib/boinc/boinc-client -return_results_immediately >boinc.log 2>/dev/null&
;;

stop) echo -n "Stopping boinc client"
killall boinc-client
;;

*)
echo "Usage: $0 {start|stop}"
exit 1
esac

exit 0

---

> The reason this is happening is because boinc is looking in the directory you
> are currently in (pwd) for the projects folder and other files. For this to
> work, you need to cd to the folder that contains the project folder for
> setiathome, i.e. /var/db/boinc BEFORE you execute the boinc-client commands.
>
[...]
>
> Hope it helps.....
>

No, sorry... I've started boinc in /var/db/boinc/, in /var/db/boinc/projects/setiathome.berkeley.edu/ and other places with the same issue :-| (on two machines).

> > The reason this is happening is because boinc is looking in the directory
> you
> > are currently in (pwd) for the projects folder and other files. For this
> to
> > work, you need to cd to the folder that contains the project folder for
> > setiathome, i.e. /var/db/boinc BEFORE you execute the boinc-client
> commands.
> >
> [...]
> >
> > Hope it helps.....
> >
>
> No, sorry... I've started boinc in /var/db/boinc/, in
> /var/db/boinc/projects/setiathome.berkeley.edu/ and other places with the same
> issue :-| (on two machines).
>
Argl, it was a wrong homedir-entry of the boinc-user in /etc/master.passwd.

It works now.

---

On a Fresh 'All' install (i386, 5.4-release, and 5.3-release (both yeild the same result), including ports tree) I did a cvsup for the ports tree.

cd /usr/ports/astro/boinc-setiathome
make install


It compiles all the libraries fine, and gets down to the setiathome package and:

===> Building for boinc-setiathome-4.07.20050218
gmake all-recursive
gmake[1]: Entering directory `/usr/ports/astro/boinc-setiathome/work/seti_boinc'
Making all in client
gmake[2]: Entering directory `/usr/ports/astro/boinc-setiathome/work/seti_boinc/client'
if c++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/X11R6/include -O -pipe -DHAVE_CONFIG_H -DTEXT_UI -DNDEBUG -DCLIENT -include ../config.h -I../db -I/usr/local/include/BOINC -D_THREAD_SAFE -pthread -I/usr/X11R6/include -D_THREAD_SAFE -pthread -I/usr/X11R6/include -D_THREAD_SAFE -pthread -I/usr/X11R6/include -D_THREAD_SAFE -pthread -I/usr/X11R6/include -I/usr/local/include -MT seti_boinc-main.o -MD -MP -MF ".deps/seti_boinc-main.Tpo" -c -o seti_boinc-main.o `test -f 'main.cpp' || echo './'`main.cpp; \
then mv -f ".deps/seti_boinc-main.Tpo" ".deps/seti_boinc-main.Po"; else rm -f ".deps/seti_boinc-main.Tpo"; exit 1; fi
In file included from :11:
./../config.h:403:23: std_fixes.h: No such file or directory
main.cpp:45:25: diagnostics.h: No such file or directory
main.cpp:46:18: util.h: No such file or directory
In file included from ../db/sqlrow.h:26,
from ../db/db_table.h:26,
from seti_header.h:33,
from s_util.h:105,
from main.cpp:47:
../db/xml_util.h:55:27: error_numbers.h: No such file or directory
In file included from ../db/sqlrow.h:26,
from ../db/db_table.h:26,
from seti_header.h:33,
from s_util.h:105,
from main.cpp:47:
../db/xml_util.h: In function `std::vector > xml_decode_field(const std::string&, const char*)':
../db/xml_util.h:846: error: `ERR_XML_PARSE' undeclared (first use this function)
../db/xml_util.h:846: error: (Each undeclared identifier is reported only once for each function it appears in.)
main.cpp:48:23: boinc_api.h: No such file or directory
main.cpp:50:20: reduce.h: No such file or directory
main.cpp:51:27: graphics_data.h: No such file or directory
main.cpp:52:26: graphics_api.h: No such file or directory
In file included from main.cpp:64:
sah_gfx.h:22:19: gutil.h: No such file or directory
In file included from sah_gfx.h:23,
from main.cpp:64:
sah_gfx_base.h: At global scope:
sah_gfx_base.h:36: error: expected class-name before '{' token
sah_gfx_base.h:38: error: `REDUCED_ARRAY' does not name a type
sah_gfx_base.h: In constructor `GRAPH_BUFFER::GRAPH_BUFFER()':
sah_gfx_base.h:45: error: class `GRAPH_BUFFER' does not have any field named `GRAPHICS_BUFFER'
sah_gfx_base.h:45: error: class `GRAPH_BUFFER' does not have any field named `rarray'
sah_gfx_base.h: At global scope:
sah_gfx_base.h:58: error: `GRAPH_STYLE' does not name a type
sah_gfx_base.h:81: error: `STARFIELD' does not name a type
sah_gfx_base.h:82: error: `TEXTURE_DESC' does not name a type
sah_gfx_base.h:83: error: `TEXTURE_DESC' does not name a type
sah_gfx_base.h:84: error: `TEXTURE_DESC' does not name a type
sah_gfx_base.h:85: error: `APP_INIT_DATA' does not name a type
sah_gfx_base.h:86: error: `GRAPHICS_DOUBLE_BUFFER' does not name a type
In file included from main.cpp:64:
sah_gfx.h:34: error: `PROGRESS' does not name a type
sah_gfx.h:35: error: `PROGRESS' does not name a type
sah_gfx.h:36: error: `PROGRESS_2D' does not name a type
sah_gfx.h:37: error: `RIBBON_GRAPH' does not name a type
sah_gfx.h:38: error: `RIBBON_GRAPH' does not name a type
sah_gfx.h:39: error: `MOVING_TEXT_PANEL' does not name a type
main.cpp: In function `int main(int, char**)':
main.cpp:201: error: `BOINC_DIAG_DUMPCALLSTACKENABLED' undeclared (first use this function)
main.cpp:202: error: `BOINC_DIAG_HEAPCHECKENABLED' undeclared (first use this function)
main.cpp:203: error: `BOINC_DIAG_TRACETOSTDERR' undeclared (first use this function)
main.cpp:204: error: `BOINC_DIAG_REDIRECTSTDERR' undeclared (first use this function)
main.cpp:206: error: `boinc_init_diagnostics' undeclared (first use this function)
main.cpp:219: error: `boinc_init_graphics' undeclared (first use this function)
main.cpp:226: error: `boinc_init' undeclared (first use this function)
gmake[2]: *** [seti_boinc-main.o] Error 1
gmake[2]: Leaving directory `/usr/ports/astro/boinc-setiathome/work/seti_boinc/client'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/ports/astro/boinc-setiathome/work/seti_boinc'
gmake: *** [all] Error 2
*** Error code 2

Stop in /usr/ports/astro/boinc-setiathome.



This is a fresh install, with a fresh copy of the ports tree? what the hell went wrong? I reinstalled the box twice under 5.3-release, with the exact same problem.

--Dave

---

On a Fresh 'All' install (i386, 5.4-release, and 5.3-release (both yeild the same result), including ports tree) I did a cvsup for the ports tree.

cd /usr/ports/astro/boinc-setiathome
make install

It compiles all the libraries fine, and gets down to the setiathome package and:



Stop in /usr/ports/astro/boinc-setiathome.

This is a fresh install, with a fresh copy of the ports tree? what the hell went wrong? I reinstalled the box twice under 5.3-release, with the exact same problem.

--Dave

I found a working solution, for the moment.

1) Grab the latest binary ports for boinc-client and boinc-setiathome from your closest 4.11-release mirror. These binaries don't exist in the 5.3-release or 5.4-release port directories on your mirror for whatever reason.

Working URLs:
http://ftp://ftp3.freebsd.org/pub/FreeBSD/ports/i386/packages-4.11-release/net/boinc-client-4.13_2.tgz
http://ftp://ftp3.freebsd.org/pub/FreeBSD/ports/i386/packages-4.11-release/astro/boinc-setiathome-4.07.tgz

2) Install these using pkg_add .tgz from a rootshell.

3) Run boinc-client from a rootshell, register, and you're all set.

Worked for me at least, hope it helps somebody else.


--Dave

---