2: runaway loop? and boincmgr passwords

Questions and Answers : Unix/Linux : 2: runaway loop? and boincmgr passwords
Message board moderation

To post messages, you must log in.

AuthorMessage
Fortran

Send message
Joined: 20 Apr 06
Posts: 16
Credit: 13,398,872
RAC: 31
Canada
Message 1624890 - Posted: 7 Jan 2015, 14:46:18 UTC

I have 2 problems, but came looking specifically about a runaway loop. I am running on a dual core amd64 machine. Way back when, it was Debian/unstable, not too long ago changed to Gentoo. Lately, SETI jobs take from 2-8 hours of CPU time, the currently active process is over 90 hours. Which is still quite a bit less than the climate prediction jobs I get. But is it possible that this has run past some loop exit condition accidentally, and now it will never end? How long should I let it run?

Second. Every since the switch to Gentoo (caused by a disk crash, so I never had access to the original BOINC stuff in /var), trying to start the BoincMgr via the GUI menu results in a manager which can't talk to the clients or the BOINC projects running tasks. What I have been doing, is to start a shell, and use the command line to start the manager:

boincmgr -p `cat /var/lib/boinc/gui_rpc_auth.cfg` &

which works.

I need to shut down this machine for an OS upgrade, and some hardware issues, so I thought I would look into this again.

Thanks.
ID: 1624890 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15184
Credit: 4,362,181
RAC: 3
Netherlands
Message 1624953 - Posted: 7 Jan 2015, 17:19:51 UTC - in response to Message 1624890.  

Lately, SETI jobs take from 2-8 hours of CPU time, the currently active process is over 90 hours. Which is still quite a bit less than the climate prediction jobs I get. But is it possible that this has run past some loop exit condition accidentally, and now it will never end? How long should I let it run?

There are two main sorts of tasks available at Seti, one is the Multibeam tasks, which run anywhere from mere seconds to those 8 hours you mention, and the second is Astropulse, which runs from mere seconds to multi-tens-of-hours on a CPU.

You had one of the latter. An Astropulse v7.
They're a broadband way of looking for ET, whereas Multibeam is narrow band.
More on the differences between the two, at the AP FAQ and How Seti@Home works.

Second.

You added BOINC from Berkeley or from repository? The latter I think, seeing how it's "7.2.0", unless you built it yourself?
Did you follow http://boinc.berkeley.edu/wiki/Installing_BOINC_on_Gentoo on that? (Do read the Optional setup hints)
ID: 1624953 · Report as offensive
Fortran

Send message
Joined: 20 Apr 06
Posts: 16
Credit: 13,398,872
RAC: 31
Canada
Message 1625001 - Posted: 7 Jan 2015, 18:30:47 UTC - in response to Message 1624953.  

The name on that long running SETI job looks the same as the others queued up. But, I won't worry about it for a while yet.

Yes, BOINC came from a repository. No doubt, I have the wrong password stored in that login box that pops up with new jobs. I added the user that normally views boincmgr to the boinc group, so that the "cat" gets the password in that cfg file.

Thanks.
ID: 1625001 · Report as offensive
Fortran

Send message
Joined: 20 Apr 06
Posts: 16
Credit: 13,398,872
RAC: 31
Canada
Message 1625845 - Posted: 9 Jan 2015, 17:03:58 UTC - in response to Message 1625001.  

FYI - that long running job died at 140+ hours with a computation error.
ID: 1625845 · Report as offensive

Questions and Answers : Unix/Linux : 2: runaway loop? and boincmgr passwords


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.