Posts by Eric_Kaiser

log in
1) Message boards : Number crunching : WUProp Have A New Project URL? 's' added to http. (Message 4830)
Posted 12 Mar 2017 by Profile Eric_Kaiser
To be honest: Using notepad or whatsoever is not a solution. It is a dirty workaround.
Anything regarding project urls should be working with either resetting a project or using detach and reattach.
2) Message boards : Number crunching : WUProp Have A New Project URL? 's' added to http. (Message 4818)
Posted 12 Mar 2017 by Profile Eric_Kaiser
All androids are running fine again. Whatever may have caused the trouble has vanished.
3) Message boards : Number crunching : WUProp Have A New Project URL? 's' added to http. (Message 4816)
Posted 11 Mar 2017 by Profile Eric_Kaiser
On Android 4.x NativeBoinc as the Bercley Client doesn't allow remote access, cc_config.xml and name setting and doesn't run well.

Lots of invalids on projects while on nativeboinc I see zero invalids.

Edit: I checked my nativeboinc androids and 4 out of 7 are ok again. Only 3 still have the issue. Didn't make any changes
4) Message boards : Number crunching : WUProp Have A New Project URL? 's' added to http. (Message 4796)
Posted 9 Mar 2017 by Profile Eric_Kaiser
I have one windows and four linux computers running where I didn't need to change anything. They are still running fine. Oh well, a raspberry too.
Additionally I have six Androids (with Android 5.0 and 6.0) that run fine, too. There was no need to make any changes.
And I have seven Androids (with Android 4.2/4.4) that don't run wuprop because of the problems. Three of them are rooted so I could eventually make changes manually. On the other four I have no chance to make changes.
On these androids I'm loosing 3,552 hours in my wuprop-statistics every day.

What is the official solution for the connection problems?
5) Message boards : Number crunching : WUProp Have A New Project URL? 's' added to http. (Message 4790)
Posted 8 Mar 2017 by Profile Eric_Kaiser
Tested again on one android running 4.x.
Detached the project and tried to add it with https again.
Adding failed with error -184. So added the project again with http only.
The question is why do I receive v4 nci wu?
The v5 version has pie and non_pie available and is running fine on all other androids with android >=5

Here is one result log:


Name data_collect_v4_1488715731_2186_0
Arbeitspaket 66394594
Erstellt 5 Mar 2017, 13:51:27 UTC
Gesendet 5 Mar 2017, 20:59:46 UTC
Ablaufdatum 12 Mar 2017, 20:59:46 UTC
Empfangen 8 Mar 2017, 6:52:45 UTC
Serverstatus Abgeschlossen
Resultat Berechnungsfehler
Clientstatus am herunterladen
Endstatus -186 (0xffffffffffffff46) ERR_RESULT_DOWNLOAD
Computer ID 123591
Laufzeit
CPU Zeit
Pr├╝fungsstatus Ung├╝ltig
Punkte 0.00
Device peak FLOPS 0.02 GFLOPS
Anwendungsversion Data collect version 4 v4.20 (nci)
Stderr Ausgabe

<core_client_version>7.0.36</core_client_version>
<![CDATA[
<message>
WU download error: couldn't get input files:
<file_xfer_error>
<file_name>data_collect_v4_1488715731_2186</file_name>
<error_code>-197</error_code>
<error_message>user requested transfer abort</error_message>
</file_xfer_error>

</message>
]]>
6) Message boards : Number crunching : WUProp Have A New Project URL? 's' added to http. (Message 4786)
Posted 7 Mar 2017 by Profile Eric_Kaiser
Can't edit my last post...

Seems that only android 4.x devices are affected.
My other androids with 5.x and 6.x are running fine.

The 4.x devices are capable to run arm_pie (v5 wu) but they are trying to fetch nci versions (v4 wu).
7) Message boards : Number crunching : WUProp Have A New Project URL? 's' added to http. (Message 4785)
Posted 7 Mar 2017 by Profile Eric_Kaiser
I have only issues with my android devices. Upload and Downloads are stuck.
Resetting the project doesn't help.
On two of my androids I removed the project and added it again with https, but this makes no difference. Either http or https gives me 'Temporarily failed download of data_collect_v4_1488715731_18645: transient HTTP error'

All other devices (Windows/Linux) work without changes being made by me.
8) Message boards : Number crunching : Last day (hours) on GoofyxGrid (Message 3935)
Posted 5 Jul 2016 by Profile Eric_Kaiser
Thanks for letting me know.
I was wondering too.
9) Message boards : Number crunching : Failing wu on linux on arm device (Message 2083)
Posted 12 Mar 2014 by Profile Eric_Kaiser
Ok, a couple of wu are calculated now. They are validated and credit was granted.

I'm not sure if the hrs for the active project on this device are counted correctly and added to the project at wuprop.

The stderr output is now:

<core_client_version>7.2.7</core_client_version>
<![CDATA[
<stderr_txt>
15:57:43 (10148): Erreur wu_terminee (wu deja reportee)
16:27:43 (10148): Erreur reception active_result
17:21:43 (10148): Erreur reception active_result
17:25:43 (10148): Erreur reception active_result
17:39:43 (10148): Erreur reception active_result
17:45:43 (10148): Erreur reception active_result
17:52:43 (10148): Erreur reception active_result
18:21:43 (10148): Erreur reception active_result
18:38:43 (10148): Erreur reception active_result
18:57:43 (10148): called boinc_finish

</stderr_txt>
]]>
10) Message boards : Number crunching : Failing wu on linux on arm device (Message 2082)
Posted 11 Mar 2014 by Profile Eric_Kaiser
Thank you very much for your assistance.
I made the suggested changes in the source code and compiled it. The first wu is now running.
I will report whether it was successfull or not.
11) Message boards : Number crunching : Failing wu on linux on arm device (Message 2078)
Posted 11 Mar 2014 by Profile Eric_Kaiser
I'm running an arm device odroid u3 with ubuntu 13.10.

I've attached this device to wuprop and it downloaded data_collect_v3_3.52_arm-unknown-linux-gnueabihf__nci which is correct because the arm cpu supports hardfloat.
But every wu errors out immediately with the following error:

<core_client_version>7.2.7</core_client_version>
<![CDATA[
<message>
process exited with code 127 (0x7f, -129)
</message>
<stderr_txt>
../../projects/wuprop.boinc-af.org/data_collect_v3_3.52_arm-unknown-linux-gnueabihf__nci: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory

</stderr_txt>
]]>

ldd results are:
libstdc++.so.6 => not found
libm.so.6 => /lib/arm-linux-gnueabi/libm.so.6 (0xb6e6a000)
libgcc_s.so.1 => /lib/arm-linux-gnueabi/libgcc_s.so.1 (0xb6e47000)
libpthread.so.0 => /lib/arm-linux-gnueabi/libpthread.so.0 (0xb6e2c000)
libc.so.6 => /lib/arm-linux-gnueabi/libc.so.6 (0xb6d47000)
/lib/ld-linux.so.3 (0xb6f0d000)

Seems that libstdc++.so.6 was not linked during compile of the executable.

I've downloaded the sources for v3.52 and compiled it myself. I put the compiled version in the project folder and renamed it to data_collect_v3_3.52_arm-unknown-linux-gnueabihf__nci.
Owner and access rights were set according to the original file.

On a first sight wu finish ok but they end in status "finished, but not valid".

stderr output:
<core_client_version>7.2.7</core_client_version>
<![CDATA[
<stderr_txt>
09:37:09 (7665): Nombre de GPU non conforme: 0
09:38:09 (7665): Nombre de GPU non conforme: 0
09:39:09 (7665): Nombre de GPU non conforme: 0
09:40:09 (7665): Nombre de GPU non conforme: 0
09:41:09 (7665): Nombre de GPU non conforme: 0
09:42:09 (7665): Nombre de GPU non conforme: 0
09:43:09 (7665): Nombre de GPU non conforme: 0
09:44:09 (7665): Nombre de GPU non conforme: 0
09:45:09 (7665): Nombre de GPU non conforme: 0
09:46:09 (7665): Nombre de GPU non conforme: 0
09:47:09 (7665): Nombre de GPU non conforme: 0
09:48:09 (7665): Nombre de GPU non conforme: 0
09:49:09 (7665): Nombre de GPU non conforme: 0
09:50:09 (7665): Nombre de GPU non conforme: 0
09:51:09 (7665): Nombre de GPU non conforme: 0
09:52:09 (7665): Nombre de GPU non conforme: 0
09:53:09 (7665): Nombre de GPU non conforme: 0
09:54:09 (7665): Nombre de GPU non conforme: 0
09:55:09 (7665): Nombre de GPU non conforme: 0
09:56:09 (7665): Nombre de GPU non conforme: 0
09:57:09 (7665): Nombre de GPU non conforme: 0
09:58:09 (7665): Nombre de GPU non conforme: 0
09:59:09 (7665): Nombre de GPU non conforme: 0
10:00:09 (7665): Nombre de GPU non conforme: 0
10:01:09 (7665): Nombre de GPU non conforme: 0
10:02:09 (7665): Nombre de GPU non conforme: 0
10:03:09 (7665): Nombre de GPU non conforme: 0
10:04:09 (7665): Nombre de GPU non conforme: 0
10:05:09 (7665): Nombre de GPU non conforme: 0
10:06:09 (7665): Nombre de GPU non conforme: 0
10:07:09 (7665): Nombre de GPU non conforme: 0
10:08:09 (7665): Nombre de GPU non conforme: 0
10:09:09 (7665): Nombre de GPU non conforme: 0
10:10:09 (7665): Nombre de GPU non conforme: 0
10:11:09 (7665): Nombre de GPU non conforme: 0
10:12:09 (7665): Nombre de GPU non conforme: 0
10:13:09 (7665): Nombre de GPU non conforme: 0
10:14:09 (7665): Nombre de GPU non conforme: 0
10:15:09 (7665): Erreur reception host_info
10:16:09 (7665): Nombre de GPU non conforme: 0
10:17:09 (7665): Nombre de GPU non conforme: 0
10:18:09 (7665): Nombre de GPU non conforme: 0
10:19:09 (7665): Nombre de GPU non conforme: 0
10:20:09 (7665): Nombre de GPU non conforme: 0
10:21:09 (7665): Nombre de GPU non conforme: 0
10:22:09 (7665): Nombre de GPU non conforme: 0
10:23:09 (7665): Nombre de GPU non conforme: 0
10:24:09 (7665): Nombre de GPU non conforme: 0
10:25:09 (7665): Nombre de GPU non conforme: 0
10:26:09 (7665): Nombre de GPU non conforme: 0
10:27:09 (7665): Nombre de GPU non conforme: 0
10:28:09 (7665): Nombre de GPU non conforme: 0
10:29:09 (7665): Nombre de GPU non conforme: 0
10:30:09 (7665): Nombre de GPU non conforme: 0
10:31:09 (7665): Nombre de GPU non conforme: 0
10:32:09 (7665): Nombre de GPU non conforme: 0
10:33:09 (7665): Nombre de GPU non conforme: 0
10:34:09 (7665): Nombre de GPU non conforme: 0
10:35:09 (7665): Nombre de GPU non conforme: 0
10:36:09 (7665): Nombre de GPU non conforme: 0
10:37:09 (7665): Nombre de GPU non conforme: 0
10:38:09 (7665): Nombre de GPU non conforme: 0
10:39:09 (7665): Nombre de GPU non conforme: 0
10:40:09 (7665): Nombre de GPU non conforme: 0
10:41:09 (7665): Nombre de GPU non conforme: 0
10:42:09 (7665): Nombre de GPU non conforme: 0
10:43:09 (7665): Nombre de GPU non conforme: 0
10:44:09 (7665): Nombre de GPU non conforme: 0
10:45:09 (7665): Nombre de GPU non conforme: 0
10:46:09 (7665): Nombre de GPU non conforme: 0
10:47:09 (7665): Erreur reception host_info
10:48:09 (7665): Nombre de GPU non conforme: 0
10:49:09 (7665): Nombre de GPU non conforme: 0
10:50:09 (7665): Erreur reception host_info
10:51:09 (7665): Erreur reception host_info
10:52:09 (7665): Erreur reception host_info
10:53:09 (7665): Erreur reception host_info
10:54:09 (7665): Erreur reception host_info
10:55:09 (7665): Erreur reception host_info
10:56:09 (7665): Erreur reception host_info
10:57:09 (7665): Erreur reception host_info
10:58:09 (7665): Erreur reception host_info
10:59:09 (7665): Erreur reception host_info
11:00:09 (7665): Nombre de GPU non conforme: 0
11:01:09 (7665): Nombre de GPU non conforme: 0
11:02:09 (7665): Nombre de GPU non conforme: 0
11:03:09 (7665): Nombre de GPU non conforme: 0
11:04:09 (7665): Nombre de GPU non conforme: 0
11:05:09 (7665): Nombre de GPU non conforme: 0
11:06:09 (7665): Nombre de GPU non conforme: 0
11:07:09 (7665): Nombre de GPU non conforme: 0
11:08:09 (7665): Nombre de GPU non conforme: 0
11:09:09 (7665): Nombre de GPU non conforme: 0
11:10:09 (7665): Nombre de GPU non conforme: 0
11:11:09 (7665): Nombre de GPU non conforme: 0
11:12:09 (7665): Nombre de GPU non conforme: 0
11:13:09 (7665): Nombre de GPU non conforme: 0
11:14:09 (7665): Nombre de GPU non conforme: 0
11:15:09 (7665): Nombre de GPU non conforme: 0
11:16:09 (7665): Nombre de GPU non conforme: 0
11:17:09 (7665): Nombre de GPU non conforme: 0
11:18:09 (7665): Nombre de GPU non conforme: 0
11:19:09 (7665): Nombre de GPU non conforme: 0
11:20:09 (7665): Nombre de GPU non conforme: 0
11:21:09 (7665): Nombre de GPU non conforme: 0
11:22:09 (7665): Nombre de GPU non conforme: 0
11:23:09 (7665): Nombre de GPU non conforme: 0
11:24:09 (7665): Erreur reception host_info
11:25:09 (7665): Erreur reception host_info
11:26:09 (7665): Erreur reception host_info
11:27:09 (7665): Nombre de GPU non conforme: 0
11:28:09 (7665): Nombre de GPU non conforme: 0
11:29:09 (7665): Erreur reception host_info
11:30:09 (7665): Nombre de GPU non conforme: 0
11:31:10 (7665): Nombre de GPU non conforme: 0
11:32:11 (7665): Nombre de GPU non conforme: 0
11:33:11 (7665): Nombre de GPU non conforme: 0
11:34:11 (7665): Nombre de GPU non conforme: 0
11:35:11 (7665): Nombre de GPU non conforme: 0
11:36:11 (7665): Nombre de GPU non conforme: 0
11:37:11 (7665): Nombre de GPU non conforme: 0
11:38:11 (7665): Nombre de GPU non conforme: 0
11:39:11 (7665): Nombre de GPU non conforme: 0
11:40:11 (7665): Nombre de GPU non conforme: 0
11:41:11 (7665): Nombre de GPU non conforme: 0
11:42:11 (7665): Nombre de GPU non conforme: 0
11:43:11 (7665): Nombre de GPU non conforme: 0
11:44:11 (7665): Nombre de GPU non conforme: 0
11:45:11 (7665): Nombre de GPU non conforme: 0
11:46:11 (7665): Nombre de GPU non conforme: 0
11:47:11 (7665): Nombre de GPU non conforme: 0
11:48:11 (7665): Nombre de GPU non conforme: 0
11:49:11 (7665): Nombre de GPU non conforme: 0
11:50:11 (7665): Nombre de GPU non conforme: 0
11:51:11 (7665): Nombre de GPU non conforme: 0
11:52:11 (7665): Nombre de GPU non conforme: 0
11:53:11 (7665): Nombre de GPU non conforme: 0
11:54:11 (7665): Nombre de GPU non conforme: 0
11:55:11 (7665): Nombre de GPU non conforme: 0
11:56:11 (7665): Nombre de GPU non conforme: 0
11:57:11 (7665): Nombre de GPU non conforme: 0
11:58:11 (7665): Nombre de GPU non conforme: 0
11:59:11 (7665): Nombre de GPU non conforme: 0
12:00:11 (7665): Nombre de GPU non conforme: 0
12:01:11 (7665): Nombre de GPU non conforme: 0
12:02:11 (7665): Nombre de GPU non conforme: 0
12:03:11 (7665): Nombre de GPU non conforme: 0
12:04:11 (7665): Nombre de GPU non conforme: 0
12:05:11 (7665): Nombre de GPU non conforme: 0
12:06:11 (7665): Nombre de GPU non conforme: 0
12:07:11 (7665): Nombre de GPU non conforme: 0
12:08:11 (7665): Nombre de GPU non conforme: 0
12:09:11 (7665): Nombre de GPU non conforme: 0
12:10:11 (7665): Nombre de GPU non conforme: 0
12:11:11 (7665): Nombre de GPU non conforme: 0
12:12:11 (7665): Nombre de GPU non conforme: 0
12:13:11 (7665): Nombre de GPU non conforme: 0
12:14:11 (7665): Nombre de GPU non conforme: 0
12:15:11 (7665): Nombre de GPU non conforme: 0
12:16:11 (7665): Nombre de GPU non conforme: 0
12:17:11 (7665): Nombre de GPU non conforme: 0
12:18:11 (7665): Nombre de GPU non conforme: 0
12:19:11 (7665): Nombre de GPU non conforme: 0
12:20:11 (7665): Nombre de GPU non conforme: 0
12:21:11 (7665): Nombre de GPU non conforme: 0
12:22:11 (7665): Nombre de GPU non conforme: 0
12:23:11 (7665): Nombre de GPU non conforme: 0
12:24:11 (7665): Nombre de GPU non conforme: 0
12:25:11 (7665): Nombre de GPU non conforme: 0
12:26:11 (7665): Nombre de GPU non conforme: 0
12:27:11 (7665): Nombre de GPU non conforme: 0
12:28:11 (7665): Nombre de GPU non conforme: 0
12:29:11 (7665): Nombre de GPU non conforme: 0
12:30:11 (7665): Nombre de GPU non conforme: 0
12:31:11 (7665): Nombre de GPU non conforme: 0
12:32:11 (7665): Nombre de GPU non conforme: 0
12:33:11 (7665): Nombre de GPU non conforme: 0
12:34:11 (7665): Nombre de GPU non conforme: 0
12:35:11 (7665): Nombre de GPU non conforme: 0
12:36:11 (7665): Nombre de GPU non conforme: 0
12:36:11 (7665): called boinc_finish

</stderr_txt>
]]>

Do you have any idea how I can solve this?

Kind Regards

Eric

PS: Link to all wu from this host: http://wuprop.boinc-af.org/results.php?hostid=66351
12) Message boards : News : Server mirgration (Message 1548)
Posted 31 Aug 2013 by Profile Eric_Kaiser
It is working now. Thank you for your support.
13) Message boards : News : Server mirgration (Message 1545)
Posted 31 Aug 2013 by Profile Eric_Kaiser
yepp. Same here. This also means I don't get a new WU...
14) Message boards : News : Server mirgration (Message 1542)
Posted 31 Aug 2013 by Profile Eric_Kaiser
I got the following messages:
31.08.2013 11:25:28 | WUProp@Home | update requested by user
31.08.2013 11:25:30 | WUProp@Home | Sending scheduler request: Requested by user.
31.08.2013 11:25:30 | WUProp@Home | Requesting new tasks for CPU
31.08.2013 11:25:31 | WUProp@Home | Scheduler request failed: HTTP internal server error




Home | My Account | Message Boards | Results


Copyright © 2020 Sebastien