@Hartmut : I don't know how Sudoku uses the CPU. A very hard test for the FPU would be QMC@Home, it produces a higher load than most other projects. (p.s.: I don't think that Sudoku uses floating point maths in 1st place)
Got 223.61 credits on a WU done with 4.20 despite the sick leave. And never had any problem with QMC on my PII Deschutes FPU. Therein the quorum is only one.
Tullio
Donald, that's interesting... I was at Uni at the time and the WiFi access point had died again, so, no internet... and BOINC might have wanted to contact the server to report the two previous WUs, which had just finished... I already wondered if there was a connection but thought it was unlikely. But after reading your post, I'm not so sure any more.
Well, it just happened to me again, this time on a machine that's still running the old 4.14 app. So, apparently, communication problems really are a cause of our client errors.
I don't know what's going on with my ISP, though. Their service has been quite flaky lately.
I experiencied the same problem one month ago with 4.14 app. Immediately after a DSL internet connection failure, the first reported task failed with a signal 11 error.
And I was not the only one, other users had the same problem.
Here is the link to that post in "Problems and bug reports" subforum:
@Hartmut : I don't know how Sudoku uses the CPU. A very hard test for the FPU would be QMC@Home, it produces a higher load than most other projects. (p.s.: I don't think that Sudoku uses floating point maths in 1st place)
After erroring out 9 results on QMC@Home I now really believe that there's something wrong with my box regarding the FPU. So I'll exclude it from EAH.
Thank's for the hints.
@Hartmut : I don't know how Sudoku uses the CPU. A very hard test for the FPU would be QMC@Home, it produces a higher load than most other projects. (p.s.: I don't think that Sudoku uses floating point maths in 1st place)
After erroring out 9 results on QMC@Home I now really believe that there's something wrong with my box regarding the FPU. So I'll exclude it from EAH.
Thank's for the hints.
Hartmut
Anyway, thanks for letting us know what the cause of the problem was.
You seem to be the natural-born-beta-tester :-). Well, you could try to catch one this signal 11 exceptions with the ddd debugger, apparently this is still enabled on your BOINC installation but the debugger doesn't show up because BOINC runs as a daemon without X11 .
Bikeman
Goodness, looks like I can't manage... I seem to be positively collecting sig 11s atm, so I wanted to run boinc manually... and can't for the life of me remember how I did it last time without the daemon. I do have "boinc" executables in /usr/bin, but when I start from there my WUs and prefs don't show up. Could anyone please help? When I used boinc without a daemon, it was still the old shell-script style...
You seem to be the natural-born-beta-tester :-). Well, you could try to catch one this signal 11 exceptions with the ddd debugger, apparently this is still enabled on your BOINC installation but the debugger doesn't show up because BOINC runs as a daemon without X11 .
Bikeman
Goodness, looks like I can't manage... I seem to be positively collecting sig 11s atm, so I wanted to run boinc manually... and can't for the life of me remember how I did it last time without the daemon. I do have "boinc" executables in /usr/bin, but when I start from there my WUs and prefs don't show up. Could anyone please help? When I used boinc without a daemon, it was still the old shell-script style...
Strange. Isn't there a "run_client" script in the same directory where client_state.xml is located? Running that one should work. The script does nothing more than changing to this particular directory and start the boinc core client, tho.
I remember this script from older BOINC installations but don't seem to have it on this system (did locate and all, nothing there). I even copied my BOINC executable file to the /var/lib/boinc-client dir and started it from there, but it gave me an error it was unable to start...
You seem to be the natural-born-beta-tester :-). Well, you could try to catch one this signal 11 exceptions with the ddd debugger, apparently this is still enabled on your BOINC installation but the debugger doesn't show up because BOINC runs as a daemon without X11 .
Bikeman
Goodness, looks like I can't manage... I seem to be positively collecting sig 11s atm, so I wanted to run boinc manually... and can't for the life of me remember how I did it last time without the daemon. I do have "boinc" executables in /usr/bin, but when I start from there my WUs and prefs don't show up. Could anyone please help? When I used boinc without a daemon, it was still the old shell-script style...
Strange. Isn't there a "run_client" script in the same directory where client_state.xml is located? Running that one should work. The script does nothing more than changing to this particular directory and start the boinc core client, tho.
CU
H-B
BOINC 5.10.21. I have both run_client and run_manager in the BOINC directory. I start first the client and then the manager if I want to see what is going on in Einstein,SETI and QMC. If I kill the manager window BOINC is still running.
Tullio
There are reports at
)
There are reports at http://boinc.berkeley.edu/dev/forum_forum.php?id=2 that some BOINC versions are acting up when there's no web connection, e.g. :
Worst bug ever: short time without internet => most/all tasks fail!!!
(All) tasks fail when internet connection is down
@Hartmut : I don't know how Sudoku uses the CPU. A very hard test for the FPU would be QMC@Home, it produces a higher load than most other projects. (p.s.: I don't think that Sudoku uses floating point maths in 1st place)
Got 223.61 credits on a WU
)
Got 223.61 credits on a WU done with 4.20 despite the sick leave. And never had any problem with QMC on my PII Deschutes FPU. Therein the quorum is only one.
Tullio
RE: Donald, that's
)
Well, it just happened to me again, this time on a machine that's still running the old 4.14 app. So, apparently, communication problems really are a cause of our client errors.
I don't know what's going on with my ISP, though. Their service has been quite flaky lately.
I experiencied the same
)
I experiencied the same problem one month ago with 4.14 app. Immediately after a DSL internet connection failure, the first reported task failed with a signal 11 error.
And I was not the only one, other users had the same problem.
Here is the link to that post in "Problems and bug reports" subforum:
http://einsteinathome.org/node/193038&nowrap=true#77077
Josep
RE: @Hartmut : I don't
)
After erroring out 9 results on QMC@Home I now really believe that there's something wrong with my box regarding the FPU. So I'll exclude it from EAH.
Thank's for the hints.
Hartmut
RE: RE: @Hartmut : I
)
Anyway, thanks for letting us know what the cause of the problem was.
CU
Bikeman
RE: Hi Annika! You seem to
)
Goodness, looks like I can't manage... I seem to be positively collecting sig 11s atm, so I wanted to run boinc manually... and can't for the life of me remember how I did it last time without the daemon. I do have "boinc" executables in /usr/bin, but when I start from there my WUs and prefs don't show up. Could anyone please help? When I used boinc without a daemon, it was still the old shell-script style...
RE: RE: Hi Annika! You
)
Strange. Isn't there a "run_client" script in the same directory where client_state.xml is located? Running that one should work. The script does nothing more than changing to this particular directory and start the boinc core client, tho.
CU
H-B
I remember this script from
)
I remember this script from older BOINC installations but don't seem to have it on this system (did locate and all, nothing there). I even copied my BOINC executable file to the /var/lib/boinc-client dir and started it from there, but it gave me an error it was unable to start...
RE: RE: RE: Hi
)
BOINC 5.10.21. I have both run_client and run_manager in the BOINC directory. I start first the client and then the manager if I want to see what is going on in Einstein,SETI and QMC. If I kill the manager window BOINC is still running.
Tullio