Now WCG is down for 2 months, I moved back to Rosetta.

A lot of VirtualBox tasks get stuck for days and don't seem end. They expire on the server side, the work is lost and no points.
Don't want to babysit my computers...

Is there any fix for that? Other option is to disable Virtual Box work.

A lot of VirtualBox tasks get stuck for days and don't seem end. They expire on the server side, the work is lost and no points.
Don't want to babysit my computers...

Is there any fix for that? Other option is to disable Virtual Box work.

They are easier to spot if you install BoincTasks. It shows the CPU useage, and when you see it in red that means the CPU is not doing much.
You can delete them in the first five minutes if you catch them.

Otherwise, the project has to fix it, if there is anyone at Rosetta at all.

(It would be nice if some software expert could automate the process.)

---

https://efmer.com/boinctasks/download-boinctasks/

A lot of VirtualBox tasks get stuck for days and don't seem end. They expire on the server side, the work is lost and no points.
Don't want to babysit my computers...

Is there any fix for that? Other option is to disable Virtual Box work.

They are easier to spot if you install BoincTasks. It shows the CPU useage, and when you see it in red that means the CPU is not doing much.
You can delete them in the first five minutes if you catch them.

Otherwise, the project has to fix it, if there is anyone at Rosetta at all.

(It would be nice if some software expert could automate the process.)

Thanks!

I'm used to look at my rigs once a week, sometimes 2 times in a month... Before the VB work, I ran Rosetta for a year without many issues.

I guess they'll have to fix it while I focus on non-VB work or another project....

A lot of VirtualBox tasks get stuck for days and don't seem end. They expire on the server side, the work is lost and no points.
Don't want to babysit my computers...

Is there any fix for that? Other option is to disable Virtual Box work.

They are easier to spot if you install BoincTasks. It shows the CPU useage, and when you see it in red that means the CPU is not doing much.
You can delete them in the first five minutes if you catch them.

Otherwise, the project has to fix it, if there is anyone at Rosetta at all.

(It would be nice if some software expert could automate the process.)

Thanks!

I'm used to look at my rigs once a week, sometimes 2 times in a month... Before the VB work, I ran Rosetta for a year without many issues.

I guess they'll have to fix it while I focus on non-VB work or another project....

Check your Vbox version and extensions version. You may need to update to get stable.

I forgot about WCG going down. I guess I need to disable that project for now.
You can try another Vbox project, I can't get it to be stable on my rig for some reason, others have lots of success. Look up QuChemPedia.

A lot of VirtualBox tasks get stuck for days and don't seem end. They expire on the server side, the work is lost and no points.
Don't want to babysit my computers...

Is there any fix for that? Other option is to disable Virtual Box work.

They are easier to spot if you install BoincTasks. It shows the CPU useage, and when you see it in red that means the CPU is not doing much.
You can delete them in the first five minutes if you catch them.

Otherwise, the project has to fix it, if there is anyone at Rosetta at all.

(It would be nice if some software expert could automate the process.)

Thanks!

I'm used to look at my rigs once a week, sometimes 2 times in a month... Before the VB work, I ran Rosetta for a year without many issues.

I guess they'll have to fix it while I focus on non-VB work or another project....

Check your Vbox version and extensions version. You may need to update to get stable.

I forgot about WCG going down. I guess I need to disable that project for now.
You can try another Vbox project, I can't get it to be stable on my rig for some reason, others have lots of success. Look up QuChemPedia.

I turned of VB work for now, it's not worth it. Just had to abort another 22 units that got stuck, waste of CPU-cycles and no points.
Will start looking for another project in the coming days or just shut them down the machines until WCG is back.

Another batch of work released, and only some of these error out straight away. Not great, but still better than all of them doing it.

---

Grant
Darwin NT

5 4.20 tasks running, two failed immediately, one rosetta python waiting to run.
Tullio

---

Since 2 days I have tried Python on several of my machines, the success is modest :-(
Too many tasks are still faulty (e.g. keeping running, but not using CPU, which is a waste).
Since I cannot, as someone else wrote above, babysit my computers just to find out whether a newly started Python task is okay or not, I will abandon Rosetta for the time being. Which is too bad, but I have no other choice :-(

You disable VirtualBox work on the details page of every one of your devices.

---

Another batch of work released, and only some of these error out straight away. Not great, but still better than all of them doing it.

+1
Seems that "h3_3stub" wus have problems

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x00007FF767908316 read attempt to address 0xFFFFFFFF

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x00007FF76B0A9D88

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x0000000000000000

Also these wus are NOT tested on Ralph

---

Some PcrV8MER wus crashed too.

BlueTooth76 wrote:

A lot of VirtualBox tasks get stuck for days and don't seem end. They expire on the server side, the work is lost and no points.
Don't want to babysit my computers...

Is there any fix for that? Other option is to disable Virtual Box work.

There is no fix, but a workaround. See thread "Summary of issues with VirtualBox tasks", message 104802.

Rosetta has always been an experimental project imo.
Asking questions that have never been asked before, using tasks that have never been written before, with parameters whose limits may not be entirely obvious from the outset.
So if things go wrong, it should hardly be a surprise to anyone and no-one should get themselves worked up about it, especially when failures are a bigger problem for the project than they are for any one of us.
And that's the case here. How they chose to solve the problem is down to them, not us. Because they <can't> solve it and only users can in this instance.
Same as it ever was.

This is cutting edge science. But... they usually use Ralph first to test their ideas. This time they didn't. Such is life at the 'new' RAH.

It should, you're right, but it's never really worked. I've never bothered with Ralph.

Some people take the view there's no such thing as betatest software - you only need to look at the assurances you get from finished product, no guarantee it'll do what it's claimed to do.
It makes sense not to have any sense of entitlement as to the reliability of anything we get issued. That approach certainly saves time.

If we didn't have perpetual indignance on these message boards, the traffic would certainly be a lot less. From some accounts a lot more than others.

---

This is cutting edge science. But...they usually use Ralph first to test their ideas. This time they didn't. Such is life at the 'new' RAH.

I participate also to Ralph and it's "not a problem to have problems".
But here in Rosetta i would like a stable and tested work

---

If we didn't have perpetual indignance on these message boards, the traffic would certainly be a lot less. From some accounts a lot more than others.

I don't know if you're referring to me, but it's not important.
I have not a "perpetual indignance", often i write about science, about new languages or cpu/gpu features, etc.
A request, occasionally, of explanations i think it's not "indignance".

About "message board traffic" i'm agree with you: admins are vanished :-P

---

When i changed target cpu time from 1d12h to 2h and updated project in boinc manager workunits that were in progress at 7 hours didn't change their target cpu time to 2 hours and didn't finish.

When i changed target cpu time from 1d12h to 2h and updated project in boinc manager workunits that were in progress at 7 hours didn't change their target cpu time to 2 hours and didn't finish.

I recommend stopping them with LAIM off or exit BOINC ticking the box where it says "stop all applications".

---

Now WCG is down for 2 months, I moved back to Rosetta.

A lot of VirtualBox tasks get stuck for days and don't seem end. They expire on the server side, the work is lost and no points.
Don't want to babysit my computers...

Is there any fix for that? Other option is to disable Virtual Box work.

Which Vbox versions have you been using?
What other Vbox projects are you running?
Which computer are you referring to?
What is the load on your system?
How much memory is being used in terms of %? Do you get any error messages?
Do they go into "waiting to run" status a lot or are there any "need more memory" errors?
Do your machines run 24/7?
If not, before you close BOINC, do you suspend your work (and is the keep in memory option checked?) and then use the shut down client option before you exit?

All these things can be a factor.

This is cutting edge science. But...they usually use Ralph first to test their ideas. This time they didn't. Such is life at the 'new' RAH.

I participate also to Ralph and it's "not a problem to have problems".
But here in Rosetta i would like a stable and tested work

Rosetta is supposed to be stable and tested tasks with only minor errors that can be corrected quickly upon notification. That a team member just dumped the tasks on Rosetta and did not respond to any messages, shows the lack of commitment from the team towards their non neural network base.