climateprediction.net home page
Client connected to server all night

Client connected to server all night

Questions and Answers : Windows : Client connected to server all night
Message board moderation

To post messages, you must log in.

AuthorMessage
old_user272

Send message
Joined: 6 Aug 04
Posts: 58
Credit: 1,286,603
RAC: 0
Message 279 - Posted: 7 Aug 2004, 6:38:22 UTC

As I use a modem to connect to the Internet I have set my preferences so that the client asks before connecting and doesn\'t automatically disconnect.

At 00:50 this morning the client decided it wanted to connect to the server - and did so!. It stayed online for 17 mins, cleared down, waited 30 secs, redialled and went online for another 30 odd minutes. This went on through the whole night for a total of nearly 6 hours online time.

In addition, at 00:50 the client stopped working on the model and hasn\'t completed any work all night.

Anyone else seen this or is it just a problem with my machine (heat maybe?).

Ian
ID: 279 · Report as offensive     Reply Quote
old_user272

Send message
Joined: 6 Aug 04
Posts: 58
Credit: 1,286,603
RAC: 0
Message 280 - Posted: 7 Aug 2004, 6:52:27 UTC

Update -

I rebooted the machine, the client restarted and then, about 30 secs later, went online (without asking), sent some data and then froze with no more work being done - and still stayed online.

Ian



ID: 280 · Report as offensive     Reply Quote
Profile Keck_Komputers
Avatar

Send message
Joined: 5 Aug 04
Posts: 426
Credit: 2,340,019
RAC: 0
Message 288 - Posted: 7 Aug 2004, 9:04:36 UTC

BOINC still has some problems playing with intermittent connection types. The best workaround currently is to disable network access in BOINC's file menu. This setting is not persistant so you will have to redo it each time you start BOINC. When you want to connect reenable network access while you are online.
<br>John Keck
BOINCing since 2002/12/08
ID: 288 · Report as offensive     Reply Quote
old_user1
Avatar

Send message
Joined: 5 Aug 04
Posts: 907
Credit: 299,864
RAC: 0
Message 292 - Posted: 7 Aug 2004, 9:50:58 UTC

I haven't seen this on mine although I have a cable modem now and not dialup. It should only try to use the network to send "trickle" updates of the run every 10,802 timesteps, which should be at most every 6-7 hours on a pretty fast machine (i.e. I get 7 hours per trickle on my AMD64 which runs the model at 2.4 seconds per timestep).

Perhaps you should select "Disable BOINC Network Access" (assuming you use the Windows GUI), and then trickles will get sent when you allow network access? The trickle files are very small and just "queue" in the projects directory.

ID: 292 · Report as offensive     Reply Quote
old_user272

Send message
Joined: 6 Aug 04
Posts: 58
Credit: 1,286,603
RAC: 0
Message 294 - Posted: 7 Aug 2004, 9:57:05 UTC - in response to Message 288.  

&gt; BOINC still has some problems playing with intermittent connection types. The
&gt; best workaround currently is to disable network access in BOINC's file menu.
&gt; This setting is not persistant so you will have to redo it each time you start
&gt; BOINC. When you want to connect reenable network access while you are online.

Thanks, that has temporarily solved the problem and I've moved back to the BOINC client sucessfully (I'd temporarily restarted the "normal" client).

It might be worth adding a note to the beta instruction page about the possibility of a problem with dial up access. If I'd had to _pay_ for 6 hours worth of phone calls I wouldn't have been a happy bunny...

Ian
ID: 294 · Report as offensive     Reply Quote

Questions and Answers : Windows : Client connected to server all night

©2020 climateprediction.net