Messages

Another issue that seems to have been resolved is the crashing problem.  I had fairly constant crashes with 1.22 - 1.29 (at the least several a day).  So far have had NONE with 1.30 

1.25 had major problems, use 1.30 and I believe your issue will be gone 
And no I have no idea why 1.25 is listed as the latest non beta.  It didn't work so well here either.  1.30 solved all the major issues I had.

My log shows: Set the connect flag in log.xml to 1.

Duh on my part.  I rechecked my settings again and somehow the "Reconnect every xx seconds" under Expert was changed to 0.  Set it back to 120, tried disconnecting a client and it reconnected with tasks showing properly.  Sorry, I should have investigated further before posting an issue. 

Have a great holiday everyone!

Must be a misunderstanding.  Not referring to installing a new BOINC version.  If I shut down BOINC or restart a machine it is not picked up again by BT (the machines do show as connected but no tasks are listed) no matter how long I wait.  Exiting BT and restarting it instantly picks up all the machines and tasks again.  Using 6.12.41 or 6.12.43 on all machines.  BTW the long start and exit times are gone, it takes only about a second with v1.30 

In the side bar a lost connection icon should appear. Does it?
When you click on the computer in the side bar it should reconnect.

Maybe need to be clearer:  when the connection is lost the lost icon appears in the left pane.  When the computer becomes available again the lost icon goes away and the computer shows as connected in the left pane but no tasks are listed under the Tasks Tab.  This behavior is consistent and absolutely repeatable.  Double clicking on the computer does NOT bring the tasks back.  Restarting BT fixes the problem.

Compare this behavior to that of 1.21.  In 1.21 on a lost connection the tasks reappear when the disconnected computer's icon is double clicked.  Double clicking is not usually even necessary as in 1.21 the disconnected computers generally automatically reconnect within a couple minutes.  My BT settings are consistent for both 1.21 and 1.30.

I'm not seeing any more crashes since updating to 1.30.  In fact most of the previous problems seem to be gone.  The only one still not working is reconnecting a client after it disconnects by either shutting down BOINC or rebooting.  BT will not reconnect.  It must be exited and restarted (double clicking on the computer icon doesn't work), but at least that works very quickly now.

Seems I've been doing something right this time.
Must be related to a bad connection somehow.

Installing a new BOINC version will probably always be a problem, best to shut down the client first.
BOINC is killed by the installer, this leaves the connection open, without properly closing it down.

Must be a misunderstanding.  Not referring to installing a new BOINC version.  If I shut down BOINC or restart a machine it is not picked up again by BT (the machines do show as connected but no tasks are listed) no matter how long I wait.  Exiting BT and restarting it instantly picks up all the machines and tasks again.  Using 6.12.41 or 6.12.43 on all machines.  BTW the long start and exit times are gone, it takes only about a second with v1.30 

I'm not seeing any more crashes since updating to 1.30.  In fact most of the previous problems seem to be gone.  The only one still not working is reconnecting a client after it disconnects by either shutting down BOINC or rebooting.  BT will not reconnect.  It must be exited and restarted (double clicking on the computer icon doesn't work), but at least that works very quickly now.

It's running now (looks like on all 9 clients), how long to leave it this way?

Until the next crash.

Dmp & log files uploaded.

It's running now (looks like on all 9 clients), how long to leave it this way?

Until the next crash.
If you see the 100% running again....
Try all graphs, see if they still work.
Try using anything you can think off and see if it's still working.

I never had the 100% problem, that was someone else.  Had much higher usage than with 1.21 though.
Had 5 dmp files with 1.29 yesterday but so far none since doing the log changes.  Just typical
The CPU usage is low so far too since initiating the heap checking.

That's probably not right, let me know.  I'm using 1.29.

C:\Program Files\eFMer\BoincTasks\examples\log\log.xml
change the 0 -> 1
Copy the file to C:\Program Files\eFMer\BoincTasks\log\log.xml

It's running now (looks like on all 9 clients), how long to leave it this way?

05 December 2011 - 14:53:23 Heap checking  ---- WARNING: is enabled
05 December 2011 - 14:53:23 Heap checking  ---- WARNING: is enabled
05 December 2011 - 14:53:23 Heap checking  ---- WARNING: is enabled
05 December 2011 - 14:53:23 Heap checking  ---- WARNING: is enabled
05 December 2011 - 14:53:24 Heap checking  ---- WARNING: is enabled
05 December 2011 - 14:53:24 Heap checking  ---- WARNING: is enabled
05 December 2011 - 14:53:24 Heap checking  ---- WARNING: is enabled
05 December 2011 - 14:53:24 Heap checking  ---- WARNING: is enabled
05 December 2011 - 14:53:24 Heap checking  ---- WARNING: is enabled

moved post to the 1.29 beta thread...

Four of the little dears should be there

The problem is I never got them or any previous....
Probably blocked along the way.

They still show in your upload directory:

Fred, do you want more dmp files?  I sent one a while ago but haven't heard if you found anything interesting.

I do. 

Four of the little dears should be there

during this evening I've seen BT using nearly the whole CPU and nothing could be done except re-start, and twice there has been to reboot the computer as immediately went to the top.

While I haven't seen this kind of usage, 1.28 uses many times more CPU than 1.21.  Lately as an experiment I've been running 1.21 on one of my desktop machines and 1.28 on the other.  1.21 has proven to be FAR more stable and uses very little CPU.  All settings are the same for both versions.  LT history is disabled in 1.28.  Both machines are running the same programs/projects and both have AMD CPUs with 2 GPUs (although the 1.21 box has 1 ATI and 1 NVidia while the 1.28 box has 2 ATIs).  If there is even a remotely flaky connection with one of the computers 1.28 becomes unstable and often has to be restarted.  1.21 will either pick the connection back up or restore it when double-clicked.  The situation gets worse when running many WUs.  I stopped running MW for Collatz a few days ago but when running MW had an AVERAGE of over 5 WUs/minute finishing.  1.21 also seemed to handle this situation better than 1.28.

I'd suggest 1.21 for the most stable version or 1.28 if you're a bit more adventurous.  Everything between was troublesome here, including the symptoms you describe.  To use 1.28 I have to disable the long term history (new feature).  It also does not handle machines with flaky connections (such as weak WiFi) as well as 1.21.  1.28 often has to be restarted (and sometimes crashes) when machines lose connection for any reason (WiFi, reboot, crash, etc.).  Fred, do you want more dmp files?  I sent one a while ago but haven't heard if you found anything interesting.

Turns out that what has grown to a 3 minute start time for BT is related to history logging.  Had to manually delete the 6.5GB of long term history files as well as disabling long term history.  Now BT starts in 2-3 seconds.  I was also getting frequent BT crashes.  Now they've stopped too.

In V 1.29 I will make the history backup optional (default off), it's not needed for most users anyway.

Nice, that should solve a lot of problems.  Thanks