Bug#789095: [boinc-client] Unable to send back computed tasks
Dimitri Chausson
tri2000 at gmx.net
Wed Jun 17 19:56:40 UTC 2015
Package: boinc-client
Version: 7.4.23+dfsg-2
Severity: important
--- Please enter the report below this line. ---
Hello,
the client has not been able to send finished tasks back to the server for several days, although internet access is ok. I have also looked for temporary unavailability news on the project's website, but found nothing. It seems to me that the update of the ca-certificates package brought the system into trouble.
Below an extract of the logs boincmgr:
=============================================================================
dim. 14 juin 2015 19:27:03 CEST | World Community Grid | Sending scheduler request: Requested by project.
dim. 14 juin 2015 19:27:03 CEST | World Community Grid | Not requesting tasks: too many uploads in progress
dim. 14 juin 2015 19:27:03 CEST | | [network_status] status: online
dim. 14 juin 2015 19:27:04 CEST | | [network_status] got HTTP error - checking ref site
dim. 14 juin 2015 19:27:04 CEST | | [network_status] need_phys_conn 0; trying http://www.google.com/
dim. 14 juin 2015 19:27:04 CEST | | Project communication failed: attempting access to reference site
dim. 14 juin 2015 19:27:04 CEST | World Community Grid | Scheduler request failed: Peer certificate cannot be authenticated with given CA certificates
dim. 14 juin 2015 19:27:04 CEST | | [network_status] status: reference site lookup pending
dim. 14 juin 2015 19:27:05 CEST | | [network_status] status: reference site lookup pending
dim. 14 juin 2015 19:27:06 CEST | | [network_status] status: reference site lookup pending
dim. 14 juin 2015 19:27:07 CEST | | Re-reading cc_config.xml
dim. 14 juin 2015 19:27:07 CEST | | Not using a proxy
dim. 14 juin 2015 19:27:07 CEST | | Config: GUI RPCs allowed from:
dim. 14 juin 2015 19:27:07 CEST | | log flags: file_xfer, sched_ops, task
dim. 14 juin 2015 19:27:07 CEST | | Internet access OK - project servers may be temporarily down.
dim. 14 juin 2015 19:27:18 CEST | World Community Grid | Started upload of MCM1_0014435_6636_0_0
dim. 14 juin 2015 19:27:18 CEST | World Community Grid | Started upload of MCM1_0014436_8146_0_0
dim. 14 juin 2015 19:27:19 CEST | World Community Grid | Sending scheduler request: Requested by project.
dim. 14 juin 2015 19:27:19 CEST | World Community Grid | Not requesting tasks: too many uploads in progress
dim. 14 juin 2015 19:27:20 CEST | | Project communication failed: attempting access to reference site
dim. 14 juin 2015 19:27:20 CEST | World Community Grid | Temporarily failed upload of MCM1_0014435_6636_0_0: transient HTTP error
dim. 14 juin 2015 19:27:20 CEST | World Community Grid | Backing off 05:56:18 on upload of MCM1_0014435_6636_0_0
dim. 14 juin 2015 19:27:20 CEST | World Community Grid | Temporarily failed upload of MCM1_0014436_8146_0_0: transient HTTP error
dim. 14 juin 2015 19:27:20 CEST | World Community Grid | Backing off 04:01:16 on upload of MCM1_0014436_8146_0_0
dim. 14 juin 2015 19:27:20 CEST | World Community Grid | Scheduler request failed: Peer certificate cannot be authenticated with given CA certificates
dim. 14 juin 2015 19:27:21 CEST | | Internet access OK - project servers may be temporarily down.
dim. 14 juin 2015 20:42:12 CEST | World Community Grid | Sending scheduler request: Requested by project.
dim. 14 juin 2015 20:42:12 CEST | World Community Grid | Not requesting tasks: too many uploads in progress
dim. 14 juin 2015 20:42:14 CEST | | Project communication failed: attempting access to reference site
dim. 14 juin 2015 20:42:14 CEST | World Community Grid | Scheduler request failed: Peer certificate cannot be authenticated with given CA certificates
=============================================================================
Thanks for any help,
Dimitri
--- System information. ---
Architecture: amd64
Kernel: Linux 3.16.0-4-amd64
Debian Release: stretch/sid
990 testing security.debian.org
990 testing merlin.fit.vutbr.cz
500 unstable merlin.fit.vutbr.cz
500 stable repos.codelite.org
500 binary pkg.jenkins-ci.org
--- Package information. ---
Depends (Version) | Installed
=====================================-+-==================
libboinc7 (>= 7.4.8+dfsg-3) | 7.4.23+dfsg-2
libc6 (>= 2.15) |
libcurl3 (>= 7.16.2) |
libgcc1 (>= 1:4.1.1) |
libssl1.0.0 (>= 1.0.0) |
libstdc++6 (>= 4.9) |
libx11-6 |
libxext6 |
libxss1 |
zlib1g (>= 1:1.1.4) |
debconf (>= 0.5) |
OR debconf-2.0 |
python:any |
adduser |
ca-certificates |
Package's Recommends field is empty.
Suggests (Version) | Installed
================================-+-===========
boinc-manager | 7.4.23+dfsg-2
boinc-amd-opencl |
boinc-nvidia-cuda |
x11-xserver-utils | 7.7+4
--- Output from package bug script ---
-- Contents of /etc/default/boinc-client:
# This file is /etc/default/boinc-client, it is a configuration file for the
# /etc/init.d/boinc-client init script.
# Set this to 1 to enable and to 0 to disable the init script.
ENABLED="1"
# Set this to 1 to enable advanced scheduling of the BOINC core client and
# all its sub-processes (reduces the impact of BOINC on the system's
# performance).
SCHEDULE="1"
# The BOINC core client will be started with the permissions of this user.
BOINC_USER="boinc"
# This is the data directory of the BOINC core client.
BOINC_DIR="/mnt/grid/boinc-client"
# This is the location of the BOINC core client, that the init script uses.
# If you do not want to use the client program provided by the boinc-client
# package, you can specify here an alternative client program.
#BOINC_CLIENT="/usr/local/bin/boinc"
BOINC_CLIENT="/usr/bin/boinc"
# Here you can specify additional options to pass to the BOINC core client.
# Type 'boinc --help' or 'man boinc' for a full summary of allowed options.
#BOINC_OPTS="--allow_remote_gui_rpc"
BOINC_OPTS=""
# Scheduling options
# Set SCHEDULE="0" if prefering to run with upstream default priority
# settings.
# Nice levels. When systems are truly busy, e.g. because of too many active
# scientific applications started by the boinc client, there is a chance for
# the boinc client not to be granted sufficient opportunity to check for
# scientific applications to be alive and make the (wrong) decision to
# terminate the scientific app. This is particularly an issue with many
# apps started in parallel on modern multi-core systems and extra overheads
# for the download and uploads of files with the project servers. Another
# concern is the latency for scientific applications to communicate with the
# graphics card, which should be low. All such values should be set and
# controled from within the BOINC client. The Debian init script also sets
# extra constrains via chrt on real time performance and via ionice on
# I/O performance, which is beyond the regular BOINC client. It then was
# too easy to use that code to also constrain minimal nice levels. We still
# think about how to best distinguish GPU applications from regular apps.
BOINC_NICE_CLIENT=10
BOINC_NICE_APP_DEFAULT=19
#BOINC_NICE_APP_GPU=5 # not yet used
# ionice classes. See manpage of ionice (1) in the util-linux package.
BOINC_IONICE_CLIENT=3 # idle
#BOINC_IONICE_APP_DEFAULT=3 # idle, not yet used
#BOINC_IONICE_APP_GPU=2 # best effort, not yet used
More information about the pkg-boinc-devel
mailing list