These sterr_outs from your more recent 20 credit workunits look more normal than the original ones. The original ones appeared to have at least a few full runs under one file if I remember correctly which was quite odd.

I get these from time to time as well, the "hybrid" or "hyb" tasks. I looked through my results and I only have received one that still resides in the database, and it completed normally. Some of them complete normally, some of them error out. The units that error out have been set to give you 20 instead of 0.

---

I have had 2 of them lately, more than 25000 seconds for 20 credits.
If it are the hyb_a*_bench_* than I have 4 more currently crunching (2.5 hours gone, 8 to go).
I have also ActCys_ estimated more than 11 hours.
This is a bad credit project and the processor has to work here hard.
However as said earlier I stick with it.

---

Greetings,
TJ.

I have had 2 of them lately, more than 25000 seconds for 20 credits.
If it are the hyb_a*_bench_* than I have 4 more currently crunching (2.5 hours gone, 8 to go).
I have also ActCys_ estimated more than 11 hours.
This is a bad credit project and the processor has to work here hard.
However as said earlier I stick with it.

They will get it fixed, it is imperative to the science circles to be precise. I'm sure they are working as quickly and as diligently as possible to correct issues with their coding or incompatibilities problems. Rosetta will always have 100% of my cores. The breakthrough's in disease's alone, make up for waiting for them to work out some of their kinks. I don't abort even if I suspect a WU has failed. If anything so they can at least have a chance to try an extrapolate as much data as possible from the failed units so hopefully they are able to figure out what went wrong in the first place faster.

Stay positive, you wouldn't here in the first place if you didn't think it was worth while research and everything you donate whether credited or not helps the project.

That being said provide as much information as possible to help solve the issue. Such as Client versions for Boinc and O/S system for the PC MAC or Linux system that you are operating.

Cheers

---

I have had 2 of them lately, more than 25000 seconds for 20 credits.
If it are the hyb_a*_bench_* than I have 4 more currently crunching (2.5 hours gone, 8 to go).
I have also ActCys_ estimated more than 11 hours.
This is a bad credit project and the processor has to work here hard.
However as said earlier I stick with it.

They will get it fixed, it is imperative to the science circles to be precise. I'm sure they are working as quickly and as diligently as possible to correct issues with their coding or incompatibilities problems. Rosetta will always have 100% of my cores. The breakthrough's in disease's alone, make up for waiting for them to work out some of their kinks. I don't abort even if I suspect a WU has failed. If anything so they can at least have a chance to try an extrapolate as much data as possible from the failed units so hopefully they are able to figure out what went wrong in the first place faster.

Stay positive, you wouldn't here in the first place if you didn't think it was worth while research and everything you donate whether credited or not helps the project.

That being said provide as much information as possible to help solve the issue. Such as Client versions for Boinc and O/S system for the PC MAC or Linux system that you are operating.

Cheers

Well then you have to read way more posts here. The change that something will be resolved quickly or that there will be any communication is about issues is very very bad. They are already way behind with the server software. It is outdated for years and they don't even care to update it until it is broken.
They have lost a lot of crunchers with this behavior, but they don't see it. However I think this science is very useful so I stick with this odd project.

---

Greetings,
TJ.

I have had 2 of them lately, more than 25000 seconds for 20 credits.
If it are the hyb_a*_bench_* than I have 4 more currently crunching (2.5 hours gone, 8 to go).
I have also ActCys_ estimated more than 11 hours.
This is a bad credit project and the processor has to work here hard.
However as said earlier I stick with it.

They will get it fixed, it is imperative to the science circles to be precise. I'm sure they are working as quickly and as diligently as possible to correct issues with their coding or incompatibilities problems. Rosetta will always have 100% of my cores. The breakthrough's in disease's alone, make up for waiting for them to work out some of their kinks. I don't abort even if I suspect a WU has failed. If anything so they can at least have a chance to try an extrapolate as much data as possible from the failed units so hopefully they are able to figure out what went wrong in the first place faster.

Stay positive, you wouldn't here in the first place if you didn't think it was worth while research and everything you donate whether credited or not helps the project.

That being said provide as much information as possible to help solve the issue. Such as Client versions for Boinc and O/S system for the PC MAC or Linux system that you are operating.

Cheers

Well then you have to read way more posts here. The change that something will be resolved quickly or that there will be any communication is about issues is very very bad. They are already way behind with the server software. It is outdated for years and they don't even care to update it until it is broken.
They have lost a lot of crunchers with this behavior, but they don't see it. However I think this science is very useful so I stick with this odd project.

I noted the amount of requests for investigation into various bugs with crediting. Which is merely bragging rights for most anyway. I guess what I was trying to get across was that the science is well worth the effort. It would be a nice idea to get more then just communication from the project team. They have ton's of people with coding knowledge contributing to their project I would assume. If they are lacking in hardware I'm sure there is a good reason for it. Server pricing can range widely depending on what you wish them to do. 20 grand or more, which is why a lot of companies lease the server instead of buying it. Perhaps a meter on the home page listing a donation meter towards upgrading said hardware to rule out these problems.

Since they are a non profit organization I would imagine it is in their best interests to run some of the equipment until it does die. In the IT world if it's not broken don't fix it. Mainly because of the total cost of ownership tends to go up and the equipment will breakdown more rapidly in some cases. Which means more breakdowns more often. You seem to have some insight TJ into what servers they are using along with coding I assume from your previous statements. Could you prey tell me what they are using that is so obviously outdated? Perhaps someone might be able to offer some support free of charge from the community.


Also since we are in the right section for this. I noticed this on one of my WU's after it completed.

<core_client_version>7.0.64</core_client_version>
<![CDATA[
<stderr_txt>
[2013- 7-10 15:49: 4:] :: BOINC:: Initializing ... ok.
[2013- 7-10 15:49: 4:] :: BOINC :: boinc_init()
BOINC:: Setting up shared resources ... ok.
BOINC:: Setting up semaphores ... ok.
BOINC:: Updating status ... ok.
BOINC:: Registering timer callback... ok.
BOINC:: Worker initialized successfully.
Registering options..
Registered extra options.
Initializing broker options ...
Registered extra options.
Initializing core...
Initializing options.... ok
Options::initialize()
Options::adding_options()
Options::initialize() Check specs.
Options::initialize() End reached
Loaded options.... ok
Processed options.... ok
Initializing random generators... ok
Initialization complete.
Initializing options.... ok
Options::initialize()
Options::adding_options()
Options::initialize() Check specs.
Options::initialize() End reached
Loaded options.... ok
Processed options.... ok
Initializing random generators... ok
Initialization complete.
Setting WU description ...
Unpacking zip data: ../../projects/boinc.bakerlab.org_rosetta/minirosetta_database_rev54943.zip
Unpacking WU data ...
Unpacking data: ../../projects/boinc.bakerlab.org_rosetta/fold_and_dock_frxtrimer2_dock2_10135_data.zip
Setting database description ...
Setting up checkpointing ...
Setting up graphics native ...
BOINC:: Worker startup.
Starting watchdog...
Watchdog active.
# cpu_run_time_pref: 86400
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
======================================================
DONE :: 99 starting structures 13359.7 cpu seconds
This process generated 99 decoys from 99 attempts
======================================================
BOINC :: WS_max 4.55877e+008

BOINC :: Watchdog shutting down...
BOINC :: BOINC support services shutting down cleanly ...
called boinc_finish

</stderr_txt>
]]>

---

I take it no one else has any insight into what the above bold phrase is referring to correct?

hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???

---

I take it no one else has any insight into what the above bold phrase is referring to correct?

hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???
hey is this the right thing to be doing???

It's bizarre, I'll give you that.

cryo_vp26_aligned_tmpl_helix3* WUs have this issue too. They were downloaded recently. 20.0 credits for each of them.

I joined Rosetta yesterday and have already got two of those out of 26 tasks so far. :-( I found this thread googling the warning message.

See e.g. ac_t20s_reg_shift_4.1A_1pma_fit_INPUT_A0041-A0045_-1_SAVE_ALL_OUT_IGNORE_THE_REST_100053_351

The other one has almost the same name. I notice in the output also a:

SIGSEGV: segmentation violation

So something is very wrong. I have another ac_t20s task running for 4:29 at this moment which I suspect is suffering the same problem.

I'm running BOINC 7.0.65 on Linux Mint 14.

Another observation: the 3 currently running ac_t20s task I have are all lacking a default.out file in their slots subdirectory.

- Bjorn

kinda like working for free isnt it.granted it takes me a 1/4 of the time it takes you,for the same credit.i remember now,why i quit running this project in the first place.not enough credit for the run time.gonna finish what i got and its adious amigos.