Errors: Gravitational Wave search O3 All-Sky #1 v1.01 () x86_64-pc-linux-gnu

Laurent_L
Laurent_L
Joined: 1 May 22
Posts: 2
Credit: 1952119
RAC: 0
Topic 227553

Hello,

I see 63 compute errors today, only for Gravitional Wave search.

The same errors below occurs everywhere:

einstein_O3AS_1.01_x86_64-pc-linux-gnu__GW-opencl-nvidia: unrecognized option `--device'

Usage: einstein_O3AS_1.01_x86_64-pc-linux-gnu__GW-opencl-nvidia [-h|--help] [-v|--version] [@<config-file>] [--log] [--semiCohToplist] [--DataFiles1] [--IFOs] [--skyRegion] [--numSkyPartitions] [--partitionIndex] [--skyGridFile] [--dAlpha] [--dDelta] [-f|--Freq] [--dFreq] [-b|--FreqBand] [--f1dot] [--df1dot] [--f1dotBand] [--f2dot] [--df2dot] [--f2dotBand] [--f3dot] [--df3dot] [--f3dotBand] [--peakThrF] [-m|--mismatch1] [--gridType1] [--metricType1] [-g|--gammaRefine] [-G|--gamma2Refine] [-o|--fnameout] [--fnameChkPoint] [-n|--nCand1] [--printCand1] [--refTime] [--ephemEarth] [--ephemSun] [--minStartTime1] [--maxStartTime1] [--printFstat1] [--assumeSqrtSX] [--nStacksMax] [-T|--tStack] [--segmentList] [--recalcToplistStats] [--loudestSegOutput] [--writeLeanerOutput] [--tlCompartments] [--computeBSGL] [--Fstar0sc] [--oLGX] [--getMaxFperSeg] [--SortToplist] [--FstatMethod] [--FstatMethodRecalc] [--injectionSources] [--injectSqrtSX] [--timestampsFiles] [--Tsft] [--useGPUSemiCoh] [--GPUDevice]

2022-05-18 18:38:29.3150 (33927) [CRITICAL]: ERROR: MAIN() returned with error '1'

There were no errors before today.

Any advice welcome.

Regards

 

Gary Roberts
Gary Roberts
Moderator
Joined: 9 Feb 05
Posts: 5877
Credit: 118695106967
RAC: 19801506

Hi, welcome to

Hi, welcome to Einstein@Home.

Your computers are 'hidden' (which is a default setting) so it would be difficult for anybody to offer useful advice.

You can allow others to see non-sensitive information about your hardware and the tasks it is working on by going to your account -> preferences -> privacy and allowing your computers to be 'shown' on the website.  That way, someone wishing to help will be able to see the failed tasks and their stderr outputs and this may give a much better idea of what is causing the problem.

Cheers,
Gary.

Laurent_L
Laurent_L
Joined: 1 May 22
Posts: 2
Credit: 1952119
RAC: 0

Hi Gary, Thanks for your

Hi Gary,

Thanks for your reply, my computers are now shown.

I took some times to investigate.

clinfo failed to find my GPU (it worked fine before this day).

The issue was fixed, at least temporarily, with a reboot.

I suspect there is a bug with Ubuntu's built-in Nvidia driver.

By the way, the GPU is rather old but a recent one won't fit in a Small Form Factor computer case.

Regards,

 

Gary Roberts
Gary Roberts
Moderator
Joined: 9 Feb 05
Posts: 5877
Credit: 118695106967
RAC: 19801506

Laurent_L wrote:.... my

Laurent_L wrote:
.... my computers are now shown.

Thanks.

I took a look at your O3AS GPU tasks.  The first one showing an error had the real error message just a few lines before the block you posted.  It showed:-

[ERROR] Couldn't get OpenCL device from BOINC (-1)!

What you had highlighted as the error message was likely just information that was triggered by no OpenCL information coming from BOINC.  Real errors tend to be flagged with the [ERROR] label so that's what I always try to find.  Since you had been crunching up to that point something weird must have happened to cause your OpenCL libraries not to be detected after that.  If the reboot fixed it, you should be OK, hopefully.

One other point to be aware of.  The O3AS tasks tend to use quite a lot of memory so you may find insufficient memory errors with the 2GB amount that your GPU has.  It used to be that 2GB wasn't really enough some time ago but maybe that has been changed with more recent work.

Cheers,
Gary.

Keith Myers
Keith Myers
Joined: 11 Feb 11
Posts: 5044
Credit: 19044081890
RAC: 6568121

The most common reason for

The most common reason for this type of error is that Ubuntu has a tendency to pull the Nvidia drivers out from underneath running tasks because of an automatic Nvidia driver update for security reasons.

Two of my teammates were bitten just so a day ago by this cause.

 

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.