BOINC Manager has downloaded a number of work units and is actively working on 3 of them. If I hit the graphics button, it looks pretty ok to me, but I will do the following (as soon as I am at this machine again):
1. Un-Hide my computer
2. Send further information
What puzzles me a great deal is that is worked for one start and then failed again.
Thanks. Looking at the finished tasks (there are no errored ones) shows that they don't show the errors you posted previously:
Quote:
15:44:11 (18108): Can't open init data file - running in standalone mode
2021-02-22 15:44:11.4000 (18108) [CRITICAL]: ERROR: no result file has been specified
Any idea in which task that might have originated? Maybe it's useful to limit BOINC to running one tasks at a time to avoid potential confusion about which task is throwing what errors. If would be helpful to find the task (or a similar one) that produced the original error. Hint: compare the file data/time of stderr.txt and stderrgfx.txt to correlate events.
Just to make sure: by running only once, you refer to the graphics in screensaver mode, not the manual graphics or the science app, right?
Also, please enable screensaver debugging in BOINC's event log settings.
Graphics from BOINC Manager (by clicking the button) will work always. Just the screensaver fails 99.9% of the time. I got it to show up 2 times, right after changing settings here on the website and synchronizing this with BOINC Manager. But I am not at all sure that this is even related.
The errors in the log were the latest (or only) errors in there. As I said, I did a complete re-install of anything, including deleting all local files in between uninstall and install.
EDIT:
I will enable screensaver logging and get back to you with the information!
EDIT2:
Now I am completly lost. I have changed the logging settings and added screensaver logs. Then I started the manager, waited until the screensaver comes up... it failed. I checked the logs... and there is no log file of today. The latest log there is is the one from the 22nd, yesterday.
So, no new information other than it still does not work and it still always works ok if I click the button.
EDIT3:
Which log should be monitored anyway? In the slot (which one?), the project folder or in the log messages in the BOINC Manager? They all seem to have very different contents... In the Manager there are entries of today, but no error messages or warnings whatsoever... and the other files are not being written at all it seems.
EDIT4:
There is just one task active now. I can still start graphics with the button at any time without any issue. Screensaver logs are enabled. Screensaver still fails and there is nothing in any of the logs at all.
I am about to just let it go, really.
changing settings here on the website and synchronizing this with BOINC Manager. But I am not at all sure that this is even related.
You're right, it isn't. The screensaver settings we provide here on the website affect the graphics in both, "Show Graphics" and screensaver mode.
Quote:
Which log should be monitored anyway?
The screensaver debug logs should appear in BOINC's Event Log (in the Manager, at least). Too bad it doesn't provide any hints :-/
Quote:
I am about to just let it go, really.
Honestly, that's probably the wisest thing to do until the related upstream issues are resolved. Apparently you're not the only one. Here's one remarkable quote from BOINC's main author: "the screensaver is a disaster"...
I checked memory allocation and I have 8 Gb of RAM and when BOINC is running 3 tasks it still has 50% resources reporting. I'm running version 7.16.11 of BOINC. When I start the screen saver by clicking on the "show graphics" button, it does show the statistics and other data for the jobs running. I cleared both stderr.txt, stderrscrgfx.txt and run them, getting the same results with the screen saver cycling between the 3 states. I looked at the error texts to see what was going on and found the following:
stderr.txt
DEPRECATION WARNING: program has invoked obsolete function XLALGetVersionString(). Please see XLALVCSInfoString() for information about a replacement.
Code-version: %% LAL: 6.19.2.1 (CLEAN ed30a8358ee2fa6952b3bd4d99f3f4c6ebc7a5de)
%% LALPulsar: 1.17.1.1 (CLEAN ed30a8358ee2fa6952b3bd4d99f3f4c6ebc7a5de)
%% LALApps: 6.23.0.1 (CLEAN ed30a8358ee2fa6952b3bd4d99f3f4c6ebc7a5de)
There is also a stderr.txt in slot\0 that reports:
putenv 'LAL_DEBUG_LEVEL=3'
2021-02-25 03:13:01.6925 (4216) [normal]: This program is published under the GNU General Public License, version 2
2021-02-25 03:13:01.6965 (4216) [normal]: For details see http://einstein.phys.uwm.edu/license.php
2021-02-25 03:13:01.6985 (4216) [normal]: This Einstein@home App was built at: Dec 19 2019 11:51:52
2021-02-25 03:13:01.7015 (4216) [normal]: Start of BOINC application 'projects/einstein.phys.uwm.edu/einstein_O2MD1_2.09_windows_x86_64__GWnew.exe'.
Activated exception handling...
2021-02-25 03:13:01.7085 (4216) [debug]: BSGL output files
2021-02-25 03:13:01.7405 (4216) [debug]: Flags: LAL_DEBUG, OPTIMIZE, HS_OPTIMIZATION, GC_SSE2_OPT, X64, SSE, SSE2, GNUC X86 GNUX86
2021-02-25 03:13:01.7455 (4216) [debug]: Set up communication with graphics process.
DEPRECATION WARNING: program has invoked obsolete function XLALGetVersionString(). Please see XLALVCSInfoString() for information about a replacement.
Code-version: %% LAL: 6.19.2.1 (CLEAN ed30a8358ee2fa6952b3bd4d99f3f4c6ebc7a5de)
%% LALPulsar: 1.17.1.1 (CLEAN ed30a8358ee2fa6952b3bd4d99f3f4c6ebc7a5de)
%% LALApps: 6.23.0.1 (CLEAN ed30a8358ee2fa6952b3bd4d99f3f4c6ebc7a5de)
2021-02-25 03:13:03.5314 (4216) [normal]: Reading input data ... 2021-02-25 03:18:01.3635 (4216) [normal]: Search FstatMethod used: 'ResampGeneric'
2021-02-25 03:18:01.3645 (4216) [normal]: Recalc FstatMethod used: 'DemodSSE'
2021-02-25 03:18:01.3655 (4216) [normal]: SSE2 version is used for the semi-coherent step!
2021-02-25 03:19:17.4792 (4216) [normal]: Number of segments: 22, total number of SFTs in segments: 9902
done.
% --- GPS reference time = 1177806642.5000 , GPS data mid time = 1177806642.5000
2021-02-25 03:19:17.6481 (4216) [normal]: dFreqStack = 7.061150e-007, df1dot = 4.521800e-012, df2dot = 2.284100e-018, df3dot = 0.000000e+000
% --- Setup, N = 22, T = 604800 s, Tobs = 19646545 s, gammaRefine = 37, gamma2Refine = 45, gamma3Refine = 1
DEPRECATION WARNING: program has invoked obsolete function InitDopplerSkyScan(). Please see XLALInitDopplerSkyScan() for information about a replacement.
2021-02-25 03:19:17.6641 (4216) [normal]: INFO: No checkpoint checkpoint.cpt found - starting from scratch
% --- Cpt:0, total:19, sky:1/1, f1dot:1/1
Same deprecation error. It appears that it is looking for a line of code that has been changed. XLALGetVersionString() has been changed to XLALVCSInfoString().
all of that looks perfectly normal and it didn't reproduce the error you posted earlier. Also, the following shows that the screensaver ran for almost a minute and got shut down normally, due to mouse movement:
By cycling I mean that the screen saver comes on with a message telling me that BOINC has started the screen saver, it then flashes to the statistics screen, which then flashes the screen saver loading the star globe, and it then goes back to the screen saver loading BOINC. I haven't timed it but this cycle will continue until I move the mouse or tap a key. It never does land on the star globe long enough to really load it.
What about the message in the deprecation error? Is that normal?
so far I have only been working with “simple” PC builds and found information about the settings relatively quickly in the forum. Now I wanted to integrate a second graphics card and run both in parallel.
I activated multiGPU via cc_config as follows.
<cc_config>
<options>
<use_all_gpus>1</use_all_gpus>
</options>
</cc_config>
Because my 1st GPU (RTX 4080) has enough VRAM, I have set several WU per GPU via app_config.
I want the 1st GPU (RTX 4080) to calculate 4 WUs at the same time and the 2nd GPU (RTX 2070 Super) to calculate 3 WUs. Because the 2070 has too less VRAM and can only load 3 WUs.
BOINC Manager has downloaded
)
BOINC Manager has downloaded a number of work units and is actively working on 3 of them. If I hit the graphics button, it looks pretty ok to me, but I will do the following (as soon as I am at this machine again):
1. Un-Hide my computer
2. Send further information
What puzzles me a great deal is that is worked for one start and then failed again.
This should be my computer:
https://einsteinathome.org/host/12866758/tasks/0/0
(it is not hidden anymore)
Thanks. Looking at the
)
Thanks. Looking at the finished tasks (there are no errored ones) shows that they don't show the errors you posted previously:
Any idea in which task that might have originated? Maybe it's useful to limit BOINC to running one tasks at a time to avoid potential confusion about which task is throwing what errors. If would be helpful to find the task (or a similar one) that produced the original error. Hint: compare the file data/time of stderr.txt and stderrgfx.txt to correlate events.
Just to make sure: by running only once, you refer to the graphics in screensaver mode, not the manual graphics or the science app, right?
Also, please enable screensaver debugging in BOINC's event log settings.
Oliver
Einstein@Home Project
Graphics from BOINC Manager
)
Graphics from BOINC Manager (by clicking the button) will work always. Just the screensaver fails 99.9% of the time. I got it to show up 2 times, right after changing settings here on the website and synchronizing this with BOINC Manager. But I am not at all sure that this is even related.
The errors in the log were the latest (or only) errors in there. As I said, I did a complete re-install of anything, including deleting all local files in between uninstall and install.
EDIT:
I will enable screensaver logging and get back to you with the information!
EDIT2:
Now I am completly lost. I have changed the logging settings and added screensaver logs. Then I started the manager, waited until the screensaver comes up... it failed. I checked the logs... and there is no log file of today. The latest log there is is the one from the 22nd, yesterday.
So, no new information other than it still does not work and it still always works ok if I click the button.
EDIT3:
Which log should be monitored anyway? In the slot (which one?), the project folder or in the log messages in the BOINC Manager? They all seem to have very different contents... In the Manager there are entries of today, but no error messages or warnings whatsoever... and the other files are not being written at all it seems.
EDIT4:
There is just one task active now. I can still start graphics with the button at any time without any issue. Screensaver logs are enabled. Screensaver still fails and there is nothing in any of the logs at all.
I am about to just let it go, really.
Meldric wrote:changing
)
You're right, it isn't. The screensaver settings we provide here on the website affect the graphics in both, "Show Graphics" and screensaver mode.
The screensaver debug logs should appear in BOINC's Event Log (in the Manager, at least). Too bad it doesn't provide any hints :-/
Honestly, that's probably the wisest thing to do until the related upstream issues are resolved. Apparently you're not the only one. Here's one remarkable quote from BOINC's main author: "the screensaver is a disaster"...
Oliver
Einstein@Home Project
Oliver: I checked memory
)
Oliver:
I checked memory allocation and I have 8 Gb of RAM and when BOINC is running 3 tasks it still has 50% resources reporting. I'm running version 7.16.11 of BOINC. When I start the screen saver by clicking on the "show graphics" button, it does show the statistics and other data for the jobs running. I cleared both stderr.txt, stderrscrgfx.txt and run them, getting the same results with the screen saver cycling between the 3 states. I looked at the error texts to see what was going on and found the following:
stderr.txt
DEPRECATION WARNING: program has invoked obsolete function XLALGetVersionString(). Please see XLALVCSInfoString() for information about a replacement.
Code-version: %% LAL: 6.19.2.1 (CLEAN ed30a8358ee2fa6952b3bd4d99f3f4c6ebc7a5de)
%% LALPulsar: 1.17.1.1 (CLEAN ed30a8358ee2fa6952b3bd4d99f3f4c6ebc7a5de)
%% LALApps: 6.23.0.1 (CLEAN ed30a8358ee2fa6952b3bd4d99f3f4c6ebc7a5de)
stderrscrgfx.txt shows the cycle
11:10:19 (10996): Starting graphics application.
11:10:19 (10996): fullscreen mode requested.
Successfully loaded 'boinc_logo_black.jpg'.
11:11:08 (10996): Close event (mouse move) detected, shutting down.
11:11:08 (10996): Shutting down graphics application.
stderrgfx,txt is blank as well as stderrgui.txt
There is also a stderr.txt in slot\0 that reports:
putenv 'LAL_DEBUG_LEVEL=3'
2021-02-25 03:13:01.6925 (4216) [normal]: This program is published under the GNU General Public License, version 2
2021-02-25 03:13:01.6965 (4216) [normal]: For details see http://einstein.phys.uwm.edu/license.php
2021-02-25 03:13:01.6985 (4216) [normal]: This Einstein@home App was built at: Dec 19 2019 11:51:52
2021-02-25 03:13:01.7015 (4216) [normal]: Start of BOINC application 'projects/einstein.phys.uwm.edu/einstein_O2MD1_2.09_windows_x86_64__GWnew.exe'.
Activated exception handling...
2021-02-25 03:13:01.7085 (4216) [debug]: BSGL output files
2021-02-25 03:13:01.7405 (4216) [debug]: Flags: LAL_DEBUG, OPTIMIZE, HS_OPTIMIZATION, GC_SSE2_OPT, X64, SSE, SSE2, GNUC X86 GNUX86
2021-02-25 03:13:01.7455 (4216) [debug]: Set up communication with graphics process.
DEPRECATION WARNING: program has invoked obsolete function XLALGetVersionString(). Please see XLALVCSInfoString() for information about a replacement.
Code-version: %% LAL: 6.19.2.1 (CLEAN ed30a8358ee2fa6952b3bd4d99f3f4c6ebc7a5de)
%% LALPulsar: 1.17.1.1 (CLEAN ed30a8358ee2fa6952b3bd4d99f3f4c6ebc7a5de)
%% LALApps: 6.23.0.1 (CLEAN ed30a8358ee2fa6952b3bd4d99f3f4c6ebc7a5de)
2021-02-25 03:13:03.5314 (4216) [normal]: Reading input data ... 2021-02-25 03:18:01.3635 (4216) [normal]: Search FstatMethod used: 'ResampGeneric'
2021-02-25 03:18:01.3645 (4216) [normal]: Recalc FstatMethod used: 'DemodSSE'
2021-02-25 03:18:01.3655 (4216) [normal]: SSE2 version is used for the semi-coherent step!
2021-02-25 03:19:17.4792 (4216) [normal]: Number of segments: 22, total number of SFTs in segments: 9902
done.
% --- GPS reference time = 1177806642.5000 , GPS data mid time = 1177806642.5000
2021-02-25 03:19:17.6481 (4216) [normal]: dFreqStack = 7.061150e-007, df1dot = 4.521800e-012, df2dot = 2.284100e-018, df3dot = 0.000000e+000
% --- Setup, N = 22, T = 604800 s, Tobs = 19646545 s, gammaRefine = 37, gamma2Refine = 45, gamma3Refine = 1
DEPRECATION WARNING: program has invoked obsolete function InitDopplerSkyScan(). Please see XLALInitDopplerSkyScan() for information about a replacement.
2021-02-25 03:19:17.6641 (4216) [normal]: INFO: No checkpoint checkpoint.cpt found - starting from scratch
% --- Cpt:0, total:19, sky:1/1, f1dot:1/1
-------------------------------------------------------------------------------------------------------------------
Same deprecation error. It appears that it is looking for a line of code that has been changed. XLALGetVersionString() has been changed to XLALVCSInfoString().
Hope you can make sense of this
Thanks
Bobby
Thanks Bobby,all of that
)
Thanks Bobby,
all of that looks perfectly normal and it didn't reproduce the error you posted earlier. Also, the following shows that the screensaver ran for almost a minute and got shut down normally, due to mouse movement:
What do you mean by "cycle" above? Also, what were your observations of the screensaver's behavior during this test?
Oliver
Einstein@Home Project
Oliver: By cycling I mean
)
Oliver:
By cycling I mean that the screen saver comes on with a message telling me that BOINC has started the screen saver, it then flashes to the statistics screen, which then flashes the screen saver loading the star globe, and it then goes back to the screen saver loading BOINC. I haven't timed it but this cycle will continue until I move the mouse or tap a key. It never does land on the star globe long enough to really load it.
What about the message in the deprecation error? Is that normal?
Bobby
That is basics what happens
)
That is basicly what happens to me. It tries to load the globe again and again and again without ever getting there.
Bobby Conger wrote: What
)
Yes. And that's the science app, not the graphics.
Oliver
Einstein@Home Project
Hello friends of
)
Hello friends of science,
so far I have only been working with “simple” PC builds and found information about the settings relatively quickly in the forum. Now I wanted to integrate a second graphics card and run both in parallel.
I activated multiGPU via cc_config as follows.
<cc_config>
<options>
<use_all_gpus>1</use_all_gpus>
</options>
</cc_config>
Because my 1st GPU (RTX 4080) has enough VRAM, I have set several WU per GPU via app_config.
<app_config>
<app>
<name>einstein_O3AS</name>
<gpu_versions>
<gpu_usage>0.25</gpu_usage>
<cpu_usage>1</cpu_usage>
</gpu_versions>
</app>
</app_config>
My question:
I want the 1st GPU (RTX 4080) to calculate 4 WUs at the same time and the 2nd GPU (RTX 2070 Super) to calculate 3 WUs. Because the 2070 has too less VRAM and can only load 3 WUs.
How do I have to set this up?
Regards
Marcelo