Posts by [CSF] Aleksey Belkov

1) Message boards : Number crunching : Vote for BOINC (Message 2227)
Posted 26 Mar 2024 by [CSF] Aleksey Belkov
Post:
Voted*
2) Message boards : News : Project status: December 2023 (Message 2157)
Posted 27 Dec 2023 by [CSF] Aleksey Belkov
Post:
Thank you for the new and kind words!
Keep going!
Keep crunching!
And happy new year! ; )
3) Questions and Answers : Windows : Project fills CPU use to 100% although "Use at most xx% of CPU time" is set (Message 1733)
Posted 13 Sep 2022 by [CSF] Aleksey Belkov
Post:
I can see BOINC Manager shutting down and restarting the application in the background

Clearly not what should be happening.
Looks like WU's crushing or constantly suspending/restarting.
Have you any conditions in "When to suspend" section configured?
4) Questions and Answers : Windows : Project fills CPU use to 100% although "Use at most xx% of CPU time" is set (Message 1714)
Posted 22 Aug 2022 by [CSF] Aleksey Belkov
Post:
There are 20 instances of the driver for CPUs listed. So, 20 cores?

20 vCPU (Virtual), because Hyper-Threading also add "cores", but they are no "real" cores.
And news Intel CPU now have 2 class cores: "Performance-cores" and "Efficient-cores".
And HT supported only on "Perf" cores.
So: (6p x 2) + 8e = 20 virtual cores (e.g. treads).

Judging by your low power/mobile CPU, that is laptop, right?

Such CPUs, as well as laptops of such class(not gaming) in general are not designed for constant / long-term high load.
Accordingly, the cooling systems(in such laptops) are not designed for efficient cooling of CPU under heavy load ("Turbo Boost" mode).
Based on its Thermal Design Power(TDP) and current temperature, such processors under prolonged/high load will quickly lower frequencies of all cores.
I can assume that this is what causes the problems with responsiveness of your system.
I recommend you trying to reduce the number of threads available BOINC, to 6 (according to the number of real Performance class cores in this CPU).
"Options" >> "Computing preferences" >> "Usage limits" >> "Use at most 30% of the CPUs"

You should also (at least for the first time) carefully monitor the temperature of all cores, the CPU as a whole, as well as the current frequency of cores (which will show how much and how often the processor uses throttling under such a load).
5) Questions and Answers : Windows : Project fills CPU use to 100% although "Use at most xx% of CPU time" is set (Message 1709)
Posted 20 Aug 2022 by [CSF] Aleksey Belkov
Post:

I believe that the process is creating multiple threads, each of which may take an entire CPU.

This is not true at all.
Here you can see how much % of CPU each SiDock WU get.
3% = 1 of 32 thread CPU (16 core x SMT)

I will have to leave this project set to no new work until such a time as the problem is fixed. I need to be able to use my computer.

There are no any issues in general with this project.
I also crunching this project on many systems: from Nehalem arch.(Intel Xeon X5550 / 2009 y.) to Zen+ arch. (AMD Ryzen Threadripper X2950 / 2018 y.) without any issues.

Your case is some kind of rare confluence of some factors.
For example:
- CPU - problems with the new architecture (big.LITTLE) Intel have already been noticed in some situations/applications.
- OS - very raw Windows 11
- Hardware problems (in combination) with other devices
& etc

So if you really want to help this project (instead of just slam the door and leave with discontent) - give a full description of hardware components of your computer, OS version and installed drivers.
6) Message boards : Number crunching : Task's_0 file is too large to upload (Message 1597)
Posted 23 Mar 2022 by [CSF] Aleksey Belkov
Post:
hoarfrost
WU uploaded successfully.
Thank you!
7) Message boards : Number crunching : Task's_0 file is too large to upload (Message 1595)
Posted 23 Mar 2022 by [CSF] Aleksey Belkov
Post:
Good day
I have the same problem with WU сorona_Sprot_delta_v1_sidock_00227778_10:
https://www.sidock.si/sidock/result.php?resultid=51800078

According to BOINC info, WU has the size of 85,6 MiB.

Last upload try at 10:55 (UTC+3) 2022.03.23:
23-Mar-2022 10:55:24 [SiDock@home] [fxd] starting upload, upload_offset -1
23-Mar-2022 10:55:24 [SiDock@home] [http] HTTP_OP::libcurl_exec(): ca-bundle '*****\BOINC\ca-bundle.crt'
23-Mar-2022 10:55:24 [SiDock@home] [http] HTTP_OP::libcurl_exec(): ca-bundle set
23-Mar-2022 10:55:24 [SiDock@home] Started upload of corona_Sprot_delta_v1_sidock_00227778_10_r1432721829_0
23-Mar-2022 10:55:24 [SiDock@home] [file_xfer] URL: https://www.sidock.si/sidock_cgi/file_upload_handler
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:  Connection 7662 seems to be dead!
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:  Closing connection 7662
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:    Trying 83.149.227.88...
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:  Connected to www.sidock.si (83.149.227.88) port 443 (#7664)
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:  ALPN, offering http/1.1
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:  Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:  successfully set certificate verify locations:
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:    CAfile: *****\BOINC\ca-bundle.crt
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:    CApath: none
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:  TLSv1.2 (OUT), TLS header, Certificate Status (22):
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:  TLSv1.2 (OUT), TLS handshake, Client hello (1):
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:  TLSv1.2 (IN), TLS handshake, Server hello (2):
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:  TLSv1.2 (IN), TLS handshake, Certificate (11):
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:  TLSv1.2 (IN), TLS handshake, Server key exchange (12):
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:  TLSv1.2 (IN), TLS handshake, Server finished (14):
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:  TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:  TLSv1.2 (OUT), TLS change cipher, Client hello (1):
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:  TLSv1.2 (OUT), TLS handshake, Finished (20):
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:  TLSv1.2 (IN), TLS change cipher, Client hello (1):
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:  TLSv1.2 (IN), TLS handshake, Finished (20):
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:  SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:  ALPN, server accepted to use http/1.1
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:  Server certificate:
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:  	 subject: CN=sidock.si
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:  	 start date: Jan 25 18:58:18 2022 GMT
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:  	 expire date: Apr 25 18:58:17 2022 GMT
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:  	 subjectAltName: www.sidock.si matched
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:  	 issuer: C=US; O=Let's Encrypt; CN=R3
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:  	 SSL certificate verify ok.
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Sent header to server: POST /sidock_cgi/file_upload_handler HTTP/1.1

23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Sent header to server: Host: www.sidock.si

23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Sent header to server: User-Agent: BOINC client (windows_x86_64 7.16.20)

23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Sent header to server: Accept: */*

23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Sent header to server: Accept-Encoding: deflate, gzip

23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Sent header to server: Accept-Language: en_GB

23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Sent header to server: Content-Length: 308

23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Sent header to server: Content-Type: application/x-www-form-urlencoded

23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Sent header to server: 

23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:  We are completely uploaded and fine
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Received header from server: HTTP/1.1 200 OK

23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Received header from server: Date: Wed, 23 Mar 2022 07:55:24 GMT

23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Received header from server: Server: Apache/2.4.29 (Ubuntu)

23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Received header from server: Vary: Accept-Encoding

23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Received header from server: Content-Encoding: gzip

23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Received header from server: Content-Length: 75

23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Received header from server: Content-Type: text/plain

23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Received header from server: 

23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Received header from server: ‹
23-Mar-2022 10:55:24 [---] [http_xfer] [ID#8164] HTTP: wrote 93 bytes
23-Mar-2022 10:55:24 [SiDock@home] [http] [ID#8164] Info:  Connection #7664 to host www.sidock.si left intact
23-Mar-2022 10:55:25 [SiDock@home] [file_xfer] http op done; retval 0 (Success)
23-Mar-2022 10:55:25 [SiDock@home] [file_xfer] parsing upload response: <data_server_reply>
    <status>0</status>
    <file_size>0</file_size>
</data_server_reply>
23-Mar-2022 10:55:25 [SiDock@home] [file_xfer] parsing status: 0
23-Mar-2022 10:55:25 [SiDock@home] [fxd] starting upload, upload_offset 0
23-Mar-2022 10:55:25 [SiDock@home] [http] HTTP_OP::libcurl_exec(): ca-bundle set
23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Info:  Found bundle for host www.sidock.si: 0x3067550 [can pipeline]
23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Info:  Re-using existing connection! (#7664) with host www.sidock.si
23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Info:  Connected to www.sidock.si (83.149.227.88) port 443 (#7664)
23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Sent header to server: POST /sidock_cgi/file_upload_handler HTTP/1.1

23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Sent header to server: Host: www.sidock.si

23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Sent header to server: User-Agent: BOINC client (windows_x86_64 7.16.20)

23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Sent header to server: Accept: */*

23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Sent header to server: Accept-Encoding: deflate, gzip

23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Sent header to server: Accept-Language: en_GB

23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Sent header to server: Content-Length: 89757918

23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Sent header to server: Content-Type: application/x-www-form-urlencoded

23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Sent header to server: Expect: 100-continue

23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Sent header to server: 

23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Received header from server: HTTP/1.1 413 Request Entity Too Large

23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Received header from server: Date: Wed, 23 Mar 2022 07:55:25 GMT

23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Received header from server: Server: Apache/2.4.29 (Ubuntu)

23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Received header from server: Connection: close

23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Received header from server: Content-Type: text/html; charset=iso-8859-1

23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Received header from server: 

23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Received header from server: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Received header from server: <html><head>
23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Received header from server: <title>413 Request Entity Too Large</title>
23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Received header from server: </head><body>
23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Received header from server: <h1>Request Entity Too Large</h1>
23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Received header from server: The requested resource does not allow request data with POST requests, or the amount of data provided in
23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Received header from server: the request exceeds the capacity limit.
23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Received header from server: <hr>
23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Received header from server: <address>Apache/2.4.29 (Ubuntu) Server at www.sidock.si Port 443</address>
23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Received header from server: </body></html>
23-Mar-2022 10:55:25 [---] [http_xfer] [ID#8164] HTTP: wrote 396 bytes
23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Info:  TLSv1.2 (IN), TLS alert, Client hello (1):
23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Info:  Closing connection 7664
23-Mar-2022 10:55:25 [SiDock@home] [http] [ID#8164] Info:  TLSv1.2 (OUT), TLS alert, Client hello (1):
23-Mar-2022 10:55:26 [SiDock@home] [file_xfer] http op done; retval -224 (permanent HTTP error)
23-Mar-2022 10:55:26 [SiDock@home] [file_xfer] file transfer status -224 (permanent HTTP error)
23-Mar-2022 10:55:26 [SiDock@home] Backing off 05:34:59 on upload of corona_Sprot_delta_v1_sidock_00227778_10_r1432721829_0
8) Message boards : Number crunching : MD5 check failed for ABU-DHABI.png (Message 865)
Posted 3 May 2021 by [CSF] Aleksey Belkov
Post:

A) The expected value is not a md5sum.

Yes, "expected" value is actually a SHA256 sum, but without the last character(63 out of 64 required characters).

Below is the actual hashsums of this file:
MD5 - 87D2448035BFF7E8852D10343C281D68
SHA256 - 0A8D7A4A3B37940A62CD0CCB21ECD9799C5835D5BE8E3C40A85FB36F20B0708A

If you compare with the values (below) from the log, they match(not counting the absence of one character in the "expected" SHA256 sum).


B) You quoted the same message twice.

Yes, but only because messages always the same.
As example:
03/05/2021 04:33:38 | SiDock@home | Resetting file projects/www.sidock.si_sidock/ABU-DHABI.png: md5 checksum failed for file
03/05/2021 04:33:40 | SiDock@home | Started download of ABU-DHABI.png
03/05/2021 04:33:41 | SiDock@home | Finished download of ABU-DHABI.png
03/05/2021 04:33:41 | SiDock@home | [error] MD5 check failed for ABU-DHABI.png
03/05/2021 04:33:41 | SiDock@home | [error] expected 0a8d7a4a3b37940a62cd0ccb21ecd9799c5835d5be8e3c40a85fb36f20b0708, got 87d2448035bff7e8852d10343c281d68
03/05/2021 04:33:41 | SiDock@home | [error] Checksum or signature error for ABU-DHABI.png



I guess something interfered with the communication. Is the expected value reproducible?

That was reproducible at any startup of this BOINC instance.
BOINC does not report any network error when downloading the file, and given that the file is downloaded over HTTPS this guarantees its integrity.
I searched for "expected" value in the BOINC files, but found its mention only in stdoutdae.txt and client_state.xml,
Therefore, it is logical to assume that the" expected " value of hashsum, the BOINC client is received from the server when downloading the file for integrity checking.
But after resetting project the problem has gone *rolling eyes*
9) Message boards : Number crunching : MD5 check failed for ABU-DHABI.png (Message 837)
Posted 28 Apr 2021 by [CSF] Aleksey Belkov
Post:
Good day,
I noticed the following error in the BOINC log:
28/04/2021 17:30:18 | SiDock@home | [error] MD5 check failed for ABU-DHABI.png
28/04/2021 17:30:18 | SiDock@home | [error] expected 0a8d7a4a3b37940a62cd0ccb21ecd9799c5835d5be8e3c40a85fb36f20b0708, got 87d2448035bff7e8852d10343c281d68
28/04/2021 17:30:18 | SiDock@home | [error] Checksum or signature error for ABU-DHABI.png


I tried to solve the problem by deleting this file and re-downloading it, but problem stays the same:

28/04/2021 17:30:17 | SiDock@home | Started download of ABU-DHABI.png
28/04/2021 17:30:18 | SiDock@home | Finished download of ABU-DHABI.png
28/04/2021 17:30:18 | SiDock@home | [error] MD5 check failed for ABU-DHABI.png
28/04/2021 17:30:18 | SiDock@home | [error] expected 0a8d7a4a3b37940a62cd0ccb21ecd9799c5835d5be8e3c40a85fb36f20b0708, got 87d2448035bff7e8852d10343c281d68
28/04/2021 17:30:18 | SiDock@home | [error] Checksum or signature error for ABU-DHABI.png


The file itself is a quite valid PNG image.
Perhaps the problem is that the server reports to BOINC client incorrect checksum/signature for integrity check of the downloaded file.

System:
Starting BOINC client version 7.16.11 for windows_x86_64
OS: Microsoft Windows 10: x64 Edition, (10.00.17763.00)




©2024 SiDock@home Team