I have tried to download and run climateprediction a few times on my Linux machine (redhat). It downloads everything fine, but never runs. It tells me \"Model hasn\'t started, please wait\".
Hours later, still nothing.
My work tab says its running, but no cpu total.
I have uninstalled everything and reinstalled three different times over the last two weeks, with the same result.
SETI works well, but have swithched to climateprediction without luck.
Any suggestions? I am using BOINC 5.2.13
It just won\'t start running!

David

---

As an additional debugging tool, I reran boinc. In my terminal window, I get the following:


Created shared memory region key = 72665 of size 569976 bytes
.so shmem return code = 0
Copying files for startup...
In pre_initialise_phase (part 1 of 3)
In initialise_phase (part 2 of 3)
In startup_phase (part 3 of 3)
Starting model ID sulphur_h067_000793375 Phase 1
Getting pthread attributes - retval=0
Setting pthread size (66560000 bytes) - retval=22
Waiting for model startup, this may take a minute...
Model timeout at 180.00 seconds
Preparing for restart...
Rewinding a model-day...
Starting model ID sulphur_h067_000793375 Phase 1
Getting pthread attributes - retval=0
Setting pthread size (66560000 bytes) - retval=22
Waiting for model startup, this may take a minute...



Hours later, nothing else happens. Does this help anybody debug my problem?
Thanks

---

I just did a forum search for pthread. It looks like your post is the only one that\'s found. This must be a new error. Hopefully someone more fluent in Linux technicalities will come along and help figure this out.

I think there may be a clue in this line:
> Rewinding a model-day...

This usually means that the program has a problem, and is rewinding to a previous calcultion point to try again.
Except that there isn\'t one, because the model has only just started.

All of your many attempts have failed with an unknown error.
And I seem to remember Thyme Lawn posting that the error \'161\' shown on them just means that when BOINC tried to upload the failure data to the server, there weren\'t any files to upload.
Which brings us back to the usual questions about stability and software conflicts.
And I don\'t know enough about Linux to know where to begin.

I\'ll point you to a couple of posts about these things, and hope.
<a href=\"http://www.climateprediction.net/board/viewtopic.php?t=2124\"> Here</a> and <a href=\"http://www.climateprediction.net/board/viewtopic.php?t=2126\"> here.</a>

Actually, its an old problem, one I\'ve also had.
http://climateapps2.oucs.ox.ac.uk/cpdnboinc/forum_thread.php?id=3187

I\'m searching for more info -- and will look at the Sulphur Beta BB, as well.

Edit. Took awhile and I didn\'t find much. This was a problem in Beta v. 4.17 and it didn\'t affect all Linux versions equally.

I hope it doesn\'t require a new version to fix!

Posted by Tolu on the SC Beta BB after we reported the problem:
This was a problem in the boinc api with timer handling .
David.A fixed this this morning and i\'ve released a new app version for linux. 4.18. This would also resolve the initial linux failures.


(Tolu\'s post dealt with stoppage of Terminal Window logging and the failure-to-start issue.)

---

"We have met the enemy and he is us." -- Pogo
Greetings from coastal Washington state, the scenic US Pacific Northwest.

OK. Leave it with you.

I am using sulphur version 4.22 without success. Still won\'t start.

---

I am using sulphur version 4.22 without success. Still won\'t start.

Understood; no one is using the old versions (though I have some Beta Runs suspended in favor of Spinup). The point of the post was that the \"fix\" was a new client.

Geophi had the failure with Mandrake and one other implementation. Mine were with SuSE 9.0 and 9.1. As geophi pointed out in a PM, \"pthread\" wasn\'t reported then, so this may not be the same failure. I focused on the \"won\'t start\" aspect of the problem.

As was true in Beta and the thread noted below, my machines got cold awaiting a new release. (I don\'t run other boinc projects.) Bottom line, I can only offer empathy, not help.

Edit: If you haven\'t tried reboot and Reset project (in Projects Tab) to start from the beginning, you have nothing to lose.

By the way, if all four of the machines listed in Your account are physically the same box, they can be merged.

---

"We have met the enemy and he is us." -- Pogo
Greetings from coastal Washington state, the scenic US Pacific Northwest.

Hello AstroWX,
Yes, I have tried (multiple times) to reset the project and start over. Each time, the same thing. Oh well....
Thanks for your empathy.

---

If you edit client_state.sah and reduce the values on_frac, connected_frac and active_frac in the time_stats section to maybe 0.1, it will probably stop assigning sulphur models and give you one of the \"normal\" ones instead. Maybe your PC is more happy with that.

This is not really a solution of course - but maybe an intermediate workaround until a version is out that works better on your box

There aren\'t any slab models now, just sulphur.
Some computers just won\'t work with BOINC no matter what you do. :(

Guess this thread is somewhat related:
http://www.climateprediction.net/board/viewtopic.php?t=3402

---

The problem seems to have been identified. It seems to be an incompatibility with GLIBC windows library versions.

Please see thread:

http://climateapps2.oucs.ox.ac.uk/cpdnboinc/forum_thread.php?id=3822

I have put together a patch that might help fix the problem, until a new version is released.

Cheers,
Stefan.

---