Posts by Dougga

1) Message boards : Questions and problems : New Windows install no reading app_config.xml (Message 92792)
Posted 13 Sep 2019 by Dougga
Post:
I've placed the following text i app_config.xml in C:\ProgramData\BOINC\projects\boinc.thesonntags.com_collatz

<app_config>
<app>
<name>collatz_sieve</name>
<max_concurrent>10</max_concurrent>
<gpu_versions>
<gpu_usage>0.25</gpu_usage>
<cpu_usage>0.25</cpu_usage>
</gpu_versions>
</app>
</app_config>

When I load the boinc client, there's no log entry referencing this file as I think there should be.
Can anyone help me figure out what I'm missing?
Thanks,
Doug
2) Message boards : Projects : News on Project Outages (Message 91494)
Posted 14 May 2019 by Dougga
Post:
Collatz Conjecture: update from the administrator

"I'm having trouble with the DDNS and had to switch back to the static DNS so it may take a few hours to trickle through. Exit and restart BOINC may also help as it has a tendancy to cache the DNS entries. "
3) Message boards : Projects : Collatz Conjecture Down? (Message 91493)
Posted 14 May 2019 by Dougga
Post:
I heard from the admin of the Collatz Conjecture project.

"I'm having trouble with the DDNS and had to switch back to the static DNS so it may take a few hours to trickle through. Exit and restart BOINC may also help as it has a tendancy to cache the DNS entries. "


So there's the answer.
4) Message boards : Projects : Collatz Conjecture Down? (Message 91491)
Posted 14 May 2019 by Dougga
Post:
I'm still getting timeouts when I attempt to click on your link. My proxy server is showing "No route to host". From my cell phone (Verizon) I get a generic error.

This is a great example of the problem of having a troubleshooting forum on the same infrastructure as the service: there's no way to communicate troubleshooting network infrastructure issues.
5) Message boards : Projects : News on Project Outages (Message 91490)
Posted 14 May 2019 by Dougga
Post:
Quite possible that ping is restricted and the root problem is simply a certificate expiring or something annoying like that.
6) Message boards : Projects : News on Project Outages (Message 91488)
Posted 14 May 2019 by Dougga
Post:
Collatz Conjecture Outage: further information

URL: boinc.thesonntags.com/collatz
The URL resolves to 67.167.89.131
This in turn resolves back to "c-67-167-89-131.hsd1.il.comcast.net".

A traceroute suggests the server is down or unreachable:
traceroute to 67.167.89.131 (67.167.89.131), 30 hops max, 40 byte packets using UDP

1 192.168.0.1 (192.168.0.1) 0.769 ms 0.552 ms 0.464 ms
2 * * * LOCAL DETAILS HIDDEN
3 * * * LOCAL DETAILS HIDDEN
4 * * * LOCAL DETAILS HIDDEN
5 * * * LOCAL DETAILS HIDDEN
6 68.86.86.225 (68.86.86.225) 3.131 ms 5.244 ms 4.176 ms
7 68.86.84.206 (68.86.84.206) 32.530 ms 31.859 ms *
8 * * *
9 68.86.85.169 (68.86.85.169) 51.131 ms * *
10 * * *
11 * * *
12 * * *
13 68.87.204.74 (68.87.204.74)(H!) 52.094 ms * *

Note: "H!" = host, network or protocol unreachable
Did someone forget to pay Comcast?
7) Message boards : Projects : News on Project Outages (Message 91487)
Posted 14 May 2019 by Dougga
Post:
Collatz Conjecture - Down
Even their website throws errors for me. No communications at all.
Work Units piling up.
8) Message boards : Projects : Collatz Conjecture Down? (Message 91486)
Posted 14 May 2019 by Dougga
Post:
IT appears that all communications with the Collatz Conjecture project are down.
I have hundreds of completed tasks yet I can't find any reference to reasoning.
Can anyone help?
9) Message boards : Teams : Team Conversations? (Message 89633)
Posted 15 Jan 2019 by Dougga
Post:
I've been looking around for a way to communicate with my teams.
Is this (basic) feature not included in the Boinc universe?

Thanks,

Doug
10) Message boards : Questions and problems : LightDM on Ubuntu 17.04 causing corruption of Einstein work units (Message 78036)
Posted 20 May 2017 by Dougga
Post:
I've been having some trouble optimizing boinc on my computer.
After much digging I've discovered that the GUI on Ubuntu Linux causes (or at least is correlated with) the corruption of work units.

Here's a link to the threat over at Einstein where we figured this out: https://einsteinathome.org/content/help-configuring-multi-core-multi-gpu#comment-158059

Machine:
Intel CPU with 4 cores
Nvidia GPX 690 (which is two GPX 680's on one card) with 2 GPUs.

Windows 7: with an appropriately configured app_config.xml 4 GPU work units will crunch along, using one of each of the CPUs to support each GPU work unit.
This is possible because the card has 4GB of ram which is adequate to support 2 work units per GPU.

Ubuntu Linux 17.04: With the same app_config.xml, work units are corrupted within 10-15 seconds so lots of work units are churned through and more are downloaded. Quite a mess.

However, if I drop the GUI "sudo systemctl stop lightdm", 4 GPU work units will function just fine without error.

This looks like a bug to me, but it's not clear if this is a Boinc bug or an Einstein bug.
My guess is it's boinc.

Thoughts?

Thanks in advance.
11) Message boards : Questions and problems : html problems with boinc (Windows) and Sophos UTM blocking projects (Message 76269)
Posted 6 Mar 2017 by Dougga
Post:
I have been seeing (for years) problems with specific projects communicating with their home servers via the boinc client.
I'm just now reaching out as I'm a little puzzled this hasn't been identified and fixed by others.

Details:
Boinc Manager: 7.6.33 (x64)
Windows 7 Ultimate (x64)
16 GB RAM - Intel Core i5-2400 - nVidia GPX 690
Perimeter firewall: Sophos UTM w/ http(s) proxy
(turning proxy off does not improve the situation)

While SETI continues to work flawlessly, I see the following issues:

Einstein
Any attempts to communicate with the project receives the fowwoing error:
"Project communication failed: attempting acces to reference site.
"BOINC can't access Internet - check network connection or proxy configuration"
Peering at my firewall logs managing http(s) traffic I see the fowwling:
2017:03:06-14:45:01 ravenna httpproxy[5861]: id="0003" severity="info" sys="SecureWeb" sub="http" request="(nil)" function="read_request_headers" file="request.c" line="1581" message="Read error on the http handler 97 (Input/output error)"
20


Climate Prediction
I'm getting errors associated with stalled downloads.

Has anyone else seen errors like these?
12) Message boards : BOINC client : Bug Report: improper disk quota handling (Message 16065)
Posted 24 Mar 2008 by Dougga
Post:
I'm running the boinc 5.10.45 and am seeing errors in the management of the disk quota.

Boinc manager is reporting:
145.03 MB used by boinc
139.18 MB used by the Rosetta project

in the messages the client reports that disk usage is limited to 16GB of disk space.

Then the client states that there is insufficient disk space and that 0 tasks were downloaded.

On occasion I can to get it to work by rebooting, restarting, and otherwise assaulting the application at which point it downloads the maximum number of work units allowed by Rosetta preventing further computation from any of my other clients.

Is this a known issue?
Can I turn off this buggy quota system?

Thanks



Oh yes... this is running on:

OpenSuse 10.3
Intel Quad Core Proc
4GB Ram
13) Message boards : BOINC client : Bug Report: improper disk quota handling (Message 16064)
Posted 24 Mar 2008 by Dougga
Post:
I'm running the boinc 5.10.45 and am seeing errors in the management of the disk quota.

Boinc manager is reporting:
145.03 MB used by boinc
139.18 MB used by the Rosetta project

in the messages the client reports that disk usage is limited to 16GB of disk space.

Then the client states that there is insufficient disk space and that 0 tasks were downloaded.

On occasion I can to get it to work by rebooting, restarting, and otherwise assaulting the application at which point it downloads the maximum number of work units allowed by Rosetta preventing further computation from any of my other clients.

Is this a known issue?
Can I turn off this buggy quota system?

Thanks




Copyright © 2020 University of California. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.