Thread 'Error Msg ???'

Message boards : BOINC Manager : Error Msg ???
Message board moderation

To post messages, you must log in.

AuthorMessage
Knightrider

Send message
Joined: 29 Aug 05
Posts: 9
United Kingdom
Message 668 - Posted: 6 Oct 2005, 16:59:36 UTC

I am running Tiger (osx 10.4.2) on a Apple Macintosh G5 dual 2.0 ghz with 2.5 gig ddr sdram ad BOINC Manager 5.1.8

These showed up in Red in my Messages Tab

2005-10-06 17:23:07 [---] ACTIVE_TASK_SET::check_app_exited(): pid 271 not found

2005-10-06 17:29:19 [---] ACTIVE_TASK_SET::check_app_exited(): pid 287 not found

Anyone?

K.
ID: 668 · Report as offensive
Paul D. Buck

Send message
Joined: 29 Aug 05
Posts: 225
Message 672 - Posted: 7 Oct 2005, 7:59:51 UTC

WHen there was an operation on what should have been a task within a task set, the task looked for did not exist. If you send me your log files I may be able to tell you more ... then again, maybe not ...

[email protected]
ID: 672 · Report as offensive
Knightrider

Send message
Joined: 29 Aug 05
Posts: 9
United Kingdom
Message 673 - Posted: 7 Oct 2005, 8:34:42 UTC

Hi Paul,

The log files are gone now, but I did look at them and there was nothing out of the ordinary. Just these two lines at different points

I know PID is Process identity ( P - id) But which and what?

btw - Wiki pages looking good - nice work.

K.
ID: 673 · Report as offensive
Paul D. Buck

Send message
Joined: 29 Aug 05
Posts: 225
Message 675 - Posted: 7 Oct 2005, 16:16:55 UTC

This is one of those things that I have been trying to pick apart as I delve into the code of BOINC. An ACTIVE TASK SET is an object used in the BOINC application. At this time I do not have it figurred out. Since there is little to no internal code documentation I have to do it the reverse engineering way. This in addition to all else I try to do in the time I can work. Ugh.

Ok, supposition, the active task set is the intenal list of the running science applications. This is essentially the content or part of the content, if you will, of the work tab. When the BOINC Daemon looks for a science application in the set that it thinks should be there, but cannot find it, well, you will get a message such as the one you had.

I am looking for work unit/result "x" being processed by PID, "z" but the process is not running though I had expected it would be alive ...

Again, this is my current state of guess work, as I fumble aroud with trying to work on the development side of the documentation. My current approach is from the direction of messages because that seems to be the most "useful" for the most people. But, it also allows us to get a better "handle" on what is happening when bad things happen to good BOINC installations. :)

Anyway, thanks for the compliment. I hunt for new messages and the context because I feel that is the only way that they can be "relevant" for the bulk of us. I always felt cheated when I read other documentation on messages where they spelled out the message and then gave a blurp about it. Heck, I already know hwo the message is spelled, why did it happen, and what else was going on that might supply context.
ID: 675 · Report as offensive
Knightrider

Send message
Joined: 29 Aug 05
Posts: 9
United Kingdom
Message 681 - Posted: 8 Oct 2005, 14:27:23 UTC

"I am looking for work unit/result "x" being processed by PID, "z" but the process is not running though I had expected it would be alive ..."

I wondered about this but now I am not so sure as PID may mean 'Project identifier' as in cross project identifier.


K.
ID: 681 · Report as offensive
Paul D. Buck

Send message
Joined: 29 Aug 05
Posts: 225
Message 682 - Posted: 8 Oct 2005, 14:44:53 UTC

No.

PID is a "standard" identifier for Process ID on a computer.

And, 20 hours of looking at the code where those error messages come from assure me that it is what I said ... :)
ID: 682 · Report as offensive

Message boards : BOINC Manager : Error Msg ???

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.