Figures. I just approved the internet access, and it immediately crashes with the 0xC0000005 fault that's going around. Oh, well.

454295

...why a science app would be directly using the internet connection instead of letting BOINC handle the file transfers...

See discussion here: https://boinc.bakerlab.org/forum_thread.php?id=1755&nowrap=true#32219

I could of course approve the app for internet access, but that won't work long term, since soon enough it'll be upgraded to rosetta_beta_5.51... and the game will start all over again.

Yep. The good news, if you want to call it that, is that the task had failed prior to the firewall challenge. So, the application not being approved in the firewall is not what caused it to fail.

---

Oh, I see. What a pain. My firewall doesn't support app name wildcards, and there's no way to proactively say "any app that wants to connect to x.y.z.t is allowed, even if you've never heard of it before." The app approval seems to be implemented as a separate layer; first the app is checked to see if it's allowed to use the internet at all, then if so, the packets are run through the packet-level rules as they go out.

It looks like I'm stuck with losing many hours of CPU time the first time any new version of the science app aborts, along with it stuffing the error log and approval list full of spam. Argh.

---

I've contacted Vatsan -- hopefully he'll reply about what's wrong with these workunits tomorrow.
In the meanwhile, application is updated to 5.51! Not many changes this time, just a very slight fix to allow us to send out symmettric docking work units when we don't really know the native structure.

400678

400776

400748

On the same workunits that windows users are getting "exit code -1073741819 (0xc0000005)" and "- Unhandled Exception Record - Reason: Access Violation (0xc0000005)" I'm getting on Linux "process exited with code 131 (0x83)" and a segmentation violation:

ERROR:: Unable to determine sequence length from pdb file
# random seed: 2719130
SIGSEGV: segmentation violation
Stack trace (13 frames):
[0x8b95623]
[0x8bb146c]
[0xffffe420]
[0x8857337]
[0x861bad6]
[0x8620366]
[0x86222e3]
[0x8973172]
[0x8529c73]
[0x8641c32]
[0x8641cdc]
[0x8c10a94]
[0x8048111]

Exiting...

---

Faulty WU, exit code 131

https://ralph.bakerlab.org/workunit.php?wuid=400654

---

WU : 40678, 40776 etc I am sorry the WUs crashed. I tested the jobs on my desktop before sending it out to Ralph. There was a small error in renumbering the sequence number in the PDB structure. It ran on my desktop despite this discrepancy. I've fixed it and resubmitted the jobs and they ran cleanly. Sorry for the inconvenience.

Very short runtime in 5.51 for an abinitio RNA WU that generated 0 decoys from 0 attempts, followed by a validation error

https://ralph.bakerlab.org/result.php?resultid=456095

This result has been running for close to 6 hours, is still racking up cpu time and says it's at 1%. My preference settings are for 4 hours. I just suspended it and I have to reboot for a Windows Update. If it doesn't seem more sane after that I'll abort it, unless advised to let it run.

No, it looks like a lot of users have not been able to return results for the WU due to timeouts. I'm sending some out again that require less computation, let's see how those go.

This result has been running for close to 6 hours, is still racking up cpu time and says it's at 1%. My preference settings are for 4 hours. I just suspended it and I have to reboot for a Windows Update. If it doesn't seem more sane after that I'll abort it, unless advised to let it run.

---

This workunit has been running for three hours and is stil initializing. It seems to be running fine with almost 5 million steps calculated and moving graphs of folding rna. But I am worried about the lack of progress.

Jorn

---

You might wanna check this wu type: 1xjr__BOINC_INCREASE_CYCLES_RNA_ABINITIO-1xjr_-_1843_13_0. It might generate an infinite loop...I mean it runs for over 1 hour and a half (in my prefs I've selected 1 h target time), and it's at step no. 1700000 while the stage still states "initializing"....I'm gonna abort it now.

Thanks for posting. There was a definite problem with an early round of these workunits. Now, most of these workunits have now been returning fine, but I'll make sure.

[BTW, I'm fixing the "Initializing..." bug, and it will go out on the next application update.]

You might wanna check this wu type: 1xjr__BOINC_INCREASE_CYCLES_RNA_ABINITIO-1xjr_-_1843_13_0. It might generate an infinite loop...I mean it runs for over 1 hour and a half (in my prefs I've selected 1 h target time), and it's at step no. 1700000 while the stage still states "initializing"....I'm gonna abort it now.

---