I am running RH 9 and the Linux client. It is past 30,000 timesteps and still has not trickled? is this by design?

This problem was identified in another thread from several weeks ago, but has not been resolved. I think this is quite an important issue- my CPDN client is currently up to "Deferring communication" for 1 week, 1 day and there is no way I can get it to connect/update when I am online. It seems as if the client has been designed with the assumption

CPDN folks, please shed some light on this subject for us. Specifically:
- are trickles the communication being "deferred"? Is there other stuff being communicated also?
- if so, how can we initiate trickles/updates?
- if not, how can we initiate trickles?
- how can we tell the client "I am currently online. Do your thing."?
- what settings should we be using for our general prefs such that this doesn't happen?

cheers,
Randall.

sorry- unfinished sentence

It seem that the CPDN client has been designed with the assumption that network connectivity is (almost) always available. Furthermore, repeated network connection failures seem to make the wait time increase exponentially. My "deferring time" has gone from:
1 min
4 min
28 min
48 min
4 hours
13 hours
1 day 1 hour
19 hours
1 week 1 day...

Cheers,
Randall & Cath.

Hi, you can force a connection (trickle), but for Linux/Mac you need to quit boinc (Ctrl+C), and then restart with the option "-update_prefs climateprediction.net", i.e.

./boinc_4.05* -update_prefs climateprediction.net

That will "force" communications with our scheduler and at that time any pending trickles will be sent.

I complained about the exponential standoff back around easter time - pre-(cpdn)boinc beta. Other options relevant here are to have a fixed 'check for connection every 10mins' or a separate program which can be run without stopping boinc and which will just collect all upload*.xml and send them in the direction of .ox. As trickling (hopefully) requires no changes to boinc internal variables this program would be able to be run at any time, or even scripted with an entry in /etc/ppp/ip-up.local (run whenever a connection is made). But then my router arrives next week so all of this will soon be irrelevant to me.
Cheers,

PeterV.
<IMG SRC="http://boinc.mundayweb.com/cpdn/stats.php?userID=4&amp;trans=off">

Hi Carl,

Thanks for the quick reply, but this didn't work. The log is below. Have we done something wrong?

Cheers,
R &amp; C.

astrocath:~/CPDN&gt; ./boinc_4.05_i686-pc-linux-gnu -update_prefs http://climateprediction.net
2004-09-04 20:56:10 [---] Starting BOINC client version 4.05 for i686-pc-linux-gnu
2004-09-04 20:56:10 [climateprediction.net] Project prefs: no separate prefs for work; using your defaults
2004-09-04 20:56:10 [climateprediction.net] Host ID is 2292
2004-09-04 20:56:10 [---] General prefs: from climateprediction.net (last modified 2004-08-28 15:40:20)
2004-09-04 20:56:10 [---] General prefs: using separate prefs for work
2004-09-04 20:56:10 [climateprediction.net] Resuming computation for result 02ss_300028613_0 using hadsm3 version 4.03
2004-09-04 20:56:10 [climateprediction.net] Deferring communication with project for 1 weeks, 0 days, 12 hours, 22 minutes, and 3 seconds
2004-09-04 20:56:10 [climateprediction.net] Deferring communication with project for 1 weeks, 0 days, 12 hours, 22 minutes, and 3 seconds
Starting model in /home/rwayth/CPDN/projects/climateprediction.net...
Created shared memory region key = 25615
Env Used=LD_LIBRARY_PATH=/home/rwayth/CPDN/projects/climateprediction.net:/usr/local/lib/pgplot:/usr/X11R6/lib:/usr/local/lib:/usr/local/lib:/usr/lib:/lib
Starting model ID 02ss_300028613 Phase 1
Stack size=4096.00 MB
Waiting for model startup, this may take a minute...
02ss_300028613 - PH 1 TS 160273 - 10/03/1820 00:30 - H:M:S=0143:10:27 AVG= 3.22 DLT= 0.00
02ss_300028613 - PH 1 TS 160274 - 10/03/1820 01:00 - H:M:S=0143:10:40 AVG= 3.22 DLT=12.80


&gt; Hi, you can force a connection (trickle), but for Linux/Mac you need to quit
&gt; boinc (Ctrl+C), and then restart with the option "-update_prefs
&gt; climateprediction.net", i.e.
&gt;
&gt; ./boinc_4.05* -update_prefs climateprediction.net
&gt;
&gt; That will "force" communications with our scheduler and at that time any
&gt; pending trickles will be sent.

Unfortunately, that's not working for me:

2004-09-11 00:02:10 [---] Starting BOINC client version 4.05 for i686-pc-linux-gnu
2004-09-11 00:02:10 [climateprediction.net] Project prefs: using your defaults
2004-09-11 00:02:10 [climateprediction.net] Host ID not assigned yet
2004-09-11 00:02:10 [---] General prefs: from climateprediction.net (last modified 2004-08-06 23:25:33)
2004-09-11 00:02:10 [---] General prefs: using your defaults
2004-09-11 00:02:10 [climateprediction.net] Deferring communication with project for 1 weeks, 2 days, 17 hours, 27 minutes, and 35 seconds
2004-09-11 00:02:10 [climateprediction.net] Deferring communication with project for 1 weeks, 2 days, 17 hours, 27 minutes, and 35 seconds

I think what happened was that it wanted to update while I was at work (running on a laptop), which requires a proxy to get to the Internet. I didn't have the proxy configured at the time, so it failed. I tried it at home (no proxy required) and it still said "Deferring communication..."

Is it possible for me to edit wherever that delay is stored and bump it back down to a couple of minutes, maybe??

Thanks,

RalphM

&gt; Hi, you can force a connection (trickle), but for Linux/Mac you need to quit
&gt; boinc (Ctrl+C), and then restart with the option "-update_prefs
&gt; climateprediction.net", i.e.
&gt;
&gt; ./boinc_4.05* -update_prefs climateprediction.net
&gt;
&gt; That will "force" communications with our scheduler and at that time any
&gt; pending trickles will be sent.

Hi Folks,

So I think the explanation for this problem is simply: you cannot force boinc to connect while it is "Deferring communication". The "update_prefs" flag does not force a connection. You must simply wait for the clock to count down and make sure the network is available when it tries again.

I have tried this with my home computer (modem connection mostly offline). Yesterday it was due to try connecting again (after 9 days) in the afternoon. So I killed the client in the morning, then when I got home from work, established the connection and restarted the client. Lo! The trickles get sent...

I think a boinc command-line option saying "establish connection now" would be useful.

Cheers,
Randall.

&gt; Unfortunately, that's not working for me:
&gt;
&gt; 2004-09-11 00:02:10 [---] Starting BOINC client version 4.05 for
&gt; i686-pc-linux-gnu
&gt; 2004-09-11 00:02:10 [climateprediction.net] Project prefs: using your
&gt; defaults
&gt; 2004-09-11 00:02:10 [climateprediction.net] Host ID not assigned yet
&gt; 2004-09-11 00:02:10 [---] General prefs: from climateprediction.net (last
&gt; modified 2004-08-06 23:25:33)
&gt; 2004-09-11 00:02:10 [---] General prefs: using your defaults
&gt; 2004-09-11 00:02:10 [climateprediction.net] Deferring communication with
&gt; project for 1 weeks, 2 days, 17 hours, 27 minutes, and 35 seconds
&gt; 2004-09-11 00:02:10 [climateprediction.net] Deferring communication with
&gt; project for 1 weeks, 2 days, 17 hours, 27 minutes, and 35 seconds
&gt;
&gt; I think what happened was that it wanted to update while I was at work
&gt; (running on a laptop), which requires a proxy to get to the Internet. I
&gt; didn't have the proxy configured at the time, so it failed. I tried it at
&gt; home (no proxy required) and it still said "Deferring communication..."
&gt;
&gt; Is it possible for me to edit wherever that delay is stored and bump it back
&gt; down to a couple of minutes, maybe??
&gt;
&gt; Thanks,
&gt;
&gt; RalphM
&gt;
&gt; &gt; Hi, you can force a connection (trickle), but for Linux/Mac you need to
&gt; quit
&gt; &gt; boinc (Ctrl+C), and then restart with the option "-update_prefs
&gt; &gt; climateprediction.net", i.e.
&gt; &gt;
&gt; &gt; ./boinc_4.05* -update_prefs climateprediction.net
&gt; &gt;
&gt; &gt; That will "force" communications with our scheduler and at that time any
&gt; &gt; pending trickles will be sent.
&gt;
&gt;
&gt;