Hi,

I have Predictor and S@H running on my PC.

Specs:
BOINC 4.05
Win2k w/ 512 megs of RAM, patched, service packed, recent drivers, &c..

I've noticed a few things. When S@H was dead, Predictor would run for a while, then stop even though there were no S@H units to crunch. The status flag in BOINC would read running even though Predictor was not running -- "System Idle Process" would have 100% use of the processor. The flag at no time read "pre-empted".

Just now, with S@H units and my Predictor unit, BOINC again stopped crunching. S@H's status flag read "running", but it wasn't.

My resource share is 90% S@H, 10% Predictor.

Any help is appreciated!

Jason

Are you using dial up? Because it is messed up. If you aren't online when it wants to talk to the servers, all process is halted until you exit/restart the client.

Maybe dev could finally get us dial up folk sorted out?

Yes, I've gotten so used to "disabling network access" that it seems almost automatic. Anyway, that seems to keep things running.

Remember if you reboot to disable network status; Boinc does not keep the last configuration (the network status) upon exiting.

> Are you using dial up? Because it is messed up. If you aren't online when it
> wants to talk to the servers, all process is halted until you exit/restart the
> client.
>
> Maybe dev could finally get us dial up folk sorted out?
>
> <a> href="http://www.boinc.dk/index.php?page=user_statistics&project=sah&userid=91863">
>

Hi,

I'm on broadband with a very stable connection (hardware router + good ISP).

If this helps, here's my setup:

Do work while computer is running on batteries?
(matters only for portable computers) yes
Do work while computer is in use? yes
Do work only between the hours of (no restriction)
Leave applications in memory while preempted?
(suspended applications will consume swap space if 'yes') yes
Confirm before connecting to Internet?
(matters only if you use a modem) no
Disconnect when done?
(matters only if you use a modem) no
Connect to network about every 0.1 days
On multiprocessors, use at most 2 processors
Write to disk at most every 60 seconds

The only thing I can think of is the "Connect to to network about every 0.1 days" setting. Unfortunately, my cache is low (2 WUs), and I can churn out a WU every 2.5 hours or so, so my PC should be connecting frequently.

Blech.

On my beta account, I never had this problem. It was just when I activated my SETI classic account + changed to 4.05 that this problem started.

Any other suggestions?

Jason

> > Are you using dial up? Because it is messed up. If you aren't online when
> it
> > wants to talk to the servers, all process is halted until you
> exit/restart the
> > client.
> >
> > Maybe dev could finally get us dial up folk sorted out?
> >
> > <a>
> href="http://www.boinc.dk/index.php?page=user_statistics&project=sah&userid=91863">
> >
>
> Hi,
>
> I'm on broadband with a very stable connection (hardware router + good ISP).
>
> If this helps, here's my setup:
>
> Do work while computer is running on batteries?
> (matters only for portable computers) yes
> Do work while computer is in use? yes
> Do work only between the hours of (no restriction)
> Leave applications in memory while preempted?
> (suspended applications will consume swap space if 'yes') yes
> Confirm before connecting to Internet?
> (matters only if you use a modem) no
> Disconnect when done?
> (matters only if you use a modem) no
> Connect to network about every 0.1 days
> On multiprocessors, use at most 2 processors
> Write to disk at most every 60 seconds
>
> The only thing I can think of is the "Connect to to network about every 0.1
> days" setting. Unfortunately, my cache is low (2 WUs), and I can churn out a
> WU every 2.5 hours or so, so my PC should be connecting frequently.
>
> Blech.
>
> On my beta account, I never had this problem. It was just when I activated my
> SETI classic account + changed to 4.05 that this problem started.
>
> Any other suggestions?
>
> Jason
>
>

Messed my mind up, I thought you were connected to Predictor, you must mean CPDN climate prediction, ok, now I had this problem a couple of times and I think it has something to do with a project not being able to contact the server. Two times it happen, when predictor and Pirates could not connect and both were auto detached and BOINC just stopped and it took a restart and I have not had any more problems..I will not reconnect until both of the projects are listed as up......


When Asking for help, please post the following;
Type of PC
How much memory
Type of Operating System
Type of connection to Internet
Projects You are Running
Version of BOINC

M7 Seti@h Berkeley's Staff Friends Club ©

Here are my observations.

None of my computers that only run Seti have had an issue with stopping activity. However, I noticed that one of my computers that runs Seti and CPDN would stop crunching even though it says the processes were reportedly running. I also noticed that everytime I came back to computer and found it had stopped crunching the screensaver had been activated. As a test I changed my screensaver to "none". Since then I have not had an issue with the processes stopping. Everything has has been run normally.

I have a simular problem but it hapens when the internet is used hevily
the errer file sead lost hart beat

p4 with 511 mem dsl XP sp2 sety / cpdn

this started with 4.05

> > Are you using dial up? Because it is messed up. If you aren't online when
> it
> > wants to talk to the servers, all process is halted until you
> exit/restart the
> > client.
> >
> > Maybe dev could finally get us dial up folk sorted out?
> >
> > <a>
> href="http://www.boinc.dk/index.php?page=user_statistics&project=sah&userid=91863">
> >
>
> Hi,
>
> I'm on broadband with a very stable connection (hardware router + good ISP).
>
> If this helps, here's my setup:
>
> Do work while computer is running on batteries?
> (matters only for portable computers) yes
> Do work while computer is in use? yes
> Do work only between the hours of (no restriction)
> Leave applications in memory while preempted?
> (suspended applications will consume swap space if 'yes') yes
> Confirm before connecting to Internet?
> (matters only if you use a modem) no
> Disconnect when done?
> (matters only if you use a modem) no
> Connect to network about every 0.1 days
> On multiprocessors, use at most 2 processors
> Write to disk at most every 60 seconds
>
> The only thing I can think of is the "Connect to to network about every 0.1
> days" setting. Unfortunately, my cache is low (2 WUs), and I can churn out a
> WU every 2.5 hours or so, so my PC should be connecting frequently.
>
> Blech.
>
> On my beta account, I never had this problem. It was just when I activated my
> SETI classic account + changed to 4.05 that this problem started.
>
> Any other suggestions?
>
> Jason
>
>
I have a p4 3.0 and crunch a WUWU about every 2 1/2 tp 3 hrs and I use the following and never run out of work unless the server goes down..... Only get up to 10 WUWUs at a time.

Do work while computer is running on batteries? (matters only for portable computers) no
Do work while computer is in use? yes
Do work only between the hours of (no restriction)
Leave applications in memory while preempted? (suspended applications will consume swap space if 'yes') yes
Confirm before connecting to Internet?(matters only if you use a modem) no
Disconnect when done? (matters only if you use a modem) no
Connect to network about every 3 days
On multiprocessors, use at most 1 processors
Write to disk at most every 1200 seconds
Limits on disk space and memory used by BOINC:
Use no more than 8 GB
Leave at least .1 GB
Use no more than 75% of total space
Use no more than 75% of total virtual memory



When Asking for help, please post the following;
Type of PC
How much memory
Type of Operating System
Type of connection to Internet
Projects You are Running
Version of BOINC

M7 Seti@h Berkeley's Staff Friends Club ©

4.05 does this randomly. It is supposed to be fixed in 4.08 which alpha is still testing.

Not sure if this is the same bug. I have been suspecting that it has been doing this for a while but I just caught BOINC with its pants down and finnally got the error message. Below are the pertinent log lines. Of particular interest is where it actually stopped computing down at the bottom. LHC was preempted and it tried to start SAH and proceeded to crap its pants. I have also caught it restarting seti@home work units when resuming them. this created an endless loop where the same data was being processed over and over without any work actually getting done until I set resource share of LHC to a very small value so it wouldn't try to switch back to it and preempt seti.


LHC@home - 2004-09-08 14:03:21 - Restarting result v64bbe634s6_8645_1_sixvf_4163_9 using sixtrack version 4.43
SETI@home - 2004-09-08 14:03:21 - Preempting result 05my04aa.9306.11248.703400.25_0 (quit)
LHC@home - 2004-09-08 15:03:21 - Preempting result v64bbe634s6_8645_1_sixvf_4163_9 (quit)
SETI@home - 2004-09-08 15:03:21 - Restarting result 05my04aa.9306.11248.703400.25_0 using setiathome version 4.03
LHC@home - 2004-09-08 20:09:31 - Restarting result v64bbe634s6_8645_1_sixvf_4163_9 using sixtrack version 4.43
SETI@home - 2004-09-08 20:09:31 - Preempting result 05my04aa.9306.11248.703400.25_0 (quit)
LHC@home - 2004-09-08 21:09:31 - Preempting result v64bbe634s6_8645_1_sixvf_4163_9 (quit)
SETI@home - 2004-09-08 21:09:31 - resume_or_start(): unexpected process state 8




-------------------------------------------
- A member of The Knights Who Say NI!
Possibly the best stats site in the universe:
http://boinc-kwsn.no-ip.info