The BoincTasks 1.16 trayicon won't show up anymore. I've searched the forum and found someone with the same problem. I had to install version 1.09 to get BoincTasks to work again. Upgrading to 1.16 after that doesn't resolve the problem. So I'm now running 1.09.
So here's a piece of today's log:
Start logging
07 November 2011 - 04:06:24 BoincTasks version: 1.16
07 November 2011 - 04:06:24 Language ---- User: 1033 (ENU), System: 1033 (ENU), Selected: 0 () Used: 1033 (ENU)
07 November 2011 - 04:06:26 Start BOINC client ---- The BOINC client was already running
07 November 2011 - 04:06:30 Maximum number of computers: Unlimited
07 November 2011 - 04:06:30 Computers ---- Labtop , 169.254.0.2
07 November 2011 - 04:06:30 Computers ---- Windows-7-PC , localhost
07 November 2011 - 04:06:30 Computers ---- Windows-7-PC Collatz , localhost
07 November 2011 - 04:06:30 Connect ---- Connected to: Host: 169.254.0.2, Labtop, Port: 31416, BOINC Version: 6.12.34
07 November 2011 - 04:06:36 Connect ---- Connected to: Host: 169.254.0.2, Labtop,Port: 31417, TThrottle Version: 5.10
07 November 2011 - 04:06:39 Connect ---- Connected to: Host: localhost, Windows-7-PC Collatz, Port: 9999, BOINC Version: 6.12.34
07 November 2011 - 04:07:11 Synchronize with manager ---- Completed on computer: Labtop
07 November 2011 - 04:15:30 Connect ---- Connected to: Host: localhost, Windows-7-PC, Port: 31416, BOINC Version: 6.12.34
Anthony.
Quote from: Mellowman on November 07, 2011, 04:10:39 PM
The BoincTasks 1.16 trayicon won't show up anymore. I've searched the forum and found someone with the same problem. I had to install version 1.09 to get BoincTasks to work again. Upgrading to 1.16 after that doesn't resolve the problem. So I'm now running 1.09.
Do you have the icon switched on: Show hidden icons (Verborgen pictogrammen weergeven).
Try V 1.25 and see it that one is still giving you problems. http://www.efmer.eu/boinc/boinc_tasks/download_beta.html (http://www.efmer.eu/boinc/boinc_tasks/download_beta.html) This is a beta but seems to be quite stable.
I deleted some logging, as it's not relevant to a missing icon.
Yes, my notification area always shows all icons. If you looked at the log it seemed BoincTasks didn't get all the way through it's startup, but was running according to the TaskManager. I'll try the 1.25 Beta-version.
----------
Ik heb alle iconen altijd aanstaan. BTW, mijn windows 7 is de Engelse versie. Ik zal 1.25 wel eens proberen.
Anthony
Quote from: Mellowman on November 07, 2011, 05:29:53 PM
I'll try the 1.25 Beta-version.
When you see text in the logging window the icon should already be drawn.
You can try starting BT again, in that case it tries to show the copy that's already running. But as you show a V 1.16 log, you can access the program.
I couldn't access the program, and stating up a new instance just gave me the response 'BoincTasks is already running'. You deleted the part of the log where it showed that it didn't startup properly. This piece of the log:
Start logging
07 November 2011 - 01:38:51 BoincTasks version: 1.16
07 November 2011 - 01:38:51 Language ---- User: 1033 (ENU), System: 1033 (ENU), Selected: 0 () Used: 1033 (ENU)
Start logging
07 November 2011 - 01:40:06 BoincTasks version: 1.16
07 November 2011 - 01:40:06 Language ---- User: 1033 (ENU), System: 1033 (ENU), Selected: 0 () Used: 1033 (ENU)
Start logging
07 November 2011 - 01:40:14 BoincTasks version: 1.16
07 November 2011 - 01:40:14 Language ---- User: 1033 (ENU), System: 1033 (ENU), Selected: 0 () Used: 1033 (ENU)
Start logging
07 November 2011 - 01:41:31 BoincTasks version: 1.16
07 November 2011 - 01:41:31 Language ---- User: 1033 (ENU), System: 1033 (ENU), Selected: 0 () Used: 1033 (ENU)
Start logging
07 November 2011 - 01:41:47 BoincTasks version: 1.16
07 November 2011 - 01:41:47 Language ---- User: 1033 (ENU), System: 1033 (ENU), Selected: 0 () Used: 1033 (ENU)
Start logging
07 November 2011 - 01:42:09 BoincTasks version: 1.16
07 November 2011 - 01:42:09 Language ---- User: 1033 (ENU), System: 1033 (ENU), Selected: 0 () Used: 1033 (ENU)
I tried multiple restarts in a row after ending the process in TaskManager each time. I tried rebooting, logging off/logging on, it all didn't work, so I installed v1.09, because I read in the other thread that going to an earlier version worked for that guy.
I downloaded the beta v1.25 and will give it a try later tonight.
Anthony.
Quote from: Mellowman on November 07, 2011, 05:53:53 PM
I installed v1.09, because I read in the other thread that going to an earlier version worked for that guy.
I downloaded the beta v1.25 and will give it a try later tonight.
Never a good idea to install an old version over an more recent one. The installer normally refuses to copy an older file.
Always remove the old version first.
I uninstalled the newer version first. The installer or the program (after being installed) does give an error when you install an older version over a newer one. I just uninstalled v1.09 and installed v1.25 but it has the same problem as v1.16. Here is the piece of the log after start of v1.25:
Start logging
07 November 2011 - 19:10:30 BoincTasks version: 1.25
07 November 2011 - 19:10:30 Language ---- User: 1033 (ENU), System: 1033 (ENU), Selected: 0 () Used: 1033 (ENU)
That's all.
No window, no icon, but it's running according to TaskManager.
I'm gonna uninstall this one and install v1.09 again.
Anthony.
This is something weird:
07 November 2011 - 04:06:30 Computers ---- Windows-7-PC , localhost
07 November 2011 - 04:06:30 Computers ---- Windows-7-PC Collatz , localhost
You can set up only one localhost, maybe this is one of the problems.
I like to see the logging of V 1.25 to see is the logging shows something.
I run Collatz in a second directory on my second video card. V1.09 has no problems with it and v1.16 had no problems with it either. I'm using port 9999 to connect to my second BOINC client. If I use both videocards (GTX-550 & GF8600GT) in 1 BOINC all project that can use the GTX-550 will try to use the 8600GT too resulting in errors. So I start normail BOINC with a cc_config.xml file with the setting <use_all_gpus>0</use_all_gpus> and in my second BOINC directory with <use_all_gpus>1</use_all_gpus> and <ignore_cuda_dev>0</ignore_cuda_dev>. Only Collatz seems to run on my 8600GT and I dont want the card to go to waste. My GTX-550 runs all other GPU projects I run, SETI, GPUGrid, Einstein and MilkyWay.
(http://s7.postimage.org/6h9aw9bt7/Boinc_Tasks.jpg)
I don't run v1.25 as it won't give me access to the program. I can show you the logs of v1.09 to let you see that this setup works. V1.16 has run normally for a week too with this setup (I started using BoincTasks 1 week ago). I can show the daily logs from v1.16 too when it still worked.
Which log would you like? The daily log-file or the startup log-file (which is from v1.25; I guess v1.09 doesn't have this feature)?
Here's my daily log from nov 4th. It's the complete log-file:
Start logging
04 November 2011 - 15:05:43 BoincTasks is closing down all threads
04 November 2011 - 15:05:43 BoincTasks has closed down all threads
Start logging
04 November 2011 - 15:05:53 BoincTasks version: 1.16
04 November 2011 - 15:05:53 Language ---- User: 1033 (ENU), System: 1033 (ENU), Selected: 0 () Used: 1033 (ENU)
04 November 2011 - 15:06:00 Start BOINC client ---- The BOINC client was already running
04 November 2011 - 15:06:01 Maximum number of computers: Unlimited
04 November 2011 - 15:06:01 Computers ---- Labtop , 169.254.0.2
04 November 2011 - 15:06:01 Computers ---- Windows-7-PC Collatz , localhost
04 November 2011 - 15:06:01 Computers ---- Windows-7-PC , localhost
04 November 2011 - 15:06:01 Connect ---- Connected to: Host: localhost, Windows-7-PC Collatz, Port: 9999, BOINC Version: 6.12.34
04 November 2011 - 15:06:01 Connect ---- Connected to: Host: localhost, Windows-7-PC, Port: 31416, BOINC Version: 6.12.34
04 November 2011 - 15:06:01 Connect ---- Connected to: Host: 169.254.0.2, Labtop, Port: 31416, BOINC Version: 6.12.34
04 November 2011 - 15:06:07 Connect ---- Connected to: Host: localhost, Windows-7-PC,Port: 31417, TThrottle Version: 5.10
04 November 2011 - 15:06:07 Connect ---- Connected to: Host: 169.254.0.2, Labtop,Port: 31417, TThrottle Version: 5.10
04 November 2011 - 18:38:27 Synchronize with manager ---- Completed on computer: Labtop
04 November 2011 - 18:38:27 Synchronize with manager ---- Completed on computer: Windows-7-PC
04 November 2011 - 18:38:28 Synchronize with manager ---- Completed on computer: Windows-7-PC Collatz
No problems that day and I didn't reboot (or just once) that day I guess. That's why it's so small.
The second BOINC client I have to start with a shortcut, and I always have a command window open although it's minimized to the taskbar. This technique to run like this is described on one of the BOINC or project forums. It also worked with BOINC- manager. I just had to start a new manager window with IP 127.0.0.1:9999 as computer name.
The 1.26's new modification "Changed: Check if is more than one localhosts in the IP Address column. Rename the second one to localhost2." will completely deny such option (except using IP (which may keep changing) or DNS name (which might be not available at home)), instead of fixing the problem...
I'd personally modify one of the localhosts just if both machines' ports would (explicitly or implicitly) be equal.
It's the same machine/computer. So I would need to use the IP-adress of the computer. I have a static one from my LAN (169.254.0.1) and I can make the Wireless LAN (192.168.x.x) static too if needed. Just have to change it in the internet router/modem. Would that work in v1.26 if I used the LAN IP (169.254.0.1)?
But first let's try solving the problem v1.16 and v1.25 have on my system.
Anthony.
Quote from: Pepo on November 08, 2011, 12:34:50 PM
The 1.26's new modification "Changed: Check if is more than one localhosts in the IP Address column. Rename the second one to localhost2." will completely deny such option (except using IP (which may keep changing) or DNS name (which might be not available at home)), instead of fixing the problem...
I'd personally modify one of the localhosts just if both machines' ports would (explicitly or implicitly) be equal.
The problem is localhost is used by BT to ID the local machine. All sorts of things rely on the name localhost.
So finding 2 localhost can mess things up.
Start notepad as administrator and go to: C:\Windows\System32\drivers\etc
Open host no extension!
Add the line:
localhost localhost2
Now you should be able to use localhost2, you now need to give localhost2 a password as only the localhost is read from the password file.
Quote from: Mellowman on November 08, 2011, 11:45:13 AM
I don't run v1.25 as it won't give me access to the program. I can show you the logs of v1.09 to let you see that this setup works. V1.16 has run normally for a week too with this setup (I started using BoincTasks 1 week ago). I can show the daily logs from v1.16 too when it still worked.
Which log would you like? The daily log-file or the startup log-file (which is from v1.25; I guess v1.09 doesn't have this feature)?
The startup log is only needed for events that take place before the program is able to start the main logging. Build in for debugging crashes that occur early in the start up.
So I need the main log from startup (V 1.26 if possible) , after BT has ran for 5 minutes.
You can email the file. b#o#i#n#c#at#efmer.eu (without the # and at = @)
I've changed the host file. Changed localhost to localhost2 in BoincTasks v1.09 (for Windows-7-PC Collatz). It already had a password so no change there. I uninstalled v1.09 (after starting BoincManager so my projects keep running). I installed V1.25 and after posting this message it has run for 5 minutes so I'm gonna send you the logs (startup and daily logs).
Still no main window or trayicon. The daily log only shows those 2 lines posted earlier (for v1.25).
Anthony.
I reinstalled v1.09 again, but when I change localhost to localhost2 in BT it will just change it back to localhost. I even added a new computer localhost2 port 9999 with password and it changed the IP back to localhost.
Maybe I should just use the LAN IP 169.254.0.1. What do you think?
Anthony.
Quote from: Mellowman on November 08, 2011, 01:52:14 PM
Still no main window or trayicon. The daily log only shows those 2 lines posted earlier (for v1.25).
Anthony.
You can move the working copy of the program to a different location, so can stay on using it, while testing.
Copy the whole: C:\Program Files\eFMer\BoincTasks folder and move it to an 116 folder.
Testing V 1.26:
Copy C:\Program Files\eFMer\BoincTasks\examples\log log.xml to C:\Program Files\eFMer\BoincTasks\log.
Open notebook as administrator and edit C:\Program Files\eFMer\BoincTasks\log log.xml
Set everything to 1, except <fileonly>
<history_fetching> 1 </history_fetching>
<tasks> 1 </tasks>
<tthrottle_communication> 1 </tthrottle_communication>
<tthrottle_data> 1 </tthrottle_data>
<tthrottle_read> 1 </tthrottle_read>
<tthrottle_graphic> 1 </tthrottle_graphic>
<snooze> 1 </snooze>
<temperature_gpu> 1 </temperature_gpu>
<directory> 1 </directory>
<search_computers> 1 </search_computers>
<connecting> 1 </connecting>
<notices> 1 </notices>
<webserver> 1 </webserver>
<heap_check> 1 </heap_check>
Lets see if this produces any output.
Quote from: Mellowman on November 08, 2011, 02:05:12 PM
Maybe I should just use the LAN IP 169.254.0.1. What do you think?
What works works.
The extra debug logging only shows if in the logging window the "debug mode" check is set.
So you have to check that one first and next try the latest version.
In the mean time I will build a test version.
I just mailed the logs. There's no extra data in the logfiles after changing the xml-file.
I have tried using LAN IP 169.254.0.1 but it didn't work (yet) in v1.09 (remember that v1.16 also doesn't work, like v1.25). Maybe for the LAN IP to work I have to change something in the Boinc files to allow for remote connection, I don't know.
Fred, I just replied to your email, so it's send to your private email adres, not the one you supplied earlier in this thread.
You just posted before I could post.
I enabled debug mode in v1.09, I will stop it and start v1.25 again. Reacting will take a bit slower now as I have company.
Anthony.
I've emailed you the new logs, but there wasn't any extra logging data as I've said in the mail and will show in the attached logs.
Anthony.
I'm almost ready with a test version, expect one tomorrow.
Okay.
Anthony.
Test version: 1.27 TEST http://www.efmer.com/download/boinc/boinc_tasks/unified/setup_32_64_boinc_tasks_1_2_7_TEST.exe (http://www.efmer.com/download/boinc/boinc_tasks/unified/setup_32_64_boinc_tasks_1_2_7_TEST.exe)
This version does start up. But now my main Boinc directory is recognized as localhost2 (because of the change in the hosts file yesterday) and not connected. My secondary Boinc directory (Boinc2 with only Collatz) is recognized as localhost and connected.
So how do I let them connect to both clients?
Anthony.
Quote from: Mellowman on November 09, 2011, 10:49:37 AM
This version does start up. But now my main Boinc directory is recognized as localhost2 (because of the change in the hosts file yesterday) and not connected. My secondary Boinc directory (Boinc2 with only Collatz) is recognized as localhost and connected.
So how do I let them connect to both clients?
You can change the host file, see previous post.
Add the line:
localhost localhost2
So localhost2 = localhost.
Or you can simply use the ip address or the local machine.
And I would like to see both log files, to see what's going on, because the problem may still be there.
The program won't shutdown properly. I placed the edited log.xml in BoinTasks\Log, put debug mode on, I will kill the program, restart it, let it run for 5 minutes and send you the logs.
I just mailed you the logs.
Anthony.
Quote from: Mellowman on November 09, 2011, 11:39:27 AM
The program won't shutdown properly. I placed the edited log.xml in BoinTasks\Log, put debug mode on, I will kill the program, restart it, let it run for 5 minutes and send you the logs.
Seems to be working.
Edit the log file to remove all debugging except the connection.
<history_fetching> 0 </history_fetching>
<tasks> 0 </tasks>
<tthrottle_communication> 0 </tthrottle_communication>
<tthrottle_data> 0 </tthrottle_data>
<tthrottle_read> 0 </tthrottle_read>
<tthrottle_graphic> 0 </tthrottle_graphic>
<snooze> 0 </snooze>
<temperature_gpu> 0 </temperature_gpu>
<directory> 0 </directory>
<search_computers> 0 </search_computers>
<connecting> 1 </connecting>
<notices> 0 </notices>
<webserver> 0 </webserver>
<heap_check> 0 </heap_check>
Just changed the log.xml and started v1.27. It's still connecting to only 1 of the 2 Boinc-dirs (the primary one now is localhost and connected). The program still won't shutdown properly, I have to kill it in taskmanager. It's running for 5 minutes now. Let's see if it will now shutdown properly. I'll send you the logs.
Anthony.
Yesterday I think I forgot to put the log.xml file in the correct directory :o.
Anthony.
Quote from: fred on November 09, 2011, 10:34:24 AM
Test version: 1.27 TEST http://www.efmer.com/download/boinc/boinc_tasks/unified/setup_32_64_boinc_tasks_1_2_7_TEST.exe (http://www.efmer.com/download/boinc/boinc_tasks/unified/setup_32_64_boinc_tasks_1_2_7_TEST.exe)
BT 1.24 & 1.25 started erratically here too. Often the icon would not appear and the program would also not appear (set not to minimize on start) but the BT task would be in Task Manager with about .4 seconds of CPU time. I could get 1.25 to start by rebooting. 1.26 would not start at all. Tried 1.27 test version above and it started after about 90 seconds. Seems to be working well and for some reason now the localhost TT temp is showing in BT. In 1.25 the TT temp showed up about 1% of the time if that.
On my system it works too except that it won't close and I have to kill it in TaskManager. Can you check that on your system?
Anthony.
Quote from: Mellowman on November 09, 2011, 03:09:38 PM
On my system it works too except that it won't close and I have to kill it in TaskManager. Can you check that on your system?
It exited properly the 2 times I tried it, takes about 90 seconds to start though every time.
It starts immediatly on my system, except that it won't close. I just did a uninstall/install to see if that helped as I've been testing whole afternoon. It still won't close normally. I'll do a reboot as soon as my TV-recording is done, which is now I see. Hopefully that'll work.
Tried it a 3rd time, exited immediately. Took 90 seconds when I restarted it. Watched the process in Process Lasso, BT grabbed a whole CPU core for the 90 seconds that it took for the main window and icon to appear. Then it returned to its normal low CPU usage. The long start period always makes me a little nervous because of the BT start problems I've had post 1.21 :o
I'm still having connecting problems. Fred and I thoughed we solved it this afternoon, but we didn't actually. After my reboot it couldn't connect to 1 of my 2 clients on the same computer. I run a separate client for my old GF8600GT card which can only run Collatz. My other card is a GTX-500Ti. If I use them both with 1 client GPU-projects that can't use the 8600GT will still try to resulting in errors. And I didn't want to disable my 8600GT.
Now it won't connect to my main Boinc client, but if I start BoincManager en then start BT it does connect to both of them ???. BT still won't shutdown properly though. I still have to kill it in TaskManager.
Anthony.
Quote from: Beyond on November 09, 2011, 03:07:16 PM
BT 1.24 & 1.25 started erratically here too. Often the icon would not appear and the program would also not appear (set not to minimize on start) but the BT task would be in Task Manager with about .4 seconds of CPU time. I could get 1.25 to start by rebooting. 1.26 would not start at all. Tried 1.27 test version above and it started after about 90 seconds.
Seems to be in agreement with my observation of BT 1.26's delayed start (http://www.efmer.eu/forum_tt/index.php?topic=852.msg5067#msg5067).
Possibly the kill was indeed not necessary, but more than a couple of seconds is (or at least was) highly unusual for starting BT.
Quote from: Beyond on November 09, 2011, 04:46:25 PM
Tried it a 3rd time, exited immediately. Took 90 seconds when I restarted it. Watched the process in Process Lasso, BT grabbed a whole CPU core for the 90 seconds that it took for the main window and icon to appear. Then it returned to its normal low CPU usage. The long start period always makes me a little nervous because of the BT start problems I've had post 1.21 :o
Which client is it connected to? While the CPU usage is high, what does the
Messages tab look like? Is the
Tasks tab correct?
The 1.27 test version has a build in timeout as old files are deleted.
There is also some additional logging in the startup log.
I like to see the startup log: "BoincTasks Startup.log", that should show what BT is doing, time wise.
Quote from: Pepo on November 09, 2011, 05:03:58 PM
Quote from: Beyond on November 09, 2011, 04:46:25 PM
Tried it a 3rd time, exited immediately. Took 90 seconds when I restarted it. Watched the process in Process Lasso, BT grabbed a whole CPU core for the 90 seconds that it took for the main window and icon to appear. Then it returned to its normal low CPU usage. The long start period always makes me a little nervous because of the BT start problems I've had post 1.21 :o
Which client is it connected to? While the CPU usage is high, what does the Messages tab look like? Is the Tasks tab correct?
Tried exiting and restarting 4 more times (8 in all so far), watching in Process Lasso. The exit is always immediate. The start always takes about 90 seconds (80-85 seconds CPU time). I was trying to get the darn toolbar icons all to stay on one line, no luck there until I disabled 2 of them that I never use anyway.
To answer your questions, I don't know what you mean by "Which client is it connected to?" The CPU usage is high until BT pops up on the desktop and the BT taskbar icon simultaneously appears, then the CPU usage immediately drops to well under 1%. There is no way to see the Messages or Tasks tab until the BT program window pops up after ~90 seconds.
So far the 1.27 test version is the first one that worked at all properly here since 1.21. A very nice improvement IMO. :)
Quote from: Beyond on November 09, 2011, 05:36:15 PM
To answer your questions, I don't know what you mean by "Which client is it connected to?" The CPU usage is high until BT pops up on the desktop and the BT taskbar icon simultaneously appears, then the CPU usage immediately drops to well under 1%. There is no way to see the Messages or Tasks tab until the BT
Startup file? So I can see where the 90 seconds go.
He means your startuplog:
C:\Users\Anthony\AppData\Roaming\eFMer\BoincTasks\log\BoincTasks Startup.log
Put your username where mine (Anthony) is.
Quote from: fred on November 09, 2011, 05:21:06 PM
I like to see the startup log: "BoincTasks Startup.log", that should show what BT is doing, time wise.
11/09/2011, 11:43:57 -- Startup: BoincTasks Version: 1.27
11/09/2011, 11:43:57 -- Set exeption handler
11/09/2011, 11:43:57 -- Read arg:
11/09/2011, 11:43:57 -- Language detection
11/09/2011, 11:43:57 -- Language registry: 1033
11/09/2011, 11:43:57 -- Language selected: 1033
11/09/2011, 11:43:57 -- Read translation
11/09/2011, 11:43:57 -- Close translation, OK
11/09/2011, 11:43:57 -- Started logging
11/09/2011, 11:43:57 -- Open translation override
11/09/2011, 11:43:57 -- Close translation override, OK
11/09/2011, 11:43:57 -- User: 1033 (ENU), System: 1033 (ENU), Selected: 1033 (ENU) Used: 1033 (ENU)
11/09/2011, 11:43:57 -- Mutex is not set
11/09/2011, 11:43:57 -- DeleteFiles in folders:D:\Apps\BoincTasks\Data\crash\*.*
11/09/2011, 11:43:57 -- Deleted crash files
11/09/2011, 11:43:57 -- DeleteFiles in folders:D:\Apps\BoincTasks\Data\history\backup\*.*
11/09/2011, 11:44:18 -- Timeout
11/09/2011, 11:44:18 -- Deleted history files
11/09/2011, 11:44:18 -- DeleteFiles in folders:D:\Apps\BoincTasks\Data\log\*.*
11/09/2011, 11:44:18 -- Deleted logging files
11/09/2011, 11:44:18 -- WSAStartup OK
11/09/2011, 11:44:18 -- Menu translations done
11/09/2011, 11:44:18 -- Created main window
11/09/2011, 11:44:18 -- computers.xml IP: 192.168.1.7
11/09/2011, 11:44:18 -- computers.xml IP: 192.168.1.4
11/09/2011, 11:44:18 -- computers.xml IP: 192.168.1.11
11/09/2011, 11:44:18 -- computers.xml IP: 192.168.1.9
11/09/2011, 11:44:18 -- computers.xml IP: 192.168.1.8
11/09/2011, 11:44:18 -- computers.xml IP: localhost
11/09/2011, 11:44:18 -- computers.xml IP: 192.168.1.6
11/09/2011, 11:44:18 -- computers.xml IP: 192.168.1.3
11/09/2011, 11:44:18 -- computers.xml IP: 192.168.1.15
11/09/2011, 11:44:18 -- Connect to BOINC clients
11/09/2011, 11:45:40 -- Startup finished
So far the localhost TT temp seems to be reporting most of the time, a nice improvement.
Quote from: fred on November 09, 2011, 05:39:14 PM
Quote from: Beyond on November 09, 2011, 05:36:15 PM
To answer your questions, I don't know what you mean by "Which client is it connected to?" The CPU usage is high until BT pops up on the desktop and the BT taskbar icon simultaneously appears, then the CPU usage immediately drops to well under 1%. There is no way to see the Messages or Tasks tab until the BT
Startup file? So I can see where the 90 seconds go.
Nope, those were my answers to Pepo's questions :) :) :)
Quote from: Beyond on November 09, 2011, 05:55:19 PM
Here it is,
Also a nice log but not the one I wanted. ;D
See Anthony's link and replace the username.....
I edited my previous reply and replaced it with the correct log hopefully.
Part of the delay may be here:
11/09/2011, 11:43:57 -- DeleteFiles in folders:D:\Apps\BoincTasks\Data\history\backup\*.*
11/09/2011, 11:44:18 -- Timeout
BTW, the above directory has 6007 files using in excess of 6GB of disk space.
Quote from: fred on November 09, 2011, 06:14:19 PM
Quote from: Beyond on November 09, 2011, 06:04:14 PM
I edited my previous reply and replaced it with the correct log hopefully.
The problem:
11/09/2011, 11:43:57 -- DeleteFiles in folders:D:\Apps\BoincTasks\Data\history\backup\*.*
11/09/2011, 11:44:18 -- Timeout
The history scanning takes a bit long.
See my previous post. That accounts for 21 seconds but still leaves more than a minute. Should there be now 6009 files using in excess of 6GB of disk space?
Quote from: Beyond on November 09, 2011, 06:19:23 PM
See my previous post. That accounts for 21 seconds but still leaves more than a minute. Should there be now 6009 files using in excess of 6GB of disk space?
One thing at a time. ;D
In 1.26 there wasn't any timeout, so it could take a very long time.
Maybe BT is unable to delete the history files, can you check the file properties?
For the 1.27 release I will add a worker thread that deletes all the old history files. The thread will have a very low priority and can the garbage collection on its own.
I have to analize
Quote from: fred on November 09, 2011, 06:23:27 PM
Quote from: Beyond on November 09, 2011, 06:19:23 PM
See my previous post. That accounts for 21 seconds but still leaves more than a minute. Should there be now 6009 files using in excess of 6GB of disk space?
One thing at a time. ;D
In 1.26 there wasn't any timeout, so it could take a very long time.
Maybe BT is unable to delete the history files, can you check the file properties?
For the 1.27 release I will add a worker thread that deletes all the old history files. The thread will have a very low priority and can the garbage collection on its own.
I have to analize
1.26 didn't start even after an hour...
The folder was marked read only, the files are not. I removed the read only flag from the folder and BT put it back on when restarted. How many of those backup files do I need? can I delete some or most of them?
Quote from: Beyond on November 09, 2011, 05:36:15 PM
Quote from: Pepo on November 09, 2011, 05:03:58 PM
Which client is it connected to?
To answer your questions, I don't know what you mean by "Which client is it connected to?"
I've meant the BOINC client version. But is probably irrelevant for the rest of my questions, as you could not check the tabs.
My ...\history\backup folder (on one machine with a very small number of tasks being processed) contains 10.4 MB in 250 files, spanning 25.10.-9.11. - possibly because of
History's "keep 12 days + 0 hours" preference? The startup times are short now (2-3 seconds, full CPU use).
I'm gonna try the 1.27 version. ... Started fast too, delayed at most 4 seconds.
Quote from: Beyond on November 09, 2011, 03:07:16 PM
for some reason now the localhost TT temp is showing in BT. In 1.25 the TT temp showed up about 1% of the time if that.
Update: works for a while at least. Every once in a while I have to restart TT (5.43) to keep the localhost temps showing in BT 1.27.
Quote from: Pepo
I've meant the BOINC client version.
BOINC 6.12.41. Worked the same with 6.12.34.
I've had v1.16 working again, but I couldn't turn on 'start Boinc client at start' or 'stop Boinc client on exit'. With the first it wouldn't really startup again (no window, no trayicon, but running according to Taskmanager) and with the latter it would hang on exit and I had to kill it in Taskmanager. I had v1.25 running too, but it had the same problems besides the connection problems that I have with that version and v1.27. So the exit problem with v1.27 might have to do with 'stop boinc client on exit'.
I got them both running again because I deleted the BoincTasks registry key. But I've uninstalled them and got back to running v1.09 as this version at least works although I noticed that I don't have the option 'stop Boinc client on exit'.
That I can't use my LAN IP (169.254.0.1) or Wireless IP (192.168.1.x) is probably because of the Boinc client. I tested in BoincManager and there I can't use my LAN IP either. I've tried the option <allow_remote_gui_rpc>1</allow_remote_gui_rpc> in 'cc_config.xml' but that gave problems too.
So I don't know anymore how to solve those connection problems in v1.25 & v1.27 if 2 localhost entries aren't allowed.
Anthony.
Quote from: Beyond on November 09, 2011, 06:32:42 PM
The folder was marked read only, the files are not. I removed the read only flag from the folder and BT put it back on when restarted. How many of those backup files do I need? can I delete some or most of them?
:-X The folder should never never be read only, I will will add that to the testing.
That's the whole reason why it takes so long. The files should follow the folder settings.
You can delete any file older than 2 weeks, BoincTasks should take care of the rest.
Quote from: Mellowman on November 09, 2011, 10:25:59 PM
I've had v1.16 working again, but I couldn't turn on 'start Boinc client at start' or 'stop Boinc client on exit'. With the first it wouldn't really startup again (no window, no trayicon, but running according to Taskmanager) and with the latter it would hang on exit and I had to kill it in Taskmanager. I had v1.25 running too, but it had the same problems besides the connection problems that I have with that version and v1.27. So the exit problem with v1.27 might have to do with 'stop boinc client on exit'.
The client doesn't have any tray entry, so there is nothing to see except that it's running.
The client keeps on running and running if you exit BoincTasks. You have to check the "Stop client on exit" as well.
And as stated, I will test the dual BOINC connection problems.
I tested the dual BOINC setup and it works just fine with the 1.27 test version.
Instructions: http://www.efmer.eu/forum_tt/index.php?topic=856.0 (http://www.efmer.eu/forum_tt/index.php?topic=856.0)
Quote from: Mellowman on November 08, 2011, 11:45:13 AM
I run Collatz in a second directory on my second video card. V1.09 has no problems with it and v1.16 had no problems with it either. I'm using port 9999 to connect to my second BOINC client. If I use both videocards (GTX-550 & GF8600GT) in 1 BOINC all project that can use the GTX-550 will try to use the 8600GT too resulting in errors. So I start normail BOINC with a cc_config.xml file with the setting <use_all_gpus>0</use_all_gpus> and in my second BOINC directory with <use_all_gpus>1</use_all_gpus> and <ignore_cuda_dev>0</ignore_cuda_dev>. Only Collatz seems to run on my 8600GT and I dont want the card to go to waste. My GTX-550 runs all other GPU projects I run, SETI, GPUGrid, Einstein and MilkyWay.
Maybe a bit off topic but possibly a better way. The 8600 is power hungry and slow. Sell or give it away and get an ATI/AMD card to replace it. Even the 1st 40nm card, the HD4770 will FAR outproduce it in Collatz and uses much less energy. You should be able to get one on the cheap used. Then you can set Collatz to use ATI/AMD only and the rest of the projects to use NVidia. Voila, no more problems of this kind with BT. I'm running 4 machines with mixed ATI / NVidia cards and it's my configuration of choice. You may want to check to make sure that your MB supports mixed cards. Pretty much anything with the 790FX, 890FX and 990FX chipsets will do this. Not sure which intel based chipsets work but checking a few of the hardware forums will get you the anwer (the MB manufacturer support lines generally won't have a clue).
I don't pay the power bill, and I'm 'legally job incapable' so I have a low income. I just bought the GTX-550Ti a month ago just for crunching. The 8600GT still can crunch a mini-collatz in ~2hours. All my Collatz credits from last month are from that card. And I'm planning to buy/build a new computer with Intel iCore i7-2600K, Gigabyte Z68XP-UD5 (3x PCI-Express for videocards) motherboard etc., so I can buy new videocards later on.
My current system is a ASUS P5K-E Wifi-App motherboard with Intel C2D E6750 2666,66 MHz running at 3400 MHZ (8*425MHz) with DDR2-1066 MHz (running at 1064 MHz) with the 2 videocards mentioned (and a RAID config, TV cards).
Anthony.
It still won't connect to my main BOINC client unless the client is already running. So it also doesn't start it (while the option is on in preferences).
10 November 2011 - 16:29:43 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
And the program still hangs when I want to exit it. I have to kill it in TaskManager.
Anthony.
Quote from: Mellowman on November 10, 2011, 03:39:29 PM
It still won't connect to my main BOINC client unless the client is already running. So it also doesn't start it (while the option is on in preferences).
Check the BT logging.
The user that runs BT must have execute privileges to start the BOINC client: C:\Program Files\BOINC\boinc.exe
Is anyone else experiencing problems exiting BT?
If I turn off 'stop boinc client on exit' then I don't have problems exiting the program.
I will edit the log.xml and start logging.
Anthony.
Startup log:
11/10/2011, 16:58:07 -- Startup: BoincTasks Version: 1.27
11/10/2011, 16:58:07 -- Set exeption handler
11/10/2011, 16:58:07 -- Read arg:
11/10/2011, 16:58:07 -- Language detection
11/10/2011, 16:58:07 -- Language registry: 0
11/10/2011, 16:58:07 -- Language selected: 0
11/10/2011, 16:58:07 -- Read translation
11/10/2011, 16:58:07 -- Close translation, OK
11/10/2011, 16:58:07 -- Started logging
11/10/2011, 16:58:07 -- Open translation override
11/10/2011, 16:58:07 -- Close translation override, OK
11/10/2011, 16:58:07 -- User: 1033 (ENU), System: 1033 (ENU), Selected: 0 () Used: 1033 (ENU)
11/10/2011, 16:58:07 -- Mutex is not set
11/10/2011, 16:58:07 -- DeleteFiles in folders:C:\Users\Anthony\AppData\Roaming\eFMer\BoincTasks\crash\*.*
11/10/2011, 16:58:07 -- Deleted crash files
11/10/2011, 16:58:07 -- DeleteFiles in folders:C:\Users\Anthony\AppData\Roaming\eFMer\BoincTasks\history\backup\*.*
11/10/2011, 16:58:07 -- Deleted history files
11/10/2011, 16:58:07 -- DeleteFiles in folders:C:\Users\Anthony\AppData\Roaming\eFMer\BoincTasks\log\*.*
11/10/2011, 16:58:07 -- Deleted logging files
11/10/2011, 16:58:07 -- WSAStartup OK
11/10/2011, 16:58:07 -- Menu translations done
11/10/2011, 16:58:07 -- Created main window
11/10/2011, 16:58:08 -- computers.xml IP: localhost
11/10/2011, 16:58:08 -- computers.xml IP: localhost
11/10/2011, 16:58:08 -- computers.xml IP: 169.254.0.2
11/10/2011, 16:58:08 -- Connect to BOINC clients
11/10/2011, 16:58:08 -- Startup finished
Daily log:
Start logging
10 November 2011 - 16:58:07 BoincTasks version: 1.27
10 November 2011 - 16:58:07 Language ---- User: 1033 (ENU), System: 1033 (ENU), Selected: 0 () Used: 1033 (ENU)
10 November 2011 - 16:58:08 Maximum number of computers: Unlimited
10 November 2011 - 16:58:08 Computers ---- localhost get local password: (C:\ProgramData\BOINC\\gui_rpc_auth.cfg) 124a4ce72617dcb839f17ea33a5020af
10 November 2011 - 16:58:08 Computers ---- Windows-7-PC , localhost
10 November 2011 - 16:58:08 Computers ---- Windows-7-PC Collatz , localhost2
10 November 2011 - 16:58:08 Computers ---- Labtop , 169.254.0.2
10 November 2011 - 16:58:08 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:58:08 Connect ---- Try to connect to: Host: localhost2, Windows-7-PC Collatz, Port: 31418, Thread ID: 7496
10 November 2011 - 16:58:08 Connect ---- Try to connect to: Host: 169.254.0.2, Labtop, Port: 31416, Thread ID: 4656
10 November 2011 - 16:58:08 Connect ---- Connected to: Host: localhost2, Windows-7-PC Collatz, Port: 31418, BOINC Version: 6.12.34
10 November 2011 - 16:58:08 Connect ---- Connected to: Host: 169.254.0.2, Labtop, Port: 31416, BOINC Version: 6.12.34
10 November 2011 - 16:58:09 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:58:11 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:58:12 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:58:14 Connect ---- Connected to: Host: 169.254.0.2, Labtop,Port: 31417, TThrottle Version: 5.10
10 November 2011 - 16:58:14 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:58:15 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:58:17 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:58:18 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:58:20 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:58:21 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:58:23 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:58:24 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:58:26 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:58:27 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:58:29 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:58:30 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:58:32 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:58:33 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:58:35 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:58:36 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:58:37 Memory ----
PageFaultCount : 0x00002181 8K
PeakWorkingSetSize : 0x01F4A000 32808K
WorkingSetSize : 0x01F4A000 32808K
QuotaPeakPagedPool : 0x00071BE8 465K
QuotaPagedPool : 0x00070C88 461K
QuotaPeakNonPagedPool : 0x00008028 32K
QuotaNonPagedPool : 0x00007858 30K
Pagefile : 0x01055000 17125K
PeakPagefile : 0x011FD000 18862K
10 November 2011 - 16:58:38 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:58:39 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:58:39 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:58:40 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:58:41 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:58:42 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:58:44 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:58:45 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:59:09 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:59:10 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
10 November 2011 - 16:59:39 Connect ---- Try to connect to: Host: localhost, Windows-7-PC, Port: 31416, Thread ID: 6960
10 November 2011 - 16:59:40 Connect, init ---- Host: localhost, Windows-7-PC,Port: 31416, connection error
Anthony.
Quote from: Mellowman on November 10, 2011, 03:09:52 PM
The 8600GT still can crunch a mini-collatz in ~2hours. All my Collatz credits from last month are from that card.
Just to give you a reference, even the HD4770 will do a full size Collatz WU in ~1 hour, so is about 16x faster than the 8600. You should be able to get one for under $50 used. The HD5770 will do about 43 minutes/large WU for a 23x improvement.. You would also get rid of your Collatz problems: "I run mini-collatz on my GF8600GT in a dual GPU setup and I get a lot of computation errors."
QuoteYou would also get rid of your Collatz problems: "I run mini-collatz on my GF8600GT in a dual GPU setup and I get a lot of computation errors."
I don't have a lot of computation erorrs. Where did I say that? You can check it here (http://boinc.thesonntags.com/collatz/results.php?hostid=77755).
And I only run Collatz because that's the only project I know that will run on my 8600GT 256MB, and I want to use that card too. Otherwise I wouldn't even have signed up for the project.
Anthony.
Quote from: Mellowman on November 10, 2011, 04:14:55 PM
QuoteYou would also get rid of your Collatz problems: "I run mini-collatz on my GF8600GT in a dual GPU setup and I get a lot of computation errors."
I don't have a lot of computation erorrs. Where did I say that? You can check it here (http://boinc.thesonntags.com/collatz/results.php?hostid=77755).
Here's your thread on Collatz:
lot of videodriver crashes and WU-errors on GF8600GThttp://boinc.thesonntags.com/collatz/forum_thread.php?id=796
Your first post on the subject:
"Hi, I run mini-collatz on my GF8600GT in a dual GPU setup and I get a lot of computation errors. I got those even without my GTX-550OC added to the system. I can't even suspend a collatz task as it will result in a displaydriver crash and a computation error. I also use my GF8600GT as my main display output to my TV. Display on the GTX550OC is totally disabled as I want that card fully dedicated for crunching other non collatz tasks as collatz is the only project that seems to run on my GF8600GT 256MB card. I use the latest nvidia driver 280.26."
How soon we forget... :)
Did you read the next post too. It happened to be a driver problem, so I wasn't the only one with a lot of computation errors. Since I updated the driver I've hadn't had any problem except for the driver crashes when I suspend Collatz or exit the Collatz boinc client, but no computation errors. But I wrote to Nvidia about the driver crash problem. It isn't that big of a problem as I only suspend Collatz when I want to watch (recorded) TV. And lately I havent watched much (but still kept recording so I should watch because I'm running out of space on my 1.5 TB total drive space on this system).
So after 2.5-3 week I totally forgot about that post. Can you blame me, I might have other things on my mind, then to remember something that's been solved for 3 weeks and has been on my mind that oktober 23rd for maybe less than an hour.
I f*cked up my brain already with 23.5 years of smoking marihuana (I quit smoking it since the 2nd half of July this year after having not smoked it the first half year of this year when I was in a psychiatric hospital/clinic because I have a deathwish.
I still take tranqelizers to calm me down and those aren't that good for your memory either. So I'm sorry I forgot something that wasn't an issue anymore.
Anthony.
Sorry Anthony, was just trying to offer a helpful alternative. Think I forgot something once too, but can't remember what it was at the moment ;)
But the alternative doesn't work for me. It would mean I have to throw a perfectly good card (old but still good enough for some stuff) in the bin as I can't sell it as it isn't worth anything. And if I buy an ATI card which project that I run can I use it for. I need an ATI double precision card then, so I could use it for MilkyWay. What will those cost me? And are those 2 projects the only projects where I can use ATI cards (from the projects I run)?
Going to bed now as it's 4:42 AM overhere.
Anthony.
Quote from: Pepo on November 09, 2011, 09:41:36 PM
My ...\history\backup folder (on one machine with a very small number of tasks being processed) contains 10.4 MB in 250 files, spanning 25.10.-9.11. - possibly because of History's "keep 12 days + 0 hours" preference? The startup times are short now (2-3 seconds, full CPU use).
On another machine (with a bit more tasks) there were 800 files using up 400 MB, spanning 25.10.-11.11. Short-term history is set to keep 5d+23h.
Actually neither of the files (on both machines), nor the
backup folders were set to read-only.
Quote from: Pepo on November 11, 2011, 02:00:44 PM
Quote from: Pepo on November 09, 2011, 09:41:36 PM
My ...\history\backup folder (on one machine with a very small number of tasks being processed) contains 10.4 MB in 250 files, spanning 25.10.-9.11. - possibly because of History's "keep 12 days + 0 hours" preference? The startup times are short now (2-3 seconds, full CPU use).
On another machine (with a bit more tasks) there were 800 files using up 400 MB, spanning 25.10.-11.11. Short-term history is set to keep 5d+23h.
Actually neither of the files (on both machines), nor the backup folders were set to read-only.
Wait for 1.27, I made a lot of changes, that should fix all these problems, including a read only problem. The last one shouldn't be there in the first place.
Quote from: fred on November 11, 2011, 03:29:13 PM
Wait for 1.27, I made a lot of changes, that should fix all these problems, including a read only problem.
Will it be able to install over the "temporary" 1.27? Or better some 1.27.1?
Quote from: Pepo on November 11, 2011, 04:34:55 PM
Will it be able to install over the "temporary" 1.27? Or better some 1.27.1?
It should install over the test version as the file itself is 1.271.
Quote from: fred on November 11, 2011, 06:18:09 PM
Quote from: Pepo on November 11, 2011, 04:34:55 PM
Will it be able to install over the "temporary" 1.27? Or better some 1.27.1?
It should install over the test version as the file itself is 1.271.
:) That's exactly what I've meant.