Just looked at my logs and I've been getting this error apparently for about ~7 hours as of writing this post. My client has been spamming the server with failed workunits.

BURP | Output file ses0000002523frm0000000192prt00004_2_0 for task ses0000002523frm0000000192prt00004_2 absent

Every BURP unit does it. I tried resetting the project as that has fixed prior project screwups. Unfortunately it didn't help this time.

Bailing out for now.

Hm, in another thread someone also has problems...
Still wondering - since I didn't get any errors yet with any of the sessions which are currently running, except for some inconclusives in the last hours - so it can't be a complete fault at the session settings.

BURP | Output file ses0000002523frm0000000192prt00004_2_0 for task ses0000002523frm0000000192prt00004_2 absent

Well, this messsage doesn't say anything about the real problem, and as far as your clients are hidden, none can look into your logs to see if something is indicating what could be causing this...

---

Life is Science, and Science rules. To the universe and beyond
Proud member of BOINC@Heidelberg
My BOINC-Stats

Simply looking at the logs of some of the latest units is enough to verify this issue really. Look at the amount of errors here:
https://burp.renderfarming.net/workunit.php?wuid=2363082
https://burp.renderfarming.net/workunit.php?wuid=2363050
https://burp.renderfarming.net/workunit.php?wuid=2363030

Something has changed on the BURP side of things.

Something has changed on the BURP side of things.

And what do you think could've changed?
Janus didn't announce anything and the app is still the version deployed from October 22nd.
As far as I see from the packets you picked there it's a bit conspicuous to me that all errored WUs were on Windows 8 machines. I don't know if there's a problem with OS compatibility and if this happened before but if that's the case there needs to be done something about it.

---

Life is Science, and Science rules. To the universe and beyond
Proud member of BOINC@Heidelberg
My BOINC-Stats

I do not believe this specific error has happened before. I also don't think it's a Windows issue as it started before I had this months patches.

My guess would be that something was changed with the way WU are created during maintenance.

Recently there has been a higher than normal number of results returned with a runtime of <30 sec and the WU error log message of

---------------------------
Exception caught: Worker application apparently died prematurely
Status: -9
---------------------------

(Hint: you will see this in the result section of the website at the very bottom of the output. Oh and by the way, this is always how Glue3 presents errors - if you find a section at the bottom with an error message between two dashed lines you can usually find the issue by tracing back a few lines above them. The stuff in the BOINC log is mostly useless as it is way too general like "output absent" or "-9")

So far I haven't been able to catch one do it on the test systems but it seems related to scene loading.

@funkydude: Have you rebooted since this started happening? The reason I ask is that your system used to be working just fine and then started spewing errors all of a sudden. If not, then maybe we are on to something.

Just tried rebooting, but it didn't help :(

Just guessing, could this be the culprit?

http://www.forbes.com/sites/jasonevangelho/2014/12/13/new-windows-7-patch-is-effectively-malware-disables-graphics-driver-updates-and-windows-defender/

No. Windows 8 thankfully.

Windows 8 thankfully.

That's a new one on me.

---

Click here to see My Detailed BOINC Stats

So what's going on with this? Like previously stated, I'm not the only one experiencing this problem. Are we all relegated to abandoning this project?

No. Windows 8 thankfully.

Is that 8 or 8.1? It seems one of the things that the machines doing this have in common is Windows 8.1

No. Windows 8 thankfully.

Is that 8 or 8.1? It seems one of the things that the machines doing this have in common is Windows 8.1

8.1

I just tried to opt in again. I downloaded a 2547 unit and so far it appears to be working.

Constant errors again on 2522. I wish I could blacklist it because after I FINALLY received a 2549 unit, it works fine. So I either spam the server with errors or bail out again.

It seems there is something seriously wrong with 2522 and 2523, both by user "Ben".

Roger that. We are looking at a new client release to fix an issue with scene loading for cycles renders in >=Win 8.1. It will be pushed to the farm shortly after 2518 finishes (That is a session number not a year).

Roger that. We are looking at a new client release to fix an issue with scene loading for cycles renders in >=Win 8.1. It will be pushed to the farm shortly after 2518 finishes (That is a session number not a year).

If 2.73 is on the verge of release it might be best to wait for that, unless you mean this is a BURP specific issue.

Did you suspend this project? Either that or I'm getting really lucky with the WU's I'm getting. Saving me a lot of time manually aborting units! :)