I have installed the 4.07 seti and 4.68 boinc-client ports on my FreeBSD 6 machine. Opening a Terminal window and typing 'boincmgr' results in this output:

connect: Can't assign requested address
idprio: idprio: Operation not permitted
connect: Can't assign requested address

The Boinc Manager does launch with the message of 'connecting to localhost' in the bottom right corner. A few minutes pass and a dialog pops up stating 'connection failed'. This also adds another line to the Terminal window:

RPC_CLIENT init timed out

I have entered in the url and account keys I was sent from both seti and rosetta with the same results. I read through man boinc, but nothing in it jumped out as an answer to my connection problems. The install did create a boinc user, so I don't think that's the problem (though the permissions of the various files and folders is still confusing). I have Googled and read through the boards but with so many platforms and client / manager vintages, I'm not sure what to try next.

---

Looks like your boinc manager can not communicate with the boinc client.
The setup of the communication is described in detail in this posting : http://setiathome.berkeley.edu/forum_thread.php?id=23845#202309

---

Looks like your boinc manager can not communicate with the boinc client.
The setup of the communication is described in detail in this posting : http://setiathome.berkeley.edu/forum_thread.php?id=23845#202309

I assume this centers around the file gui_rpc_auth.cfg. I could not find this file by searching the file system - though perhaps I'm not setting the search correctly. One of the posts in the thread you refer to mentions this file should be placed in the Boinc install folder, but searching for the word boinc in my file system yields a myriad of folders. I created a file in gedit (with plain/text encoding), pasted my seti Account key along with a carriage return and saved this file in the same folder as boincmgr (/usr/local/bin). As root, I also changed the file gui_rpc_auth.cfg permissions file owner boinc - BOINC and file group nobody. Restarting as my normal user account and issuing boincmgr via Terminal yields the same connection problems. I suspect I have placed this file in the wrong folder, but I have no idea where it should be located.

---

I suspect I have placed this file in the wrong folder, but I have no idea where it should be located.

The file should be in the directory, where the boinc_client is.
You can also try to start the boinc client with the option "-allow_remote_gui_rpc".

---

I suspect I have placed this file in the wrong folder, but I have no idea where it should be located.

The file should be in the directory, where the boinc_client is.
You can also try to start the boinc client with the option "-allow_remote_gui_rpc".

$boinc -allow_remote_gui_rpc
idprio: idprio: Operation not permitted

$ su
Password:
FreeBeastie# boinc -allow_remote_gui_rpc
2006-01-07 16:28:53 [---] Another instance of BOINC is running

I'll try moving the gui_rpc_auth.cfg file now.
<update>
Moving the file made no difference.

---

$boinc -allow_remote_gui_rpc
idprio: idprio: Operation not permitted

$ su
Password:
FreeBeastie# boinc -allow_remote_gui_rpc
2006-01-07 16:28:53 [---] Another instance of BOINC is running

I'll try moving the gui_rpc_auth.cfg file now.

This "idprio" is BSD specific. - Never heared before. The only hints, I have found are these thread : http://setiathome.berkeley.edu/forum_thread.php?id=13976. - But running it as root is not a good idea.

Are You attached to the project ? - If not, can you manualy attach to the project (boinc_client -attach_project http://setiathome.berkeley.edu $ACCOUNT_KEY) ?

I will search around, if I find some more about the idprio problems...

---

$boinc -allow_remote_gui_rpc
idprio: idprio: Operation not permitted

$ su
Password:
FreeBeastie# boinc -allow_remote_gui_rpc
2006-01-07 16:28:53 [---] Another instance of BOINC is running

I'll try moving the gui_rpc_auth.cfg file now.

This "idprio" is BSD specific. - Never heared before. The only hints, I have found are these thread : http://setiathome.berkeley.edu/forum_thread.php?id=13976. - But running it as root is not a good idea.

Are You attached to the project ? - If not, can you manualy attach to the project (boinc_client -attach_project http://setiathome.berkeley.edu $ACCOUNT_KEY) ?

I will search around, if I find some more about the idprio problems...

$ boinc_client -attach_project http://setiathome.berkeley.edu $ACCOUNT_KEY
boinc_client: not found

$ boinc -attach_project http://setiathome.berkeley.edu $ACCOUNT_KEY
idprio: idprio: Operation not permitted

---

$boinc -allow_remote_gui_rpc
idprio: idprio: Operation not permitted

$ su
Password:
FreeBeastie# boinc -allow_remote_gui_rpc
2006-01-07 16:28:53 [---] Another instance of BOINC is running

I'll try moving the gui_rpc_auth.cfg file now.

This "idprio" is BSD specific. - Never heared before. The only hints, I have found are these thread : http://setiathome.berkeley.edu/forum_thread.php?id=13976. - But running it as root is not a good idea.

Are You attached to the project ? - If not, can you manualy attach to the project (boinc_client -attach_project http://setiathome.berkeley.edu $ACCOUNT_KEY) ?

I will search around, if I find some more about the idprio problems...

I tried the following...

$ boinc -allow_remote_gui_rpc
idprio: idprio: Operation not permitted
$ su
Password:
FreeBeastie# boinc -allow_remote_gui_rpc
2006-01-07 18:03:59 [---] Starting BOINC client version 4.68 for i386-portbld-fr eebsd6.0
2006-01-07 18:03:59 [---] Data directory: /var/db/boinc
2006-01-07 18:03:59 [SETI@home] Computer ID: <removed my number>; location: home; project pr efs: default
2006-01-07 18:03:59 [---] No general preferences found - using BOINC defaults
2006-01-07 18:03:59 [---] Remote control allowed
2006-01-07 18:03:59 [SETI@home] Deferring communication with project for 4 hours , 56 minutes, and 56 seconds
2006-01-07 18:03:59 [SETI@home] Deferring communication with project for 4 hours , 56 minutes, and 56 seconds
2006-01-07 18:03:59 [---] Insufficient work; requesting more

I'm not sure it is hung, waiting, working, or what. Not too thrilled about having an open Terminal as root though

---

$boinc -allow_remote_gui_rpc
idprio: idprio: Operation not permitted

$ su
Password:
FreeBeastie# boinc -allow_remote_gui_rpc
2006-01-07 16:28:53 [---] Another instance of BOINC is running

I'll try moving the gui_rpc_auth.cfg file now.

This "idprio" is BSD specific. - Never heared before. The only hints, I have found are these thread : http://setiathome.berkeley.edu/forum_thread.php?id=13976. - But running it as root is not a good idea.

Are You attached to the project ? - If not, can you manualy attach to the project (boinc_client -attach_project http://setiathome.berkeley.edu $ACCOUNT_KEY) ?

I will search around, if I find some more about the idprio problems...

I tried the following...

$ boinc -allow_remote_gui_rpc
idprio: idprio: Operation not permitted
$ su
Password:
FreeBeastie# boinc -allow_remote_gui_rpc
2006-01-07 18:03:59 [---] Starting BOINC client version 4.68 for i386-portbld-fr eebsd6.0
2006-01-07 18:03:59 [---] Data directory: /var/db/boinc
2006-01-07 18:03:59 [SETI@home] Computer ID: <removed my number>; location: home; project pr efs: default
2006-01-07 18:03:59 [---] No general preferences found - using BOINC defaults
2006-01-07 18:03:59 [---] Remote control allowed
2006-01-07 18:03:59 [SETI@home] Deferring communication with project for 4 hours , 56 minutes, and 56 seconds
2006-01-07 18:03:59 [SETI@home] Deferring communication with project for 4 hours , 56 minutes, and 56 seconds
2006-01-07 18:03:59 [---] Insufficient work; requesting more

I'm not sure it is hung, waiting, working, or what. Not too thrilled about having an open Terminal as root though

---

sorry for the duplicate posts

---

$boinc -allow_remote_gui_rpc
idprio: idprio: Operation not permitted

$ su
Password:
FreeBeastie# boinc -allow_remote_gui_rpc
2006-01-07 16:28:53 [---] Another instance of BOINC is running

I'll try moving the gui_rpc_auth.cfg file now.

This "idprio" is BSD specific. - Never heared before. The only hints, I have found are these thread : http://setiathome.berkeley.edu/forum_thread.php?id=13976. - But running it as root is not a good idea.

Are You attached to the project ? - If not, can you manualy attach to the project (boinc_client -attach_project http://setiathome.berkeley.edu $ACCOUNT_KEY) ?

I will search around, if I find some more about the idprio problems...

I tried the following...

$ boinc -allow_remote_gui_rpc
idprio: idprio: Operation not permitted
$ su
Password:
FreeBeastie# boinc -allow_remote_gui_rpc
2006-01-07 18:03:59 [---] Starting BOINC client version 4.68 for i386-portbld-fr eebsd6.0
2006-01-07 18:03:59 [---] Data directory: /var/db/boinc
2006-01-07 18:03:59 [SETI@home] Computer ID: <removed my number>; location: home; project pr efs: default
2006-01-07 18:03:59 [---] No general preferences found - using BOINC defaults
2006-01-07 18:03:59 [---] Remote control allowed
2006-01-07 18:03:59 [SETI@home] Deferring communication with project for 4 hours , 56 minutes, and 56 seconds
2006-01-07 18:03:59 [SETI@home] Deferring communication with project for 4 hours , 56 minutes, and 56 seconds
2006-01-07 18:03:59 [---] Insufficient work; requesting more

I'm not sure it is hung, waiting, working, or what. Not too thrilled about having an open Terminal as root though

this is what I now have as output from the Terminal window:

2006-01-07 22:04:01 [---] Insufficient work; requesting more
2006-01-07 23:00:55 [SETI@home] Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2006-01-07 23:00:55 [SETI@home] Requesting 8640 seconds of work, returning 0 results
2006-01-07 23:00:57 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
2006-01-07 23:00:57 [SETI@home] Message from server: platform 'i386-portbld-freebsd6.0' not found

Platform not found? Then why are the ports available?

---

2006-01-07 22:04:01 [---] Insufficient work; requesting more
2006-01-07 23:00:55 [SETI@home] Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2006-01-07 23:00:55 [SETI@home] Requesting 8640 seconds of work, returning 0 results
2006-01-07 23:00:57 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
2006-01-07 23:00:57 [SETI@home] Message from server: platform 'i386-portbld-freebsd6.0' not found

Platform not found? Then why are the ports available?

You must compile or install the binary of the seti app from the ports, and place a file called "app_info.xml" in the directory "projects/setiathome.berkeley.edu".
Please look at this threads :
http://setiathome.berkeley.edu/forum_thread.php?id=12150
http://setiathome.berkeley.edu/forum_thread.php?id=22282
http://setiweb.ssl.berkeley.edu/forum_thread.php?id=12150

---

2006-01-07 22:04:01 [---] Insufficient work; requesting more
2006-01-07 23:00:55 [SETI@home] Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2006-01-07 23:00:55 [SETI@home] Requesting 8640 seconds of work, returning 0 results
2006-01-07 23:00:57 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
2006-01-07 23:00:57 [SETI@home] Message from server: platform 'i386-portbld-freebsd6.0' not found

Platform not found? Then why are the ports available?

You must compile or install the binary of the seti app from the ports, and place a file called "app_info.xml" in the directory "projects/setiathome.berkeley.edu".
Please look at this threads :
http://setiathome.berkeley.edu/forum_thread.php?id=12150
http://setiathome.berkeley.edu/forum_thread.php?id=22282
http://setiweb.ssl.berkeley.edu/forum_thread.php?id=12150

ran make deinstall on both ports
cvsup both ports
make
make install on both ports

app_info.xml does exist in folder /var/db/boinc/projects/setiathome.berkeley.edu (along with a shortcut to the setiathome executable).

Added the following entries to /etc/rc.conf:

# Boinc - Setiathome parameters
boinc_enable="YES"
boinc_flags="-allow_remote_gui_rpc -redirectio"
boinc -attach_project http://setiathome.berkeley.edu/ my seti account key
Note I have one blank space between the last '/' and my number.

Restarting caused a panic and core dump. In retrospect, I assume boinc was running while I was de/installing the ports, causing the crash at shutdown. How does one stop a running boinc?

The restore/repair operations during the restart allowed time to read some of the screen outputs. There were several entries of 'BOINC: NOT FOUND'. That may not be the exact terminology as I didn't write it down.

Logged back in under my normal user account and tried 'boincmgr' in Terminal. Same results as before.

---

I think, it is the best way, to recompile the boinc and the seti app again.
Hard to say, why you get a crashing binary now....

Then create the file app_info.xml. The sample of the file you will find here : http://boinc.berkeley.edu/anonymous_platform.php. The "setiathome_4.07_windows_intelx86.exe" should be changed to the exatly name of your binary.

Now you can attach to the project via the commandline "boinc -attach_project setiathome.berkeley.edu $ACCOUNT_KEY"

If you do the start process and attach project within a normal terminal, you will see all debuging messages.

---

I think, it is the best way, to recompile the boinc and the seti app again.
Hard to say, why you get a crashing binary now....

Then create the file app_info.xml. The sample of the file you will find here : http://boinc.berkeley.edu/anonymous_platform.php. The "setiathome_4.07_windows_intelx86.exe" should be changed to the exatly name of your binary.

Now you can attach to the project via the commandline "boinc -attach_project setiathome.berkeley.edu $ACCOUNT_KEY"

If you do the start process and attach project within a normal terminal, you will see all debuging messages.

This is a copy of my /var/db/boinc/projects/setiathome.berkeley.edu/app_info.xml file:
−
<app_info>
−
<app>
<name>setiathome</name>
</app>
−
<file_info>
<name>setiathome</name>
<executable/>
</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>

"recompile the boinc and the seti app again" Please explain how do this if it is different from the make / make install process.

Tried the attach project procedure:

$ boinc -attach_project setiathome.berkeley.edu $ACCOUNT_KEY
idprio: idprio: Operation not permitted
$ su
Password:
FreeBeastie# boinc -attach_project setiathome.berkeley.edu $ACCOUNT_KEY
ACCOUNT_KEY: Undefined variable.

---

This is a copy of my /var/db/boinc/projects/setiathome.berkeley.edu/app_info.xml file:
−
<app_info>
−
<app>
<name>setiathome</name>
</app>
−
<file_info>
<name>setiathome</name>
<executable/>
</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>

Name and filename in the app_info.xml should be the exactly name of the setiathome binary.

$ boinc -attach_project setiathome.berkeley.edu $ACCOUNT_KEY
idprio: idprio: Operation not permitted
$ su
Password:
FreeBeastie# boinc -attach_project setiathome.berkeley.edu $ACCOUNT_KEY
ACCOUNT_KEY: Undefined variable.

$ACCOUNT_KEY is your account key. Please put in here the account key you get mailed from the project.

---

This is a copy of my /var/db/boinc/projects/setiathome.berkeley.edu/app_info.xml file:
−
<app_info>
−
<app>
<name>setiathome</name>
</app>
−
<file_info>
<name>setiathome</name>
<executable/>
</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>

Name and filename in the app_info.xml should be the exactly name of the setiathome binary.

$ boinc -attach_project setiathome.berkeley.edu $ACCOUNT_KEY
idprio: idprio: Operation not permitted
$ su
Password:
FreeBeastie# boinc -attach_project setiathome.berkeley.edu $ACCOUNT_KEY
ACCOUNT_KEY: Undefined variable.

$ACCOUNT_KEY is your account key. Please put in here the account key you get mailed from the project.

The executable name is setiathome. Is it required to append the path to this executable (/usr/local/lib/boinc/) in the app_info.xml file?

I tried the -attach_project commands with my actual account key. As normal user, the result is:
idprio: idprio: Operation not permitted
As su, the result is:
2006-01-08 14:13:08 [---] Another instance of BOINC is running

Do I have to stop boinc first? And again, how is that done?

---

The executable name is setiathome. Is it required to append the path to this executable (/usr/local/lib/boinc/) in the app_info.xml file?

The full path is not good. It work with the name of the binary.

I tried the -attach_project commands with my actual account key. As normal user, the result is:
idprio: idprio: Operation not permitted
As su, the result is:
2006-01-08 14:13:08 [---] Another instance of BOINC is running

Do I have to stop boinc first? And again, how is that done?

Yes. Please kill the boinc process, and remove the lockfile in the boinc directory. Then you cold start the boinc client again (with the attach parameters).

---

The executable name is setiathome. Is it required to append the path to this executable (/usr/local/lib/boinc/) in the app_info.xml file?

The full path is not good. It work with the name of the binary.

I tried the -attach_project commands with my actual account key. As normal user, the result is:
idprio: idprio: Operation not permitted
As su, the result is:
2006-01-08 14:13:08 [---] Another instance of BOINC is running

Do I have to stop boinc first? And again, how is that done?

Yes. Please kill the boinc process, and remove the lockfile in the boinc directory. Then you cold start the boinc client again (with the attach parameters).

as root, deleted lockfile (empty, 0kb?)

FreeBeastie# killall boinc-client
No matching processes were found
FreeBeastie# boinc -attach_project http://setiathome.berkeley.edu mynumber
2006-01-08 14:45:12 [---] Starting BOINC client version 4.68 for i386-portbld-freebsd6.0
2006-01-08 14:45:12 [---] Data directory: /var/db/boinc
2006-01-08 14:45:12 [SETI@home] Found app_info.xml; using anonymous platform
2006-01-08 14:45:12 [---] Already attached to http://setiathome.berkeley.edu/
2006-01-08 14:45:12 [---] Already attached to http://setiathome.berkeley.edu/
2006-01-08 14:45:12 [SETI@home] Computer ID: xxxxxxx; location: home; project prefs: default
2006-01-08 14:45:12 [---] No general preferences found - using BOINC defaults
2006-01-08 14:45:12 [---] Remote control not allowed; using loopback address
2006-01-08 14:45:12 [---] GUI RPC bind failed: -1
2006-01-08 14:45:12 [---] GUI RPC bind failed: -1
gstate.init() failed: -180

I erased my account number and computer ID number after I pasted the above.

---

The executable name is setiathome. Is it required to append the path to this executable (/usr/local/lib/boinc/) in the app_info.xml file?

The full path is not good. It work with the name of the binary.

I tried the -attach_project commands with my actual account key. As normal user, the result is:
idprio: idprio: Operation not permitted
As su, the result is:
2006-01-08 14:13:08 [---] Another instance of BOINC is running

Do I have to stop boinc first? And again, how is that done?

Yes. Please kill the boinc process, and remove the lockfile in the boinc directory. Then you cold start the boinc client again (with the attach parameters).

as root, deleted lockfile (empty, 0kb?)

FreeBeastie# killall boinc-client
No matching processes were found
FreeBeastie# boinc -attach_project http://setiathome.berkeley.edu mynumber
2006-01-08 14:45:12 [---] Starting BOINC client version 4.68 for i386-portbld-freebsd6.0
2006-01-08 14:45:12 [---] Data directory: /var/db/boinc
2006-01-08 14:45:12 [SETI@home] Found app_info.xml; using anonymous platform
2006-01-08 14:45:12 [---] Already attached to http://setiathome.berkeley.edu/
2006-01-08 14:45:12 [---] Already attached to http://setiathome.berkeley.edu/
2006-01-08 14:45:12 [SETI@home] Computer ID: xxxxxxx; location: home; project prefs: default
2006-01-08 14:45:12 [---] No general preferences found - using BOINC defaults
2006-01-08 14:45:12 [---] Remote control not allowed; using loopback address
2006-01-08 14:45:12 [---] GUI RPC bind failed: -1
2006-01-08 14:45:12 [---] GUI RPC bind failed: -1
gstate.init() failed: -180

I erased my account number and computer ID number after I pasted the above.

It should be "killall -9 boinc_client" ;)

---

Join BOINC United now!