Messages

JJ amigo - I am running Boinc 6.10.56 on all my systems. BoincTasks is level 0.71, and TThrottle is 2.10.
I turned off the Win7 Firewall, and everything worked perfectly. Scan found all the Win7 systems, they were connected, Boinc Yes was seen - no problems. My XP system is running Symantec Firewall, and it's setting are obviously correct, but I can't find out what to do on the Win7 firewall settings to get WIn7 to work.
At least we now know that its not Boinc, BoincTasks or Tthrottle - is the &^*&^*% Win7 firewall.

Hola Corsair, I've not seen you on the forum for awhile, it's good to see a post from you again.  Have you been sailing the 7 seas?

OK Raul, I'm glad you've been able to localize the problem at least.  A couple of points:

• BoincTasks 0.71 does not include the change that allows Find to use the MachineName reported by Tthrottle for Add selected - you should update to the latest version at URL BoincTasks 0.72 Beta
• BOINC 6.10.56 had issues in other areas - I'd recommend update all your hosts to 6.10.58 unless you have a specific problem with it

When you speak of the Win 7 firewall I assume you mean the built-in firewall provided by Microsoft with the OS.  I've used Kaspersky Internet Security on all my computers for awhile now, so the native firewall is turned off.  But now that I have a machine with Win 7_x64, I'll turn off Kaspersky, fall back on the system firewall, and see what I can come up with, as Corsair offered to do.  I'll get back to you on that.

[<unauthorized>]

Thanks JJ - I have got Throttle installed  correctly as per your instructions, and it is working well on all systems. However, it's still only the XP system that is connected to localhost. No sure what I should do next.

Well, I figured out what my problem was: I had (temporarily) installed BOINC 6.11.6(β) on all my hosts, and it wasn't responding (or incorrectly?) to the Scan or Find queries from BoincTasks.  It may be that this function isn't implemented in the beta build, though it is sending XML to BoincTasks readily enough.  I rolled all hosts back to 6.10.58 (Recommended version) and all's well now with "Yes ,Connected" or "Yes ,Password" in the BOINC column of Find computers.  I repeated Fred's debug mode test on a Scan address range and got:

27 August 2010 - 22:34:03 , SendRecieve ---- Recieved from Server: <boinc_gui_rpc_reply><unauthorized/></boinc_gui_rpc_reply>

27 August 2010 - 22:34:03 , SendRecieve ---- Recieved from Server: <boinc_gui_rpc_reply><unauthorized/></boinc_gui_rpc_reply>

27 August 2010 - 22:34:04 , SendRecieve ---- Recieved from Server: <boinc_gui_rpc_reply><unauthorized/></boinc_gui_rpc_reply>

27 August 2010 - 22:34:04 , SendRecieve ---- Recieved from Server: <TThrottle><HN:Velocity_MX228><PV 2.10><AC 1><TC 62><TG 79><NV 1><NA 0><DC 100><DG 100><CT0 61.1><CT1 54.0><CT2 59.0><CT3 61.7><GT0 79.0><GT4 0.0><GT5 0.0>
2

(Yes, only 1 host had Tthrottle running during the test.)  In other developments, I upgraded one of my remote hosts today to Windows 7.  And its BOINC client (v6.10.58) is connecting to BoincTasks without problem.  I'll be interested to know from Fred if <unauthorized> is the correct response to a Scan  Or do I still have a problem with my remote_hosts.cfg?  I look forward to BT 0.73 with the expanded logging

Add: The Find computers dialog, logs additional information in the log. (IP, BOINC reply). (done V 73 )
.

Regarding your problem, Raul, I don't know if any of that stuff helps - maybe the BOINC client version on your remotes?  I reviewed your posts above, and a few things tickled my brain:

1) If (a) you are running BoincTasks 0.72+, and (b) you have Tthrottle installed on the remotes, you should have a white checkbox and be able to tic it for an "Add selected" -- regardless of the status of the BOINC client, in either a Scan address range or a Find.

2) On the main Computers display, you should be able to do a Computer>New computer, manually enter the IP address & Password, and assign BoincTasks "nickname" (that need not match the computer's real name).  You don't need to do a scan or find for that.  (Never use an IP address for the localhost, enter only "localhost".  Also don't use the IP "alias" 127.0.0.1 - trust me, I learned that one the hard way.

3) The Password entered in the Computers tab must match that in the remote client's gui_rpc_auth.cfg file.  This is NOT the password of your account on the host computer.  Hopefully you have replaced BOINC's original randomly generated password (viz. "57e292b69fff39d4da30ab6c83c9c83e") with something you can remember, and the same one on all hosts  

4) All of Fred's advice above still applies.

5) If you do those things and still can't see your remotes in BoincTasks, I have to wonder about your connectivity.  Are all your remotes on the same subnet as localhost?  Is the subnet mask set correctly?  If not on the same subnet, does your router have a hardware firewall that might be locking off certain ports?  All the standard Network Manager-type questions in that vein.

Since you're talking about the gadget:

Sometime after the gadget changes introduced back in ~v0.63/64 (I think), I started seeing running tasks inappropriately shown in the high priority color (yellow on my system). Right now with 3 hosts, a total of 8 CPU cores & 1 GPU, the gadget is showing 8 of 9 running tasks in yellow, the remaining task in normal green.  On the tasks display, only the 4 CPU & 1 GPU tasks on a single host are (correctly) shown in Panic Mode.  The other 2 dual core machines are both shown in normal Running mode.

I've looked for a pattern in this behavior, but haven't found one.  Sometimes the gadget displays colors matching the Tasls display   I don't use the gadget a lot, so this hasn't been a high priority for me.  But since you mentioned it...

Hi guys - I've tried everything I can think of, but no change. From the tests above, maybe I should install Throttle - any thoughts?

Raul,

I won't presume to speak for Fred while he's "out of town", but Tthrottle is a useful utility, it coexists with BoincTasks like it was designed to (because it was) and it at least works around the problem of scanning/finding computers in BoincTasks (as of the latest BT release v0.72).  That is to say BT can use the hostname returned by Tthrottle in a Find to "Add selected"  Also, you will be able to see your CPU/GPU temperatures plus throttling activity on your BT Tasks display, as an added bonus.

Tthrottle needs a bit of customizing after you install it - setting up rules for throttling etc., but not too strenuous.  One thing you must do, on the Preference tab, is to check "Enable BoincTasks" for the communication with BT to work.  (On BT's Extra>BoincTasks settings>General tab, you will find a corresponding "Connect to TThrottle" checkbox to enable completion of this link & the display of temperatures.)  Once Tthrottle is up and running with "Enable BoincTasks" checked, on the BT Find computers dialog you will see Yes in the Tthrottle column of each found computer indicating that the handshake is working.  Once a computer is added and active on the main Computers display, the Tthrottle version number (currently 2.10) will appear in the appropriate column (similar to the BOINC version number in its column) as long as BT is receiving data from it.  

Tthrottle installation/configuration is pretty straightforward, and its FAQ has good information.  But if you run into problems I'm sure you can find help in its Questions topic.

I didn't see any <boinc_gui_rpc_reply> anywhere - neither did a string search of the entire log

That's not good. Do you use names or numbers for the IP. As far as I can see the first.

[duh]I knew that[/duh].  Nope, just numbers - here's a "re-read config" message stream from my localhost, with the content of remote_hosts.cfg:

console

417         8/26/2010 09:41:05   Re-reading cc_config.xml   
418         8/26/2010 09:41:05   Config: GUI RPC allowed from:   
419         8/26/2010 09:41:05   Config:   192.168.0.1   
420         8/26/2010 09:41:05   Config:   192.168.0.2   
421         8/26/2010 09:41:05   Config:   192.168.0.3   
422         8/26/2010 09:41:05   Config:   192.168.0.4   
423         8/26/2010 09:41:05   Config:   192.168.0.5   
424         8/26/2010 09:41:05   Config:   192.168.0.6   
425         8/26/2010 09:41:05   Config:   192.168.0.7   
426         8/26/2010 09:41:05   Config:   192.168.0.8   
427         8/26/2010 09:41:05   Config:   192.168.0.9   
428         8/26/2010 09:41:05   Config:   192.168.0.10   
429         8/26/2010 09:41:05   Config:   192.168.0.11   
430         8/26/2010 09:41:05   Config:   192.168.0.12   
431         8/26/2010 09:41:05   Config:   192.168.0.13   
432         8/26/2010 09:41:05   Config:   192.168.0.14   
433         8/26/2010 09:41:05   Config:   192.168.0.15   
434         8/26/2010 09:41:05   Config:   192.168.0.16   
435         8/26/2010 09:41:05   Config:   192.168.0.17   
436         8/26/2010 09:41:05   Config:   192.168.0.18   
437         8/26/2010 09:41:05   Config:   192.168.0.19   
438         8/26/2010 09:41:05   Config:   192.168.0.20   
439         8/26/2010 09:41:05   Config:   192.168.0.21   
440         8/26/2010 09:41:05   Config:   192.168.0.22   
441         8/26/2010 09:41:05   Config:   192.168.0.23   
442         8/26/2010 09:41:05   Config:   192.168.0.24   
443         8/26/2010 09:41:05   Config:   192.168.0.25   
444         8/26/2010 09:41:05   Config:   192.168.0.26   
445         8/26/2010 09:41:05   Config:   192.168.0.27   
446         8/26/2010 09:41:05   Config:   192.168.0.28   
447         8/26/2010 09:41:05   Config:   192.168.0.29   
448         8/26/2010 09:41:05   Config:   192.168.0.30   
449         8/26/2010 09:41:05   Config:   192.168.0.31   
450         8/26/2010 09:41:05   Config:   192.168.0.32   
451         8/26/2010 09:41:05   Config:   192.168.0.33   
452         8/26/2010 09:41:05   Config:   192.168.0.34   
453         8/26/2010 09:41:05   Config:   192.168.0.35   
454         8/26/2010 09:41:05   Config:   192.168.0.36   
455         8/26/2010 09:41:05   Config:   192.168.0.37   
456         8/26/2010 09:41:05   Config:   192.168.0.38   
457         8/26/2010 09:41:05   Config:   192.168.0.39   
458         8/26/2010 09:41:05   Config:   192.168.0.40   
459         8/26/2010 09:41:05   Config:   192.168.0.41   
460         8/26/2010 09:41:05   Config:   192.168.0.42   
461         8/26/2010 09:41:05   Config:   192.168.0.43   
462         8/26/2010 09:41:05   Config:   192.168.0.44   
463         8/26/2010 09:41:05   Config:   192.168.0.45   
464         8/26/2010 09:41:05   Config:   192.168.0.46   
465         8/26/2010 09:41:05   Config:   192.168.0.47   
466         8/26/2010 09:41:05   Config:   192.168.0.48   
467         8/26/2010 09:41:05   Config:   192.168.0.49   
468         8/26/2010 09:41:05   Config:   192.168.0.50   
469         8/26/2010 09:41:05   Config:   192.168.0.51   
470         8/26/2010 09:41:05   log flags: file_xfer, sched_ops, task, cpu_sched   

I got tired of dynamically assigned IPs gumming up the login works, so I assigned static IPs at the router:

IP                      DeviceName              BTComputerName                   
192.168.0.2         VELOCITY_MX228      4+1
192.168.0.3         VGN-FZ320EB           dual 32
192.168.0.7         VGN-FW170J            console   (this is the BT localhost)

The long remote_hosts.cfg is left over from the days of dynamic IPs, since I didn't want anybody to get left out - I also have a SoIP with 2 disk drives, an XBOX 360 and a PDA on my intranet.  (You see why I set static IPs to the 'computers' for BOINC login purposes )

Two questions for my own education:

• In my Case 1, should the scan show Tthrottle even though the Connect to Tthrottle option is cleared?
• Would the scan still pick up Tthrottle if its Enable BoincTasks option is cleared?

Back to you, Fred.

But if you can both do the following:

--SNIP--

I got curious, so I set up 3 test cases (all hosts are WinVista SP2, all BOINC clients v6.11.6):

Case 1 - Per Fred's instructions

Preconditions:
BOINC clients all running
All computers correctly listed by IP (except 'localhost') in Computers, showing status Connected
Tthrottle connect disabled on BT but Tthrottle still running on all computers
Temp display disappeared from Tasks
Tthrottle version disappeared from Computers

Action:
Scan address range

Result:
All 3 computers found
Tthrottle still Yes on Find computers
BOINC Yes absent on Find computers

Log entries:
26 August 2010 - 05:50:10 , SendRecieve ---- Recieved from Server: <TThrottle><HN:VGN-FW170J><PV 2.10><AC 0><TC 56><TG 0><NV 0><NA 0><DC 100><DG -1><CT0 55.8><CT1 56.0><GT4 0.0><GT5 0.0>
26 August 2010 - 05:50:10 , SendRecieve ---- Recieved from Server: <TThrottle><HN:Velocity_MX228><PV 2.10><AC 1><TC 62><TG 80><NV 1><NA 0><DC 100><DG 100><CT0 61.2><CT1 54.0><CT2 61.1><CT3 60.0><GT0 80.0><GT4 0.0><GT5 0.0>
26 August 2010 - 05:50:10 , SendRecieve ---- Recieved from Server: <TThrottle><HN:VGN-FZ320EB><PV 2.10><AC 1><TC 67><TG 15664056><NV 0><NA 0><DC 100><DG -1><CT0 64.7><CT1 67.2><GT4 0.0><GT5 0.0>

Case 2 - Shut down Tthrottle also

Preconditions:
Tthrottle connect disabled
Tthrottle shut down on all computers
Other preconditions as Case 1 above

Action:
Scan address range

Result:
No computers found
Tthrottle & BOINC Yes absent on Find computers


Log entries:
26 August 2010 - 06:06:38 , SendRecieve ---- Recieved from Server:
26 August 2010 - 06:06:38 , SendRecieve ---- Recieved from Server:
26 August 2010 - 06:06:39 , SendRecieve ---- Recieved from Server:

Case 3 - Bright idea eliminate the firewall/application control suite as a cause

Preconditions:
Disabled all Kaspersky Internet Security v11.0.1 protections on all computers
Other preconditions as Case 2 above

Action:
Scan address range

Result:
No computers found
Tthrottle & BOINC Yes absent on Find computers
All "Invalid Socket" (Possibly because the Windows Firewall took over from Kaspersky and slammed the door(s)?)

Log entries:
26 August 2010 - 06:51:45 4+1, Connect ---- Invalid Socket
26 August 2010 - 06:51:45 console, Connect ---- Invalid Socket
26 August 2010 - 06:51:45 dual 32, Connect ---- Invalid Socket
26 August 2010 - 06:51:46 GetUserDirectory3 ---- C:\Users\jjwhalen\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 06:51:46 GetUserDirectory3 ---- C:\Users\jjwhalen\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 06:51:46 GetUserDirectory3 ---- C:\Users\jjwhalen\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 06:51:47 console, Connect ---- Invalid Socket
26 August 2010 - 06:51:47 4+1, Connect ---- Invalid Socket
26 August 2010 - 06:51:47 dual 32, Connect ---- Invalid Socket
26 August 2010 - 06:51:51 console, Connect ---- Invalid Socket
26 August 2010 - 06:51:51 dual 32, Connect ---- Invalid Socket
26 August 2010 - 06:51:51 4+1, Connect ---- Invalid Socket
26 August 2010 - 06:51:57 4+1, Connect ---- Invalid Socket
26 August 2010 - 06:51:57 dual 32, Connect ---- Invalid Socket
26 August 2010 - 06:51:57 console, Connect ---- Invalid Socket
26 August 2010 - 06:51:58 , SendRecieve ---- Recieved from Server:
26 August 2010 - 06:51:58 , SendRecieve ---- Recieved from Server:
26 August 2010 - 06:51:58 , SendRecieve ---- Recieved from Server:
26 August 2010 - 06:51:59 , Connect ---- Invalid Socket
26 August 2010 - 06:51:59 , Connect ---- Invalid Socket
26 August 2010 - 06:51:59 , Connect ---- Invalid Socket
26 August 2010 - 06:52:03 console, Connect ---- Invalid Socket
26 August 2010 - 06:52:03 4+1, Connect ---- Invalid Socket
26 August 2010 - 06:52:03 dual 32, Connect ---- Invalid Socket
26 August 2010 - 06:52:09 dual 32, Connect ---- Invalid Socket
26 August 2010 - 06:52:09 4+1, Connect ---- Invalid Socket
26 August 2010 - 06:52:09 console, Connect ---- Invalid Socket
26 August 2010 - 06:52:15 dual 32, Connect ---- Invalid Socket
26 August 2010 - 06:52:15 4+1, Connect ---- Invalid Socket
26 August 2010 - 06:52:15 console, Connect ---- Invalid Socket
26 August 2010 - 06:52:17 GetUserDirectory3 ---- C:\Users\jjwhalen\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 06:52:17 GetUserDirectory3 ---- C:\Users\jjwhalen\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 06:52:17 GetUserDirectory3 ---- C:\Users\jjwhalen\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 06:52:17 4+1, Connect ---- Invalid Socket
26 August 2010 - 06:52:17 dual 32, Connect ---- Invalid Socket
26 August 2010 - 06:52:17 console, Connect ---- Invalid Socket

I didn't see any <boinc_gui_rpc_reply> anywhere - neither did a string search of the entire log

Fred,

I'm following this thread with interest, since I raised this issue some days ago in the BT 0.71 testing thread:

1) ...
You can only set a check, when the BOINC or TThrottle column show a Yes.

I reviewed the Manual and found

Finding TThrottle and not BOINC (missing yes), indicates a missing remote_hosts.cfg or a missing entry in the file.

but I definitely have remote_hosts.cfg on all my boxes & as far as I know it's complete.  Certainly I can use BM to log onto any machine from any other machine using either IP or machine_name.  So what exactly does

a missing entry in the file

refer to? I'll be glad to tweak my remote_hosts.cfg(s) any way I need to

Beginning with v0.72 I can now set a checkmark in Find computers as long as Tthrottle is running on the host, because of

Changed: Dialog find computers: Scan address range will now use the host name found by TThrottle.

and that's very helpful.  But I still don't get a Yes under BOINC and I'd still like to know: what does the BT Manual mean by a missing entry in the remote_hosts.cfg  My remote_host.cfg's are built per the BOINC Manual as far as I know.  As I said before, it's good enough for each computer to log onto each of the others using BOINCManager (reverified), so what is BT looking for that BM isn't?

I followed the advice you gave RaulB above

In 0.72 use "Scan address range" and see if you can find your computers.
If you don't see a yes in the BOINC column check the log of that computer. Most of the time you see an entry, like refused,

but I didn't see any such entry.  (BTW from past debugging experience, I believe the exact form you're looking for is "unable to resolve hostname..." )

When you added the (much appreciated) project filter to the Messages display, you obviously set it up to key on the Project value; however anything with a null Project value is also passed by the filter.  So client messages like benchmarks, changes to Preferences, etc. are also displayed.  When I filter for, e.g., Rosetta, that really is all I want/need to see.

Could you maybe set a filter option for "Client Messages," and send anything with a null Project value there instead?  (And exclude them from the other filter options of course.)

A couple of GUI items, hopefully not too strenuous:

1) Please consider moving the Rules tab from Settings to a separate menu item (i.e., Extra>Rules) with an expandable window to allow for long application names & rule titles.  Also request that the new Rules window ( ) remember changes to its own size/position, plus changes to the column width settings, when exiting BT (which BTW the current Settings>Rules tab doesn't).

2) The Project & Task Properties sheets are currently fixed-dimension windows.  Please also consider making them re-sizable windows with memory of the last size & screen position.

More stuff for the Registry?  

To make sure it matches any project with world in it, not just the beginning.
FAQ already updated.

(2 cool)

As you already noted spaces are removed from the text.
WORLD COMMUNITY GRID must be WORLD%20COMMUNITY%20GRID
%20 = space.

Makes sense...I thought about trying that, but was in a hurry so just truncated as noted above.  That works OK until there's another project beginning "WORLD"    Anyway, thanks for the clarification.  Maybe a good note for the FAQ?

Three computers are monitored by BT, let's call them 1 (localhost), 2 and 3 (both remote).  After switching to the Computers tab and unchecking one of the remote boxes (#2), then switching back to the Tasks tab, the Extra --> Allow network communication has the following listed:  1, 3, 1, 2, 3.

The first 1 and 3 work, but highlighting any of the 1, 2, or 3 below those causes BT to lockup and the machine becomes unusable until BT is terminated.  I have waited over 5 minutes and BT does not crash and restart, it just stays locked up.   

Good catch, BobCat13!  I have a similar setup - localhost & 2 remotes.  After not unchecking a remote host, but after BT 0.71 had been running for ~30 hours, I opened the Extra>Allow network communication> submenu to find an apparently infinite repitition of the 3 host names (full page height with scroll arrows top & bottom).  The submenu couldn't be manipulated or canceled, and BT locked up as above.  I killed BT via Process Explorer (don't cringe, Fred ) and restarted.  The behavior did not repeat after restart -- the Extra>Allow network communication> submenu was normal and worked as designed.  I'll check again after longer uptime.

I've not seen this problem before in earlier releases, even after a week of (BT) uptime.  But I don't recall any announced changes in this area of the app

Re: (from V0.70)

-Changed: Tasks: Don't show the checkpoint when a task is: Ready to report, uploading or in error.

I should have remembered this one - could you add "Aborted" to this group (no rush, maybe after the trip to France)

Retirement  , I think I'm busier now than before.

That was me in 1990, when I retired for the first time (from the Submarine Service).  Now I'm retired for the third time, and a trip to the Dog Park is as close to a day's work as I get (not counting volunteer public service)

To the Extra>Run CPU benchmarks>... and the Extra>Read Config file>... submenus, could you add an option for "All computers" ?  I for one modify my CC_CONFIG.xml options at least twice a day.

Gentle reminder:

If this requested menu change made it to the wishlist, I can't find it.  Could I get a go/no go please?

Missed that one.
But..... I'm preparing to go on a short trip to France to do some hiking, more hiking less Internet. I don't have Internet access.

Wasn't trying to rush you, it was low priority...I just noticed it apparently "fell in a crack"   In your own good time, and enjoy the trip to France.  Which reminds me, I have to take a short trip to the Dog Park - retirement is sweet.