Switching between tabs issue:
I've stopped BOINC client (shortly past 19:29:00) to install a newer version. In a few seconds BT dismissed all tasks from the Tasks tab pane. So far all good. But suddenly I could not switch to the Computers tab by clicking on it, neither on any other tab - the "tab button" just flashed after a click and nothing happened. But I was able to switch between tab panes using the "Show / ...." menu items, without any problem.
In a minute or so the newer BOINC version was installed and started (at 19:32:56). Some other minute later I helped the BT's connection to a client to be recovered - suddenly the usual switching between the tab panes was functional as usual.
16 november 2011 - 22:29:57 BoincTasks version: 1.27
16 november 2011 - 22:29:57 Language ---- User: 1051 (SKY), System: 1051 (SKY), Selected: 0 () Used: 1051 (SKY)
16 november 2011 - 22:30:01 Maximum number of computers: Unlimited
16 november 2011 - 22:30:01 Computers ---- Vandus , localhost
[....]
17 november 2011 - 19:15:06 Connect ---- Connected to: Host: localhost, Vandus,Port: 31417, TThrottle Version: 5.44
17 november 2011 - 19:29:47 Connect ---- Lost connection to: Host: localhost, Vandus, Port: 31416
17 november 2011 - 19:34:12 BoincTasks is closing down all threads
17 november 2011 - 19:36:14 BoincTasks has closed down all threads
17 november 2011 - 19:36:16 Maximum number of computers: Unlimited
17 november 2011 - 19:36:16 Computers ---- Vandus , localhost
17 november 2011 - 19:36:17 Connect ---- Connected to: Host: localhost, Vandus, Port: 31416, BOINC Version: 6.13.12
17 november 2011 - 19:36:20 Connect ---- Connected to: Host: localhost, Vandus,Port: 31417, TThrottle Version: 5.44
Quote from: Pepo on November 17, 2011, 08:00:22 PM
Switching between tabs issue:
When BT is closing, it doesn't allow any tab switching.
Quote from: fred on November 18, 2011, 08:05:45 AM
Quote from: Pepo on November 17, 2011, 08:00:22 PM
Switching between tabs issue:
When BT is closing, it doesn't allow any tab switching.
No, BT was not closing but kept running. BOINC client was closed.
Quote from: Pepo on November 18, 2011, 10:02:28 AM
No, BT was not closing but kept running. BOINC client was closed.
There is closing and closing.
This one is closing all threads and restarts them, without restarting the whole program. Shows closing...
Quote from: fred on November 18, 2011, 10:54:39 AM
Quote from: Pepo on November 18, 2011, 10:02:28 AM
No, BT was not closing but kept running. BOINC client was closed.
There is closing and closing.
This one is closing all threads and restarts them, without restarting the whole program. Shows closing...
Ah, OK. I should've read "When BT is closing [its connections and threads] ..." ;)
The interesting point was that switching through menus worked just fine.
Quote from: Pepo on October 26, 2011, 05:34:42 PM
Quote from: Pepo on October 26, 2011, 01:31:54 PM
Quote from: fred on October 26, 2011, 11:31:17 AM
I've seen the collapse problem once, but when you restart BT it should go away, I'm not sure why this happens, have to check.
In my case it persists. On the other machine, three notices related to both remote_hosts.cfg and cc_config.xml. In BT 1.24 a few minutes ago they were closing just fine. I've also noticed that the trailing numbers in URLs are being updated all three at once (like 144+145+143 -> 147+148+146), regardless of which [-] is being clicked on.
With the same BT instance, I've updated BOINC 6.12.34 -> 6.12.41 - I can suddenly close these three notices. Perhaps their format changed slightly in between and BT 1.25 does not support the older format correctly? (A wild guess.)
Still persists in BT 1.27 (connected to 6.12.41) - I can not collapse just these notices and the indices in their URLs also keep updating.
I'll check again in an hour or later.
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.
BTW, TT 5.45 has stopped the -35.7479329427759359867939745749497539927 temps here so far :)
Quote from: Beyond on November 20, 2011, 04:09:49 PM
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.
BTW, TT 5.45 has stopped the -35.7479329427759359867939745749497539927 temps here so far :)
1.27 should delete files in the background, so any start up delay should be gone.
TT had a small typo, but it effected only some computers.
Quote from: fred on November 20, 2011, 06:22:30 PM
Quote from: Beyond on November 20, 2011, 04:09:49 PM
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.
BTW, TT 5.45 has stopped the -35.7479329427759359867939745749497539927 temps here so far :)
1.27 should delete files in the background, so any start up delay should be gone.
TT had a small typo, but it effected only some computers.
1.27 did NOT delete the backup files and they grew until there were massive problems.. There seems to be a problem with the new history setup, a problem that's existed in every version after the 1.21 build.
The TT typo affected all most if not all of my computers but so far it seems to be fixed in 5.45.
Quote from: Beyond on November 20, 2011, 10:23:45 PM
1.27 did NOT delete the backup files and they grew until there were massive problems.. There seems to be a problem with the new history setup, a problem that's existed in every version after the 1.21 build.
The TT typo affected all most if not all of my computers but so far it seems to be fixed in 5.45.
But it does, see C:\Users\username\AppData\Roaming\eFMer\BoincTasks\log\BoincTasks Startup.log
It can take a while to complete, so you have to let BT run for a while.
It does not delete the backup for 14 days, it's a backup after all.
I've opened BT's window, for the second time today. The Notices tab informs about "210 Notices", now (a few minutes later) 213. BOINC Manager shows just some 18 notices.
After opening the tab pane, there are just 10 opened and 3 collapsed notices. Just two of them were added over the weekend, since I've seen them the last time.
Could it be somehow caused by the problem with collapsible client notices, which URL's index (like in file:///C:/Users/UserName/AppData/Roaming/eFMer/BoincTasks/html/__collapse__497 (http://file:///C:/Users/UserName/AppData/Roaming/eFMer/BoincTasks/html/__collapse__497)) gets auto-incremented (in my case by +3) again and again?
Quote from: Pepo on November 21, 2011, 03:03:30 PM
Could it be somehow caused by the problem with collapsible client notices, which URL's index (like in file:///C:/Users/UserName/AppData/Roaming/eFMer/BoincTasks/html/__collapse__497 (http://file:///C:/Users/UserName/AppData/Roaming/eFMer/BoincTasks/html/__collapse__497)) gets auto-incremented (in my case by +3) again and again?
Sure, it detects new messages.
Maybe it has something to do with the language setting.
Do you use the English version? If not try switching to English.
What notices are added and again?
New notices are checked against a check sum of the text. So maybe some special characters are messing things up.
Could you mail me a notices.html file.
Quote from: fred on November 21, 2011, 08:10:15 AM
Quote from: Beyond on November 20, 2011, 10:23:45 PM
1.27 did NOT delete the backup files and they grew until there were massive problems.. There seems to be a problem with the new history setup, a problem that's existed in every version after the 1.21 build.
But it does, see C:\Users\username\AppData\Roaming\eFMer\BoincTasks\log\BoincTasks Startup.log
It can take a while to complete, so you have to let BT run for a while.
It does not delete the backup for 14 days, it's a backup after all.
How long does it take, maybe BT isn't running long enough without restarting to get the job done? Why 14 days? With LT history enabled I was getting constant crashes / restarts and had > 6.5 GB of backup history files. Disabling LT history and deleting the LT files made BT 90% more stable than it was but there's still a long way to go in that department. Don't take me wrong, I love BT but there are some nagging stability problems that make it a challenge for those of us with a lot of WUs passing through. Not to tell you what to do but maybe put the new features on hold until the issues are worked out.
Quote from: Beyond on November 21, 2011, 04:27:55 PM
How long does it take, maybe BT isn't running long enough without restarting to get the job done? Why 14 days? With LT history enabled I was getting constant crashes / restarts and had > 6.5 GB of backup history files. Disabling LT history and deleting the LT files made BT 90% more stable than it was but there's still a long way to go in that department. Don't take me wrong, I love BT but there are some nagging stability problems that make it a challenge for those of us with a lot of WUs passing through. Not to tell you what to do but maybe put the new features on hold until the issues are worked out.
When I don't get crash reports they never get solved, because I haven't seen any crashes myself for a long time. And I got a lot of WU's on my computers.
You can check the startup log to see how long it takes, it log the dates.
Quote from: Pepo on November 21, 2011, 03:03:30 PM
Could it be somehow caused by the problem with collapsible client notices, which URL's index (like in file:///C:/Users/UserName/AppData/Roaming/eFMer/BoincTasks/html/__collapse__497 (http://file:///C:/Users/UserName/AppData/Roaming/eFMer/BoincTasks/html/__collapse__497)) gets auto-incremented (in my case by +3) again and again?
I've mistyped it: "the problem with
uncollapsible client notices".
Quote from: fred on November 21, 2011, 03:46:30 PM
Sure, it detects new messages.
Maybe it has something to do with the language setting.
Do you use the English version? If not try switching to English.
New notices are checked against a check sum of the text. So maybe some special characters are messing things up.
I'm using Slovak translation. I'll keep it for a while and try to sample the different
notice.html files like this. Then switch to English maybe tomorrow.
Quote
What notices are added and again?
Just looking at the file (time-stamp 21.11.11 18:03). The most recent two notices were "19.11.11 21:41 PrimeGrid: World Record Generalized Fermat Prime" and "21.11.11 18:03 Oznam od TThrottle, Táto verzia: 5.44, Nájdená nová beta verzia: 5.50." (I've already installed the 5.50 more than two hours ago (around 16:08), the
Computers tab is aware of it, but never mind.) BT just displays "6 Notices" - note it is quite possibly divisible by my 3 "usually uncollapsible notices".
One more idea - I'm using own template for notices, which off course might also be flawed.
One hour later, now "9 Notices". I'm also adding the
notices.xml, I guess it will shed more light into the problem. (Then opened the Notices tab pane. And added one more set of files. and once more opened the tab and one more set of files.) Because a set of 3 empty notices is always being added to the XML files, what is possibly also causing my auto-incrementation:
<notice>
<added_time>1321891434.000000</added_time>
<project></project>
<title></title>
<checksum>5377</checksum>
<collapsed>0</collapsed>
<deleted>0</deleted>
</notice>
<notice>
<added_time>1321891434.000000</added_time>
<project></project>
<title></title>
<checksum>5175</checksum>
<collapsed>0</collapsed>
<deleted>0</deleted>
</notice>
<notice>
<added_time>1321891434.000000</added_time>
<project></project>
<title></title>
<checksum>5475</checksum>
<collapsed>0</collapsed>
<deleted>0</deleted>
</notice>
<notice>
<added_time>1321898634.000000</added_time>
I've then restarted BT - a lot of entries in
notices.xml disapeared.
QuoteCould you mail me a notices.html file.
(Sending files per e-mail.)
Quote from: fred on November 21, 2011, 06:36:16 PM
Quote from: Beyond on November 21, 2011, 04:27:55 PM
With LT history enabled I was getting constant crashes / restarts and had > 6.5 GB of backup history files. Disabling LT history and deleting the LT files made BT 90% more stable than it was but there's still a long way to go in that department. Don't take me wrong, I love BT but there are some nagging stability problems that make it a challenge for those of us with a lot of WUs passing through. Not to tell you what to do but maybe put the new features on hold until the issues are worked out.
When I don't get crash reports they never get solved, because I haven't seen any crashes myself for a long time. And I got a lot of WU's on my computers.
Maybe the average of > 5 WUs completing/minute is causing me to have more crashes, but shouldn't BT be able to handle that? The fact is if I try to use long term history BT starts to crash once the file sizes start to build. By crash reports, do you mean dmp files? Is there a way to make them smaller? I only have 1 from today since LT history is disabled. Before that they were filling my HD.
Also I've been testing closing BOINC clients on the remote machines and restarting them. BT v1.27 shows the client as reconnected but usually does not show the clients tasks until BT is exited and restarted. Then everything is shown correctly again.
Quote from: Pepo on November 21, 2011, 07:24:26 PM
I've then restarted BT - a lot of entries in notices.xml disapeared.
QuoteCould you mail me a notices.html file.
(Sending files per e-mail.)
The problem is probably solved in 1.28, it was in the Notice from BOINC. They where added repeatedly, but only sometimes.
Quote from: Beyond on November 21, 2011, 08:53:42 PM
Maybe the average of > 5 WUs completing/minute is causing me to have more crashes, but shouldn't BT be able to handle that? The fact is if I try to use long term history BT starts to crash once the file sizes start to build. By crash reports, do you mean dmp files? Is there a way to make them smaller? I only have 1 from today since LT history is disabled. Before that they were filling my HD.
Also I've been testing closing BOINC clients on the remote machines and restarting them. BT v1.27 shows the client as reconnected but usually does not show the clients tasks until BT is exited and restarted. Then everything is shown correctly again.
I have one machine that runs 12 SETI fermi tasks on, so I get 5 WU's/minute sometimes. There shouldn't be any problems.
But as the history grows very quickly, it's not wise to keep a long history. On these machines it may be better to keep the history for a couple of hours, just to check if something goes wrong.
I need the dmp files, http://www.7-zip.org/ (http://www.7-zip.org/) Is by far the best program to compress them. Use compression level: Ultra LZMA.
You can use the free dropbox program.
I've never been able to reproduce connection problems unfortunately. If you come up with a way to reproduce them, let me know.
Quote from: Beyond on November 20, 2011, 04:09:49 PM
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.
Quote from: fred on November 22, 2011, 11:18:36 AM
I need the dmp files, http://www.7-zip.org/ (http://www.7-zip.org/) Is by far the best program to compress them. Use compression level: Ultra LZMA.
You can use the free dropbox program.
I've never been able to reproduce connection problems unfortunately. If you come up with a way to reproduce them, let me know.
Should be there now. That's a great archiver, compressed the dmp file to less than 2/3 the size of zip.
Quote from: fred on November 22, 2011, 11:21:28 AM
Quote from: Beyond on November 20, 2011, 04:09:49 PM
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 :)