PrimeGrid
Please visit donation page to help the project cover running costs for this month

Toggle Menu

Join PrimeGrid

Returning Participants

Community

Leader Boards

Results

Other

drummers-lowrise

Advanced search

Message boards : Problems and Help : "Can't acquire lockfile" error

Author Message
Ravi Fernando
Send message
Joined: 21 Mar 19
Posts: 14
ID: 1108183
Credit: 2,367,442
RAC: 18,430
321 LLR Silver: Earned 100,000 credits (100,541)PPS LLR Bronze: Earned 10,000 credits (90,867)SoB LLR Silver: Earned 100,000 credits (183,524)SGS LLR Bronze: Earned 10,000 credits (10,457)TRP LLR Bronze: Earned 10,000 credits (57,952)321 Sieve Amethyst: Earned 1,000,000 credits (1,845,512)AP 26/27 Bronze: Earned 10,000 credits (72,774)
Message 129178 - Posted: 6 May 2019 | 7:05:08 UTC

Today I noticed that two of my 321 Sieve tasks finished with computation errors. The stderr outputs say "finish file present too long" at the top, and they are full of lines saying "Can't acquire lockfile (-154) - waiting 35s". (Links: http://www.primegrid.com/result.php?resultid=998299709, http://www.primegrid.com/result.php?resultid=998302376.) Does anyone know what this means, or whether there's anything I should do to prevent it in the future?

A little context: the same thing happened about three weeks ago, also on two concurrently running 321 Sieve tasks. I was also running two SoB tasks at that time, and fortunately those completed and were validated. (Although I just noticed that they have some similar lines in their stderr output; e.g. see http://www.primegrid.com/result.php?resultid=990229112.) As far as I've noticed, these four 321 Sieves are the only failed computations I've returned to date.

dukebg
Volunteer tester
Avatar
Send message
Joined: 21 Nov 17
Posts: 224
ID: 950482
Credit: 22,083,013
RAC: 764
Found 1 prime in the 2018 Tour de Primes321 LLR Gold: Earned 500,000 credits (506,942)Cullen LLR Gold: Earned 500,000 credits (500,523)ESP LLR Gold: Earned 500,000 credits (655,642)Generalized Cullen/Woodall LLR Gold: Earned 500,000 credits (539,100)PPS LLR Gold: Earned 500,000 credits (688,232)PSP LLR Gold: Earned 500,000 credits (561,629)SoB LLR Ruby: Earned 2,000,000 credits (3,659,676)SR5 LLR Gold: Earned 500,000 credits (505,810)SGS LLR Gold: Earned 500,000 credits (506,024)TRP LLR Gold: Earned 500,000 credits (963,625)Woodall LLR Gold: Earned 500,000 credits (506,044)321 Sieve Gold: Earned 500,000 credits (511,694)Generalized Cullen/Woodall Sieve Gold: Earned 500,000 credits (549,916)PPS Sieve Gold: Earned 500,000 credits (701,168)AP 26/27 Gold: Earned 500,000 credits (525,590)GFN Turquoise: Earned 5,000,000 credits (9,675,760)PSA Gold: Earned 500,000 credits (525,639)
Message 129179 - Posted: 6 May 2019 | 7:22:51 UTC

You don't have to worry, it's a rare BOINC bug (but no matter how rare, it does happen time after time to people based on how many people run how many tasks) where in some race conditions there would be a conflict between trying to start a task and a completed task being reported in the same slot (file system folder).

There's a better description of this bug somewhere on forums... Stream definitely posted about it somewhere. And to assure you, "finish file present too long" happens in other BOINC projects too.

Either way, I'm pretty confident you don't have to worry.

JimBProject donor
Volunteer moderator
Project administrator
Project developer
Send message
Joined: 4 Aug 11
Posts: 868
ID: 107307
Credit: 829,643,365
RAC: 56,286
321 LLR Ruby: Earned 2,000,000 credits (2,071,006)Cullen LLR Ruby: Earned 2,000,000 credits (4,122,766)ESP LLR Turquoise: Earned 5,000,000 credits (5,014,632)Generalized Cullen/Woodall LLR Ruby: Earned 2,000,000 credits (2,589,971)PPS LLR Ruby: Earned 2,000,000 credits (2,102,793)PSP LLR Turquoise: Earned 5,000,000 credits (5,013,650)SoB LLR Sapphire: Earned 20,000,000 credits (35,252,137)SR5 LLR Jade: Earned 10,000,000 credits (10,987,079)SGS LLR Ruby: Earned 2,000,000 credits (2,069,865)TRP LLR Ruby: Earned 2,000,000 credits (2,125,793)Woodall LLR Ruby: Earned 2,000,000 credits (2,595,228)321 Sieve Turquoise: Earned 5,000,000 credits (5,000,447)Cullen/Woodall Sieve (suspended) Ruby: Earned 2,000,000 credits (4,002,919)Generalized Cullen/Woodall Sieve Sapphire: Earned 20,000,000 credits (20,005,451)PPS Sieve Emerald: Earned 50,000,000 credits (50,809,179)Sierpinski (ESP/PSP/SoB) Sieve (suspended) Ruby: Earned 2,000,000 credits (2,341,676)TRP Sieve (suspended) Ruby: Earned 2,000,000 credits (2,070,804)AP 26/27 Jade: Earned 10,000,000 credits (10,592,660)GFN Sapphire: Earned 20,000,000 credits (31,491,236)PSA Double Gold: Earned 500,000,000 credits (629,384,073)
Message 129182 - Posted: 6 May 2019 | 11:02:23 UTC
Last modified: 6 May 2019 | 17:04:04 UTC

I thought maybe this should be fixed by one of our scripts that runs hourly. But your jobs ended with an error code, in this case "aborted by client". Such jobs can't be fixed because we have to assume the program ended abnormally or was never run to start with. It's different with LLR, GFN and AP27 jobs, because they produce a residue rather than a (frequently empty) list of factors.

Possible causes:

1) Maybe you had two sieve jobs running at the same time in the same BOINC slot directory.

2) When a job ended the slot directory did not get emptied like it's supposed to.

3) Possibly you had more than one copy of BOINC running simultaneously, though that's not easy to do.

Post to thread

Message boards : Problems and Help : "Can't acquire lockfile" error

[Return to PrimeGrid main page]
DNS Powered by DNSEXIT.COM
Copyright © 2005 - 2019 Rytis Slatkevičius (contact) and PrimeGrid community. Server load 1.00, 1.31, 1.96
Generated 21 Jul 2019 | 0:57:36 UTC