Posts by computezrmle

41) Message boards : Questions and problems : Issues with BOINC 7.20.2 x64 behind a proxy (Message 109503)
Posted 5 Aug 2022 by computezrmle
Post:
Just compiled the recent sources from github on Linux and tried to connect to Rosetta via a Squid proxy.
This works without any further change.
https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=6175439
42) Message boards : Questions and problems : ': No such file or directory' (cryptic/useless error message) (Message 109367)
Posted 19 Jul 2022 by computezrmle
Post:
Looks like you called "boinccmd ..." without a path.
Either
- include the directory where "boinccmd" is located in the path
- call "boinccmd" with a preceding path, e.g. "./boinccmd" or "/absolute/path/to/the/executable/boinccmd".
43) Message boards : Questions and problems : Using BOINC with a different disk on Fedora36 then /, or /home/[$user] (Message 108936)
Posted 5 Jul 2022 by computezrmle
Post:
What is it you are not happy with?
A. the paths "/var/lib/boinc" and "/home/[$user]"
B. the device (disk) the data is stored on


In case of "/home/[$user]"

Modify the systemd boinc service unit.
There's a line looking like "ExecStart=.../boinc ..."
Enter the data dir there, e.g. "ExecStart=.../boinc --dir /path/where/you/want/boinc/data/to/be/boinc_data ...."
Ensure this path has the correct access rights




In case of "/var/lib/boinc" and (B.)
1. prepare a large "boinc" disk with btrfs (you wrote you are using btrfs)
2. create 2 subvolumes on that disk: "boinc_program" and "boinc_data"
3. Rename "/var/lib/boinc" to "/var/lib/boinc1"
4. create an empty "/var/lib/boinc" as mountpoint and mount "boinc_program" there
5. copy all data from "/var/lib/boinc1" to "/var/lib/boinc" (preserve attributes)
6. create an empty "/path/where/you/want/boinc/data/to/be/boinc_data" as mountpoint and mount "boinc_data" there
7. restart BOINC

Make the new mountpoints persistent in /etc/fstab.
44) Message boards : Projects : Project DENIS has restarted (Message 108853)
Posted 3 Jul 2022 by computezrmle
Post:
They will need a new server certificate:
SSL Certificate expired on: Jul 1 23:59:59 2022 GMT
45) Message boards : Projects : News on Project Outages (Message 108589)
Posted 20 Jun 2022 by computezrmle
Post:
This affects only CMS.
Theory and ATLAS are available as usual.

https://lhcathome.cern.ch/lhcathome/server_status.php
46) Message boards : GPUs : Water cooling (Message 108404)
Posted 11 Jun 2022 by computezrmle
Post:
Can't find the source ATM but I once read that if you keep the temperature 10 degrees lower than the max temp allowed by the manufacturer this usually doubles the lifetime of a CPU/GPU.
In addition, avoid peaks (up as well as down).
47) Message boards : Questions and problems : Download, upload, and Notices don't work on wired LAN; work on wireless guest LAN (Message 108299)
Posted 1 Jun 2022 by computezrmle
Post:
Einstein works fine even with (transparent) TLS connections through a Squid proxy.
So do all BOINC projects my computers are attached to.

Since TLS is the same for all firewalls just do it right and add the CA cert to your firewall (or Squid) and to the ca-bundle.crt file where the BOINC client can find it. There's no need to change BOINC, neither the client side nor the server side.

See:
https://wiki.squid-cache.org/Features/SslPeekAndSplice


Mi 01 Jun 2022 20:37:54 CEST | Einstein@Home | [http] [ID#1] Info:  Establish HTTP proxy tunnel to scheduler.einsteinathome.org:443
Mi 01 Jun 2022 20:37:54 CEST | Einstein@Home | [http] [ID#1] Sent header to server: CONNECT scheduler.einsteinathome.org:443 HTTP/1.1
Mi 01 Jun 2022 20:37:54 CEST | Einstein@Home | [http] [ID#1] Sent header to server: Host: scheduler.einsteinathome.org:443
Mi 01 Jun 2022 20:37:54 CEST | Einstein@Home | [http] [ID#1] Sent header to server: User-Agent: BOINC client (x86_64-suse-linux-gnu 7.19.0)
Mi 01 Jun 2022 20:37:54 CEST | Einstein@Home | [http] [ID#1] Sent header to server: Proxy-Connection: Keep-Alive

Mi 01 Jun 2022 20:37:54 CEST |  | [http] [ID#0] Received header from server: HTTP/1.1 200 Connection established
Mi 01 Jun 2022 20:37:54 CEST |  | [http] [ID#0] Received header from server:
Mi 01 Jun 2022 20:37:54 CEST |  | [http] [ID#0] Info:  Proxy replied 200 to CONNECT request
Mi 01 Jun 2022 20:37:54 CEST |  | [http] [ID#0] Info:  CONNECT phase completed
Mi 01 Jun 2022 20:37:54 CEST |  | [http] [ID#0] Info:  ALPN: offers h2
Mi 01 Jun 2022 20:37:54 CEST |  | [http] [ID#0] Info:  ALPN: offers http/1.1
Mi 01 Jun 2022 20:37:54 CEST |  | [http] [ID#0] Info:   CAfile: ca-bundle.crt
Mi 01 Jun 2022 20:37:54 CEST |  | [http] [ID#0] Info:   CApath: none
Mi 01 Jun 2022 20:37:54 CEST |  | [http] [ID#0] Info:  TLSv1.3 (OUT), TLS handshake, Client hello (1):
Mi 01 Jun 2022 20:37:54 CEST | Einstein@Home | [http] [ID#1] Received header from server: HTTP/1.1 200 Connection established
Mi 01 Jun 2022 20:37:54 CEST | Einstein@Home | [http] [ID#1] Received header from server:
Mi 01 Jun 2022 20:37:54 CEST | Einstein@Home | [http] [ID#1] Info:  Proxy replied 200 to CONNECT request
Mi 01 Jun 2022 20:37:54 CEST | Einstein@Home | [http] [ID#1] Info:  CONNECT phase completed
Mi 01 Jun 2022 20:37:54 CEST | Einstein@Home | [http] [ID#1] Info:  ALPN: offers h2
.
.
.
Mi 01 Jun 2022 20:37:54 CEST | Einstein@Home | [http] [ID#1] Info:   CAfile: ca-bundle.crt
Mi 01 Jun 2022 20:37:54 CEST | Einstein@Home | [http] [ID#1] Info:   CApath: none
Mi 01 Jun 2022 20:37:54 CEST | Einstein@Home | [http] [ID#1] Info:  TLSv1.3 (OUT), TLS handshake, Client hello (1):
Mi 01 Jun 2022 20:37:55 CEST | Einstein@Home | [http] [ID#1] Info:  TLSv1.3 (IN), TLS handshake, Server hello (2):
Mi 01 Jun 2022 20:37:55 CEST | Einstein@Home | [http] [ID#1] Info:  TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
Mi 01 Jun 2022 20:37:55 CEST | Einstein@Home | [http] [ID#1] Info:  TLSv1.3 (IN), TLS handshake, Certificate (11):
Mi 01 Jun 2022 20:37:55 CEST | Einstein@Home | [http] [ID#1] Info:  TLSv1.3 (IN), TLS handshake, CERT verify (15):
Mi 01 Jun 2022 20:37:55 CEST | Einstein@Home | [http] [ID#1] Info:  TLSv1.3 (IN), TLS handshake, Finished (20):
Mi 01 Jun 2022 20:37:55 CEST | Einstein@Home | [http] [ID#1] Info:  TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
Mi 01 Jun 2022 20:37:55 CEST | Einstein@Home | [http] [ID#1] Info:  TLSv1.3 (OUT), TLS handshake, Finished (20):
Mi 01 Jun 2022 20:37:55 CEST | Einstein@Home | [http] [ID#1] Info:  SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
Mi 01 Jun 2022 20:37:55 CEST | Einstein@Home | [http] [ID#1] Info:  ALPN: server did not agree on a protocol. Uses default.
Mi 01 Jun 2022 20:37:55 CEST | Einstein@Home | [http] [ID#1] Info:  Server certificate:
.
.
.
Mi 01 Jun 2022 20:37:55 CEST | Einstein@Home | [http] [ID#1] Info:   subjectAltName: host "scheduler.einsteinathome.org" matched cert's "scheduler.einsteinathome.org"
.
.
.
Mi 01 Jun 2022 20:37:55 CEST | Einstein@Home | [http] [ID#1] Info:   SSL certificate verify ok.
48) Message boards : Projects : TN-Grid currently 0 tasks ready to send. (Message 108071)
Posted 13 May 2022 by computezrmle
Post:
They send out tasks but at a rate that is too low to satisfy all computers waiting for work.
See their project forum:
https://gene.disi.unitn.it/test/forum_index.php
49) Message boards : Questions and problems : Crontab jobs not starting on Auto-restart (BIOS power setting) (Message 107954)
Posted 25 Apr 2022 by computezrmle
Post:
The recommended solution would be to use a systemd service instead of crontab.
50) Message boards : Questions and problems : Stop file deletion on reporting of tasks that error out. (Message 107928)
Posted 22 Apr 2022 by computezrmle
Post:
A simple workaround (on Linux) might be a command like this:
tail -F /path/to/logfile/joblog.log >/path/to/logfilecopy/joblog.log

Run it in a separate monitoring console just before you start a task that you expect to fail.
It keeps a copy of a single well known logfile even if the main process (e.g. BOINC) quickly removes the original logfile after a crash.
51) Message boards : Questions and problems : boinccmd RPC: "Authorization failure: -155" (Message 107911)
Posted 21 Apr 2022 by computezrmle
Post:
Interesting that it works across the ocean.
This means the reply returns within the usual timeout.
:-)

Out of curiosity - would you mind posting the typical ping times between your laptop and the cruncher at home?
You should obfuscate the real IPs to avoid getting them swamped with unwanted packets.
52) Message boards : Questions and problems : Is there a way to get BOINC to give priority to Tasks with short "time to deadline"? (Message 107842)
Posted 12 Apr 2022 by computezrmle
Post:
I'm not even sure where to begin and what to do with this thread. Will think about it.

I would agree if you make a cut at the point where the thread obviously becomes OT.
You may keep the older posts and remove the rest.
53) Message boards : Questions and problems : Is there a way to get BOINC to give priority to Tasks with short "time to deadline"? (Message 107829)
Posted 12 Apr 2022 by computezrmle
Post:
Unbelievable!

This guy came here and asked for advice how to drive a nail into something.
He got the advice to use a hammer and to be careful not to hit his thumb.
After he hit his thumb he blames the hammer and those who gave him advice.
54) Message boards : Questions and problems : Is there a way to get BOINC to give priority to Tasks with short "time to deadline"? (Message 107809)
Posted 11 Apr 2022 by computezrmle
Post:
To control the BOINC client inside the VM you could use the BOINC Manager on your host or on any other computer that can reach the VM via network.


And - I don't like your last sentence.
55) Message boards : Questions and problems : Is there a way to get BOINC to give priority to Tasks with short "time to deadline"? (Message 107807)
Posted 11 Apr 2022 by computezrmle
Post:
It may be time to move that discussion to a separate task as it has nothing to do with the original title.

Regarding the issue:
BOINC manager needs a library that is not yet installed on your guest.
Assuming you installed Xubuntu you would need to find an Ubuntu/Xubuntu repository where you can get the libwx...3.0 packets from.
You should make yourself familiar with those standard procedures as issues like that happen regularly.
I's basically not an error but the maintainers of Xubuntu decided not to deliver everything in the installation repository to keep it lean.
56) Message boards : Questions and problems : boinccmd RPC: "Authorization failure: -155" (Message 107806)
Posted 11 Apr 2022 by computezrmle
Post:
STOP!

When I wrote my previous post I just described the principle assuming every connection to be made inside you own LAN segment and protected by the firewall on the internet router.

What you describe looks like a connection across your internet router and you may have opened a security hole on your router's firewall.
This is a much more complex scenario and can't be discussed here, especially since so far nobody knows what routing/firewall functions your router offers and how the have to be configured.
57) Message boards : Questions and problems : Is there a way to get BOINC to give priority to Tasks with short "time to deadline"? (Message 107800)
Posted 11 Apr 2022 by computezrmle
Post:
Kyle Foster wrote:
I use VB on projects that use it like LHC, Rosetta, Cosmology.

I'm not aware of anybody to get WSL and Vbox running stable side by side.
58) Message boards : Questions and problems : Is there a way to get BOINC to give priority to Tasks with short "time to deadline"? (Message 107797)
Posted 11 Apr 2022 by computezrmle
Post:
... Is it easy enough to set up to grab CPDN Linux tasks?

Follow the VirtualBox manual to create a new VM:
https://www.virtualbox.org/manual/ch01.html#gui-createvm

Then install a Linux distribution as guest.
Then install BOINC on that Linux guest and attach to a project.

Most native projects (like CPDN) should run without problems.
Vbox projects inside the VM may or may not run depending on the CPU, the parameters used during VM creation and the guest Linux.

Be aware that you need to manually pause/resume that VM when you shutdown/restart the computer.
The BOINC client on your host doesn't do this as it doesn't even know that it exists.
59) Message boards : Questions and problems : Raspberry Pi, BOINC Manager versions / Fresh install procedures on PiOS (Message 107786)
Posted 10 Apr 2022 by computezrmle
Post:
Got this message when I tried to post this comment the first time:
"Can't create post. Too many links."
Hence I had to untag the links (sorry).

Regarding (2.)
"systemctl" isn't BOINC specific.
Instead it's a basic command related to the system daemon "systemd".
See: "man systemctl"
https://en.wikipedia.org/wiki/Systemd



Regarding (3.)
BOINC Manager is part of the corresponding BOINC Client package.
More information can be found here:
https://boinc.berkeley.edu/
https://boinc.berkeley.edu/trac/wiki/WikiMeta
https://boinc.berkeley.edu/download.php
https://boinc.berkeley.edu/wiki/Release_Notes
https://boinc.berkeley.edu/download.php
https://boinc.berkeley.edu/download_all.php
60) Message boards : Questions and problems : boinccmd RPC: "Authorization failure: -155" (Message 107780)
Posted 9 Apr 2022 by computezrmle
Post:
I’m assuming ufw on Ubuntu, what I’m not sure of is whether there is any option to restrict the traffic to Boinc or whether, once opened, the port is available to traffic from any program.

When BOINC client starts it's RPC listener requests a network socket (like 203.0.113.27:31416) from the Linux kernel.
If this succeeds (i.e. the socket was not already in use) BOINC exclusively binds to that socket.

A network packet arriving at any interface does not include the sender/destination process name (at that protocol level), just the port number.
The packet then goes through the kernel's network stack and ends in the input buffer of the process that is connected to the destination socket.

UFW can be seen as a frontend to control the ruleset of the kernel's network stack.


So, from the perspective of the BOINC client on the linux machine:
it keeps the socket exclusively allocated until it's own end of live.

From the perspective of the network stack:
it delivers all packets allowed by the active ruleset to the destination socket but it doesn't know if they have been sent by a valid source process.
It's the BOINC client's task to check whether the network packets contain expected/valid data.


Previous 20 · Next 20

Copyright © 2024 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.