"Deferring communication with project for 21+ hours"
24 Mar 2005 2:03:20 UTC
Topic 188698
(moderation:
Just got home, and the client does not get anything to do. I might have ran ou of space today (damn mldonkey crashed ugly), but almost one day of "banning" is a little too much... Is there anything I can do, or will all my unnused cycles go back to oblivion?
"Deferring communication with project for 21+ hours"
)
Replying to myself now... Just figured it out, had to detach from the project and run it again. I hope this helps someone...
Did you try an "update
)
Did you try an "update project" before detaching?
> Did you try an "update
)
> Did you try an "update project" before detaching?
>
I'm using BOINC Menubar for Mac OS X. BOINC does not seem to be designed to handle dial-up connections. My computer was not connected to the net when BOINC needed to send results, so it is now up to deferring for over 4 days for Einstein@Home!
I've tried the "Update project" option but it makes no difference.
> > Did you try an "update
)
> > Did you try an "update project" before detaching?
> >
> I'm using BOINC Menubar for Mac OS X. BOINC does not seem to be designed to
> handle dial-up connections. My computer was not connected to the net when
> BOINC needed to send results, so it is now up to deferring for over 4 days for
> Einstein@Home!
>
> I've tried the "Update project" option but it makes no difference.
You are correct. It's not very dial-up friendly. It is a bit better though. During beta, there was a period where if BOINC tried to access the servers and you weren't connected, it would crash your system.
Even with the latest greatest CC version, external communications when not connected aren't very graceful, and more often that not, lock up the client. I've found the safest thing to do is make sure you have enough work to last for a while, then disable network access. Then whenever you connect, you can re-enable network access to upload/download work. You just have to keep a close eye on deadlines with this method.
I'm not familiar with the Mac side of things, but there are a couple things you could try that usually work for the Win client. Exit the client for 15-20 minutes. This should clear the queues, and when you restart, it should try to connect to the project. Or, reboot the system once or twice...
> > > Did you try an "update
)
> > > Did you try an "update project" before detaching?
> > >
> > I'm using BOINC Menubar for Mac OS X. BOINC does not seem to be designed
> to
> > handle dial-up connections. My computer was not connected to the net
> when
> > BOINC needed to send results, so it is now up to deferring for over 4
> days for
> > Einstein@Home!
> >
> > I've tried the "Update project" option but it makes no difference.
>
> You are correct. It's not very dial-up friendly. It is a bit better though.
> During beta, there was a period where if BOINC tried to access the servers and
> you weren't connected, it would crash your system.
>
> Even with the latest greatest CC version, external communications when not
> connected aren't very graceful, and more often that not, lock up the client.
> I've found the safest thing to do is make sure you have enough work to last
> for a while, then disable network access. Then whenever you connect, you can
> re-enable network access to upload/download work. You just have to keep a
> close eye on deadlines with this method.
>
> I'm not familiar with the Mac side of things, but there are a couple things
> you could try that usually work for the Win client. Exit the client for 15-20
> minutes. This should clear the queues, and when you restart, it should try to
> connect to the project. Or, reboot the system once or twice...
>
And for dialup users when not attached to the internet, use the disable BOINC network connection feature.
BOINC WIKI
> And for dialup users when
)
> And for dialup users when not attached to the internet, use the disable BOINC
> network connection feature.
I thought I said that John. ;)
> > And for dialup users when
)
> > And for dialup users when not attached to the internet, use the disable
> BOINC
> > network connection feature.
>
> I thought I said that John. ;)
>
Sorry, you did, and I missed it.
BOINC WIKI
> > > And for dialup users
)
> > > And for dialup users when not attached to the internet, use the
> disable
> > BOINC
> > > network connection feature.
> >
> > I thought I said that John. ;)
> >
> Sorry, you did, and I missed it.
>
I've gone in and done a -help on the command line version this is what I get:
Usage: ./boinc [options]
-version show version info
-exit_when_idle Get/process/report work, then exit
-show_projects show attached projects
-return_results_immediately contact server when have results
-detach_project URL detach from a project
-reset_project URL reset (clear) a project
-attach_project attach to a project (will prompt for URL, account key)
-update_prefs URL contact a project to update preferences
-run_cpu_benchmarks run the CPU benchmarks
-check_all_logins check input from remote users
-allow_remote_gui_rpc allow remote GUI RPC connections
-redirectio redirect stdout and stderr to log files
I can't see anything here that will disable network connection (I am also not familiar with unix so it may be there and I just don't know it).
This is only possible via
)
This is only possible via RPC,
so you can do the following:
> telnet localhost 31416
Now enter the following:
(set_network_mode)(always)(/always)(/set_network_mode)
or
(set_network_mode)(never)(/never)(/set_network_mode)
You must replace ( and ) with "less than" and "greater than" though
But with the upcoming 4.2x release there will be a *NIX GUI too.
Team Linux Users Everywhere
> This is only possible via
)
> This is only possible via RPC,
>
> so you can do the following:
>
> > telnet localhost 31416
I'm now totally out of my depth. I'll wait until the Mac gui version is further developed.