Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 14
Posts: 14   Pages: 2   [ 1 2 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1650 times and has 13 replies Next Thread
catchercradle
Senior Cruncher
England
Joined: Jan 16, 2009
Post Count: 171
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Unable to attach to project

I am running boinc 6.2.15 When I try to attach to a project at the bottom right hand corner it says connecting to localhost then goes back to disconnected. I have used boinc in the past without this issue occurring and can not work out what I am doing wrong.

Dave
[Jan 16, 2009 10:49:53 AM]   Link   Report threatening or abusive post: please login first  Go to top 
catchercradle
Senior Cruncher
England
Joined: Jan 16, 2009
Post Count: 171
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Unable to attach to project

Realized there is a more up to date client but same problem.
[Jan 16, 2009 11:04:32 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Richard Hollins
Cruncher
Joined: Nov 1, 2008
Post Count: 6
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Unable to attach to project

I have the same problem - I am running BOINC ver. 6.4.5 in Fedora 8. I have had to reinstall, after trying to upgrade (which being from a different repo was actually 6.2.x), and can get the client running as a service, but it is almost as if the manager cannot find the client.
[Jul 6, 2009 8:46:00 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: Unable to attach to project

yes, that can happen. Either the daemon is not running (BOINC.exe), or something is blocking the RPCs over port 31416 (localhost IP 127.0.0.1)
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
[Jul 6, 2009 8:50:47 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Unable to attach to project

http://wcg.wikia.com/wiki/Unable_to_connect_to_the_core_client

If you need further help, don't hesitate to ask.
[Jul 6, 2009 9:29:02 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Richard Hollins
Cruncher
Joined: Nov 1, 2008
Post Count: 6
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Unable to attach to project

I believe I have confirmed that boinc_client is running, but boincmgr will still not connect to it.

[root@localhost rich]# /etc/rc.d/init.d/boinc stop
Stopping BOINC client daemon: [ OK ]
[root@localhost rich]# /etc/rc.d/init.d/boinc start
The BOINC client requires initialization. [WARNING]
Starting BOINC client as a daemon: [ OK ]
[root@localhost rich]# pgrep -x boinc_client
[root@localhost rich]# pgrep -x boinc
[root@localhost rich]# pgrep -x /var/lib/boinc/boinc_client
[root@localhost rich]# pgrep -x /usr/local/bin/BOINC/boinc_client
[root@localhost rich]# pgrep -u root boinc_client
[root@localhost rich]# pgrep -u boinc
[root@localhost rich]# pgrep -u daemon
[root@localhost rich]#

Logged in as root, with the firewall disabled (I am behind a hardware firewall as well)

[root@localhost boinc]# /etc/rc.d/init.d/boinc stop
Stopping BOINC client daemon: [ OK ]
[root@localhost boinc]# /etc/rc.d/init.d/boinc start
The BOINC client requires initialization. [WARNING]
Starting BOINC client as a daemon: [ OK ]
[root@localhost boinc]# /var/lib/boinc/boincmgr
connect: Connection refused
execvp(/var/lib/boinc/boinc, --redirectio, --launched_by_manager) failed with error 2!
connect: Operation now in progress
connect: Connection refused
connect: Connection refused
execvp(/var/lib/boinc/boinc, --redirectio, --launched_by_manager) failed with error 2!
connect: Connection refused
[root@localhost boinc]#

This version of BOINC worked when not installed as a daemon. Where do I go from here?
[Jul 9, 2009 12:34:23 AM]   Link   Report threatening or abusive post: please login first  Go to top 
uplinger
Former World Community Grid Tech
Joined: May 23, 2005
Post Count: 3952
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Unable to attach to project

try these steps.

in the terminal

$ ps -ef | grep boinc

You should get something like this...
$ ps -ef | grep boinc
boinc 2761 1 0 Jul04 ? 00:13:55 /usr/bin/boinc --check_all_logins --redirectio --dir /var/lib/boinc-client

Also, what is in your /etc/rc.d/init.d/boinc file? it may help in figuring out what is happening.

-Uplinger
[Jul 9, 2009 12:49:11 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Richard Hollins
Cruncher
Joined: Nov 1, 2008
Post Count: 6
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Unable to attach to project

ps -ef | grep boinc

What I get is:

rich 25468 25440 0 02:33 pts/1 00:00:00 grep boinc

or as root:

root 25504 25482 0 02:36 pts/1 00:00:00 grep boinc
[Jul 13, 2009 9:40:29 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Richard Hollins
Cruncher
Joined: Nov 1, 2008
Post Count: 6
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Unable to attach to project

etc/rc.d/init.d/boinc:


#!/bin/sh
#
# BOINC - start and stop the BOINC client daemon on Unix
#
# Unix start/stop script to run the BOINC client as a daemon at
# system startup, as the 'boinc' user (not root!).
#
# This version works on Red Hat Linux, Fedora Core, Debian, Ubuntu, SUSE,
# Mandrake, and Slackware Linux, and should work on generic Linux systems
# provided that they have 'pidof' and a POSIX /bin/sh (most all do).
# Metadata for chkconfig and the SUSE equivalent INIT info are included below.
#
# Usage: boinc { start | stop | status | restart }
#
###
# chkconfig: 345 98 03
# description: This script starts the local BOINC client as a daemon
# For more information about BOINC (the Berkeley Open Infrastructure
# for Network Computing) see http://boinc.berkeley.edu
# processname: boinc
# config: /etc/sysconfig/boinc
#
### BEGIN INIT INFO
# Provides: boinc
# Required-Start: $network
# Required-Stop: $network
# Default-Start: 3 4 5
# Default-Stop: 0 1 2 6
# Description: This script starts the local BOINC client as a daemon
# For more information about BOINC (the Berkeley Open Infrastructure
# for Network Computing) see http://boinc.berkeley.edu
### END INIT INFO
#
# Eric Myers <myers@vassar.edu> - 27 July 2004
# Department of Physics and Astronomy, Vassar College, Poughkeepsie NY
# Eric Myers <myers@spy-hill.net>
# Spy Hill Research, Poughkeepsie, New York
# @(#) $Id: boinc,v 1.14 2008/07/14 12:52:34 myers Exp $
########################################################################

# Defaults, which can be overridden by putting new NAME=value lines
# in /etc/sysconfig/boinc (for Red Hat/Fedora Linux and variants)
# or /etc/default/boinc (for Debian/Ubuntu and variants)

# Name of user to run as:
#
BOINCUSER=boinc

# Working directory. Could be /home/boinc, /var/lib/boinc, etc..
# The reason /var/lib/boinc is preferable is that this works best for a
# cluster of computers whereas /home/anything might be shared between machines
#
BOINCDIR=/var/lib/boinc

# Name of the client executable. This is the file "boinc" if you
# unpacked the download file boinc_M.mm.rr_i686-pc-linux-gnu.sh,
# but I like to rename it and put it in a public place.
# (Hint: move boincmgr to /usr/local/bin too so anyone can easily use it).
#
BOINCEXE=/var/lib/boinc/boinc_client

# Log and error files (you should rotate these occasionally)
#
LOGFILE=boinc.log
ERRORLOG=error.log

# BOINC options for the command line when running the client.
# Be aware that --allow_remote_gui_rpc opens up your machine to the world!
# (Or at least to your local subnet)
#
#BOINCOPTS="--allow_remote_gui_rpc"
BOINCOPTS=""

# Deprecated. Was used to construct the executable name in days of old.
# (Still here just as a last ditch to find an old executable, but
# probably should be removed.)
#
BUILD_ARCH=i686-pc-linux-gnu


# Mandrake 10.1 really wants a subsys lock file ...
if [ -d /var/lock/subsys ]; then
LOCKDIR=/var/lock/subsys
elif [ -d /var/lock ]; then
LOCKDIR=/var/lock
fi

# su on Linux seems to need this to be set to work properly in a script
export TERM dumb


##
# Init script function library. This stuff is Red Hat specific,
# but if the functions are not found we create our own simple replacements.
# (The idea for replacing the functions comes from OpenAFS. Thanks guys!)

if [ -f /etc/rc.d/init.d/functions ] ; then
. /etc/rc.d/init.d/functions
##TODO: Try to use LSB here for systems that have it?
else
export PATH=/sbin:/bin:/usr/sbin:/usr/bin
echo_success () { echo -n " [ OK ] " ; }
echo_failure () { echo -n " [FAILED] " ; }
echo_warning () { echo -n " [WARNING] " ; }
killproc() {
PID=`pidof -s -x -o $$ -o $PPID -o %PPID $1`
[ $PID ] && kill $PID ; }
fi


## Look for any local configuration settings which override all above

if [ -f /etc/sysconfig/boinc ]; then
. /etc/sysconfig/boinc
elif [ -f /etc/default/boinc ]; then
. /etc/default/boinc
fi


## Verify the working directory exists:

if [ ! -d $BOINCDIR ]; then
echo -n "Cannot find BOINC directory $BOINCDIR "
echo_failure
echo
exit 7
fi


# Some additional places to look for the client executable
# (We do this after init.d/functions and sysconfig/boinc, which sets PATH)

export PATH=$BOINCDIR:/usr/local/bin:$PATH


## Locate the executable, either boinc_client, boinc,
## or boinc_M.mm_.... with highest version number
## We only do this if BOINCEXE set above isn't found or is not executable.

if [ ! -x $BOINCEXE ]; then
BOINCEXE=`/usr/bin/which boinc_client 2>/dev/null`
if [ ! -x "$BOINCEXE" ]; then
BOINCEXE=`/usr/bin/which boinc 2>/dev/null`
if [ ! -x "$BOINCEXE" ]; then
BOINCEXE=`/bin/ls -1 $BOINCDIR/boinc_*_$BUILD_ARCH 2>/dev/null | tail -1 `
fi
fi
fi

if [ ! -x "$BOINCEXE" ]; then
echo -n "Cannot find an executable for the BOINC client."
echo_failure
echo
exit 2
fi



## Functions: $1 is one of start|stop|status|restart

case "$1" in
start)
cd $BOINCDIR

if [ -f lockfile ] ; then
echo -n "Another instance of BOINC is running (lockfile exists)."
echo_failure
echo
exit 4
fi

if [ ! -d projects ] ; then
echo -n "The BOINC client requires initialization."
echo_warning
echo
fi

echo -n "Starting BOINC client as a daemon: "
su $BOINCUSER -c "$BOINCEXE $BOINCOPTS" >>$LOGFILE 2>>$ERRORLOG &
sleep 4
PID=`pidof -s -x -o $$ -o $PPID -o %PPID $BOINCEXE`
if [ $PID ]; then
[ -d $LOCKDIR ] && touch $LOCKDIR/boinc
echo_success
else
echo_failure
fi
echo
;;

stop)
cd $BOINCDIR
if [ ! -f lockfile -a ! -f $LOCKDIR/boinc ] ; then
echo -n "BOINC is not running (no lockfiles found)."
echo_success
else
echo -n "Stopping BOINC client daemon: "
killproc $BOINCEXE && echo_success || echo_failure
# clean up in any case
rm -f $BOINCDIR/lockfile
rm -f $LOCKDIR/boinc
fi
echo
;;

restart)
$0 stop
$0 start
;;

status)
PID=`pidof -x -o $$ -o $PPID -o %PPID boinc_client`
if [ "x$PID" = "x" ]; then
PID=`pidof -x -o $$ -o $PPID -o %PPID $BOINCEXE`
fi
if [ "$PID" != "" ]; then
echo "BOINC client is running (pid $PID)."
else
if [ -f $BOINCDIR/lockfile -o -f $LOCKDIR/boinc ]; then
echo "BOINC is stopped but lockfile(s) exist."
else
echo "BOINC client is stopped."
fi
fi
;;

*)
echo "Usage: boinc {start|stop|restart|status}"
exit 1
esac

exit

#EOF#
[Jul 13, 2009 9:44:10 AM]   Link   Report threatening or abusive post: please login first  Go to top 
uplinger
Former World Community Grid Tech
Joined: May 23, 2005
Post Count: 3952
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Unable to attach to project

ps -ef | grep boinc

What I get is:

rich 25468 25440 0 02:33 pts/1 00:00:00 grep boinc

or as root:

root 25504 25482 0 02:36 pts/1 00:00:00 grep boinc


Ok, it looks like the boinc client is not running at all on your machine. Let's see what happens when it is started manually.

$ whereis boinc

This will tell you which directory the boinc executable is in. for my machine it was /var/lib/boinc/

$ cd /var/lib/boinc/
$ ./boinc --help

You should get something like this. No error messages or anything.

./boinc --help
The command-line options for ./boinc are intended for debugging.
The recommended command-line interface is a separate program,'boinccmd'.
Run boinccmd in the same current as ./boinc.

Usage: ./boinc [options]
--help show options
--version show version info
--exit_when_idle exit when there are no results
--show_projects show attached projects
--detach_project <URL> detach from a project
--reset_project <URL> reset (clear) a project
--attach_project <URL> <key> attach to a project
--update_prefs <URL> contact a project to update preferences
--run_cpu_benchmarks run the CPU benchmarks
--check_all_logins for idle detection, check remote logins too
--allow_remote_gui_rpc allow remote GUI RPC connections
--gui_rpc_port <port> port for GUI RPCs
--redirectio redirect stdout and stderr to log files
--detach detach from console (Windows)
--dir <path> use given dir as BOINC home
--no_gui_rpc don't allow GUI RPC, don't make socket
--daemon run as daemon (Unix)
--exit_before_start exit right before starting a job
--exit_after_finish exit right after finishing a job
--launched_by_manager core client was launched by Manager
--run_by_updater set by updater
--start_delay X delay starting apps for X secs


If this is what you get, then try this command line.

$ ./boinc --allow_remote_gui_rpc --redirectio --daemon

You can omit the allow_remote_gui_rpc if you do not plan on monitoring this machine remotely through the boinc manager.

If this runs properly, you should get your terminal back to you. Do a ps -ef | grep boinc again to see if your output has changed. if so, then try to open up the boincmgr.

Note, if this method works, then we'll need to look deeper into why the startup script is not working.

-Uplinger
[Jul 13, 2009 2:44:31 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 14   Pages: 2   [ 1 2 | Next Page ]
[ Jump to Last Post ]
Post new Thread