Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
Questions / Re: Cannot connect o local network clients
« Last post by zOU on October 04, 2017, 05:51:45 pm »
fixed it.

I had to delete all the MAC address from the "computer" tab and they re-appeared
22
Questions / Re: Cannot connect o local network clients
« Last post by zOU on October 04, 2017, 05:45:22 pm »
hello

I have the same issue after upgrading from 1.6* to 1.73:

Quote
04 October 2017 - 19:40:13 Logging ---- Start debug mode
04 October 2017 - 19:40:13
04 October 2017 - 19:40:13 BoincTasks version: 1.73
04 October 2017 - 19:40:14 Language ---- User: 1033 (ENU), System: 2057 (ENG), Selected: 0 () Used: 1033 (ENU)
04 October 2017 - 19:40:14 Get localhost IP ---- Found IP: 192.168.1.101
04 October 2017 - 19:40:14 Get localhost IP ---- Found IP: 169.254.80.183
04 October 2017 - 19:40:14 Maximum number of computers: Unlimited
04 October 2017 - 19:40:14 Computers ---- Acer , IP: 192.168.1.30
04 October 2017 - 19:40:14 Computers ---- Aphrodite , MAC: 00-1E-67-0A-38-F4
04 October 2017 - 19:40:14 Computers ---- Brix , MAC: 94-DE-80-8E-83-C8
04 October 2017 - 19:40:14 Computers ---- Fujitsu-wifi , MAC: 00-27-19-BA-13-3B
04 October 2017 - 19:40:14 Computers ---- localhost get local password: (C:\ProgramData\BOINC\\gui_rpc_auth.cfg) b992818e89126faf19fb37ce9e8c1449
04 October 2017 - 19:40:14 Computers ---- Hades , IP: localhost
04 October 2017 - 19:40:14 Computers ---- LDLC , MAC: 00-11-09-2D-CA-36
04 October 2017 - 19:40:14 Computers ---- MSI3500 , MAC: 00-13-D3-35-9D-51
04 October 2017 - 19:40:14 Computers ---- RPI , MAC: B8-27-EB-53-DF-96
04 October 2017 - 19:40:14 Computers ---- lattepanda , IP: 192.168.1.36
04 October 2017 - 19:40:14 Computers ---- lenovo_fixe , MAC: 4C-CC-6A-CC-08-94
04 October 2017 - 19:40:14 Computers ---- xeon , MAC: 00-15-17-8E-49-1D
04 October 2017 - 19:40:15 Connect ---- Connected to: Host: Hades, IP: localhost, Port: 31416, BOINC Version: 7.6.22
04 October 2017 - 19:40:18 Connect ---- Connected to: Host: localhost, Hades,Port: 31417, TThrottle Version: 7.52
04 October 2017 - 19:40:22 Start BOINC client ---- The BOINC client was already running
04 October 2017 - 19:40:26 Connect, no IP found for MAC address ---- Host: Fujitsu-wifi, IP: 192.168.1.141, Port: 31416, socket not ready
04 October 2017 - 19:40:26 Connect, no IP found for MAC address ---- Host: Brix, IP: 192.168.1.24, Port: 31416, socket not ready
04 October 2017 - 19:40:26 Connect, no IP found for MAC address ---- Host: Aphrodite, IP: 192.168.1.211, Port: 31416, socket not ready
04 October 2017 - 19:40:26 Connect, no IP found for MAC address ---- Host: LDLC, IP: 192.168.1.109, Port: 31416, socket not ready
04 October 2017 - 19:40:26 Connect, no IP found for MAC address ---- Host: RPI, IP: 192.168.1.25, Port: 31416, socket not ready
04 October 2017 - 19:40:26 Connect, no IP found for MAC address ---- Host: MSI3500, IP: 192.168.1.89, Port: 31416, socket not ready
04 October 2017 - 19:40:26 Connect, no IP found for MAC address ---- Host: xeon, IP: 192.168.1.16, Port: 31416, socket not ready
04 October 2017 - 19:40:26 Connect, no IP found for MAC address ---- Host: lenovo_fixe, IP: 192.168.1.117, Port: 31416, socket not ready
04 October 2017 - 19:40:35 Connect, init ---- Host: lattepanda, IP: 192.168.1.36, Port: 31416, init, timeout error
04 October 2017 - 19:40:35 Connect, init ---- Host: Acer, IP: 192.168.1.30, Port: 31416, init, timeout error
23
Questions / Some finished tasks do not show in history
« Last post by Harri Liljeroos on October 03, 2017, 02:23:16 pm »
Hi
Some of my finished tasks do not register to the history tab. LHC@home sixtrack applications are currently having quite a lot of tasks that are finished in 6...9 seconds. Task do not have errors, they finish succesfully. Today I noticed that that I had 29 such tasks finished in succession (visible in project website) but only 7 of them are visible in History. I tried to shorten the min and max update times to min=1 and max=6 seconds but that did not help.
Boinctasks version is 1.73, Boinc is 7.6.33 on windows 7 64 bit. So is this a bug or what gives?
24
Questions / Re: What happens if est app speed is set to zero?
« Last post by fred on September 29, 2017, 04:07:27 pm »
Charity Engine   1.39 ce11 (idle)   wu_1503000423_5512922_4   08:09:26 (00:00:17)   0.0   96.493   00:17:47   9/28/2017 6:40:56 PM   0.0001 CPUs   Running   0   40.7 C   DESKTOP-3D27Q41   17.96 MB   12.93 MB   
The task shows (idle), it should report back the app speed to the BOINC client. It also shows 0.0001 CPUs, so it suggests a memory task instead of a computation task.
Best place to ask is the project website.
25
Questions / What happens if est app speed is set to zero?
« Last post by idahofisherman on September 29, 2017, 03:42:49 am »
Charity Engine   1.39 ce11 (idle)   wu_1503000423_5512922_4   08:09:26 (00:00:17)   0.0   96.493   00:17:47   9/28/2017 6:40:56 PM   0.0001 CPUs   Running   0   40.7 C   DESKTOP-3D27Q41   17.96 MB   12.93 MB   

Properties
   
Computer:   DESKTOP-3D27Q41
Project   Charity Engine
   
Name   wu_1503000423_5512922_4
   
Application   ce11 1.39 (idle)
Workunit name   wu_1503000423_5512922
State   Running
Received   9/28/2017 1:40:59 PM
Report deadline   9/28/2017 6:40:56 PM
Estimated app speed   0.00 GFLOPs/sec
Estimated task size   2 GFLOPs
Resources   0.0001 CPUs
CPU time at last checkpoint   00:00:12
CPU time   00:00:17
Elapsed time   07:52:26
Estimated time remaining   00:17:14
Fraction done   96.480%
Virtual memory size   18.05 MB
Working set size   12.44 MB
Directory   slots/0
Process ID   1456
   
26
Questions / Re: Using BOINCTasks to edit config file adds invalid tags to cc_config.xml
« Last post by fred on September 26, 2017, 06:56:40 am »
Fred, the machines that were giving these errors are all Linux machines where I only have console access. They are all running the latest BOINC version for Linux (7.2.42) but that is rather old.
OK just checked, my Ubuntu machine is using 7.6.33 that is newer than https://boinc.berkeley.edu/download_all.php That shows a very very old version.
On my Linux machine everything works as intended.

So in order for this to work you might want to switch to BoincTasks 1.69 https://efmer.com/download-boinctasks/ that should match the older BOINC version.

Please read this: https://boinc.berkeley.edu/dev/forum_thread.php?id=10803  to get a more up to date Linux version.
27
Questions / Re: Using BOINCTasks to edit config file adds invalid tags to cc_config.xml
« Last post by fred on September 25, 2017, 03:05:26 pm »
Fred, the machines that were giving these errors are all Linux machines where I only have console access.
Yes, the Linux versions are much older than the Windows releases.
BoincTasks reads back all the possible tags and writes them bag.
Let's see if I can catch the invalid tags and don't write them back. I have a Linux machine here, so will try that.
28
Beta Testing / Re: B.T. 1.73
« Last post by fred on September 25, 2017, 03:01:56 pm »
I went back to 1.69. This version has regressed. I finished work on one of my extra clients on a remote computer for the Formula BOINC team competition so I told the client, through BT, No New Work. It still got new work. I abort it. It got another. I suspend the whole project and BT still got another. Projects sidebar had it as NNW and Suspended but there was a WUProp task running anyway. There is no other BM controlling that client besides BT. Back on 1.69 suspending the project properly suspended the task.
Weird that you are reporting these issues, as there is absolutely no change 1.69 <-> 1.73 in all the things you mentioned.
Would be nice if you checked the BOINC log, that would show what is going on.
A project no more work should show up in the log: work fetch suspended by user   
29
Fred, the machines that were giving these errors are all Linux machines where I only have console access. They are all running the latest BOINC version for Linux (7.2.42) but that is rather old. I shut down BOINC on one, edited the cc_config.xml file to remove these tags and any others with a 0 value. After restarting BOINC, I went in to edit the cc_config.xml file thru BOINCTasks and the screen was populated with all of the options including these that get flagged as errors. Quit out of that and checked this on one of my Windows machines (Win 10 running BOINC 7.8.2). Here's the contents of the cc_config.xml file (in /ProgramData/BOINC):

<cc_config>
    <log_flags>
    </log_flags>
    <options>
        <allow_remote_gui_rpc>1</allow_remote_gui_rpc>
        <report_results_immediately>1</report_results_immediately>
    </options>
</cc_config>

If I go edit the file via BOINCTasks, a whole bunch of tags are listed including these that BOINC is flagging as errors. As you say, the config file keeps on changing all the time. So, I looked for a way to edit the file via BOINCManager but under Options, it has an interface for just the <log_flags>. The tags flagged as invalid are all under <options>. Looking at the BOINC Wiki, some of the invalid tags are for levels after 7.2.42 but not all of them. I presume that you are getting the list of tags for the config file from BOINC somehow, otherwise, you'd be having to update BOINCTasks every time they changed/added a tag. Given that that is the case, why would a machine running 7.2.42 give you tags that were added after that version?
30
Beta Testing / Re: B.T. 1.73
« Last post by mmonnin on September 17, 2017, 11:55:07 pm »
I went back to 1.69. This version has regressed. I finished work on one of my extra clients on a remote computer for the Formula BOINC team competition so I told the client, through BT, No New Work. It still got new work. I abort it. It got another. I suspend the whole project and BT still got another. Projects sidebar had it as NNW and Suspended but there was a WUProp task running anyway. There is no other BM controlling that client besides BT. Back on 1.69 suspending the project properly suspended the task.
Pages: 1 2 [3] 4 5 ... 10