Posts by Carolina Calling
|
1)
Message boards :
News :
"Baffling" "signal" "from HD 164595" is probably none of the above.
(Message 1819889)
Posted 26 Sep 2016 by  Carolina Calling
Post: ID 8124204, that would be kicking around since 1999. SETI@home started 17 May 1999. |
|
2)
Message boards :
Number crunching :
How to bind BOINC to 1 address w/ multi NICs
(Message 1153741)
Posted 19 Sep 2011 by Carolina Calling
Post: Add an explicit route to SSL on the interface in question. It should use that before the default route... |
|
3)
Message boards :
Number crunching :
Orphan WUs and result
(Message 695384)
Posted 28 Dec 2007 by Carolina Calling
Post: ... I just took a look at your account summary again, and I don't see the two HID's which had the orphans, so can we assume that Pappa's suggestions at least got the project to realize they where orphans and do something about it? Actually, the old WUs DID get included in the reload. One has successfully reloaded and the other is (at this moment) 50.16% reloaded. The application is hanging BUT I'm curl'ing it separately and will stuff it into the SETI project directory when I get all of it. I'm getting between 64 to 150 KB per retry so I restart with an offset. I get to do that between 13 to 30 times and I'll have it ... (Joy and rapture unforseen... WSG) |
|
4)
Message boards :
Number crunching :
Orphan WUs and result
(Message 695364)
Posted 28 Dec 2007 by Carolina Calling
Post: The next step to try would [be to] have BOINC Issue a "Reset Seti" then check to see if the WU's are reissued. If they are not then the "BOINC Detach" the[n] reattach. The would tell the Seti Servers that the workunits are lost and reissue. Oh, boy. While a reset was, in theory, a good idea, it turns out that the HTTP server boinc2 has a REALLY hard time delivering the files. Typically, it takes over five minutes to START a transfer and then resets connections well before completion. The GPL license file has yet even to start transfer and the 5.27 executable aborts before five percent has transferred I really have to wonder how anyone ever attaches to SETI@home in the first place. This has been going on since yesterday. The thought of detaching and reattaching seriously give me pause ... |
|
5)
Message boards :
Number crunching :
Orphan WUs and result
(Message 695156)
Posted 27 Dec 2007 by Carolina Calling
Post: Found merge by name. Done. However, the totals are now totally bogus... but what the hey. I've been doing this since practically day one because I think this is a "good idea". The merge actually solved a different problem than what I asked about (and one I hadn't realized I'd had). So, how does one fix the WU/Result and solo WU sitting by their lonesome in the SETI projects directory? I would imagine there's a file missing that's supposed to point to them to let BOINC know they're there (or what?). I get the distinct feeling fixing this will involve generating files with signatures using keys I don't have ... and I'm SOL. Thanks!! We fixed one problem at least! :-<) |
|
6)
Message boards :
Number crunching :
Orphan WUs and result
(Message 695142)
Posted 27 Dec 2007 by Carolina Calling
Post: I was considering that, too. But looking at the results from the two older listed machines, they both have one result which is still waiting. So I figured it is worth an attempt at merging, since the results have not yet been marked non-returnable. OK, I'll bite. How does one do a "merge". I looked in "my computers" and there's nothing obvious. I take it I can't go back to the old ID? Also, will this solve the issue that these work units are in projects/seti... but do not show up in BOINC? |
|
7)
Message boards :
Number crunching :
Orphan WUs and result
(Message 695074)
Posted 27 Dec 2007 by Carolina Calling
Post: My Intel Linux system locked up due to thermal overload and I restarted it. It seems there are lost files in the journalling filesystem where BOINC is located. I now find an orphaned work unit and result as well as a solo WU. BOINC doesn't show any of them. Is there any way to "reconnect" them such that they will be reported and processed respectively? Should I just delete them as lost causes? |
|
8)
Message boards :
Number crunching :
Strange goings on from SETI@home ...
(Message 549989)
Posted 21 Apr 2007 by Carolina Calling
Post: I'd very much like this particular incident to be a nightmare, gentlefolk. Perhaps I should elaborate a bit more about what I was thinking before I kill those tasks. My first thought at the time was that these new images in slot/0 MUST be bogus. First, here's something to consider ... % locate setiathome- /home/boinc/BOINC/projects/setiathome.berkeley.edu/setiathome-5.12.i686-pc-linux-gnu /home/boinc/BOINC/projects/setiathome.berkeley.edu/setiathome-5.12.i686-pc-linux-gnu.so /home/boinc/BOINC/slots/0/setiathome-5.12.i686-pc-linux-gnu /home/boinc/BOINC/slots/0/setiathome-5.12.i686-pc-linux-gnu.so % (BTW, the above is the entire output.) The projects/setiathome-* images have a Sept 22, 2006 date. The slot/0 ones were created April 20, 2007. i.e. brand new. And, yes, I did run "locate", "ls -la" and "ls -lac" on the located directories before I deleted the files. I wish I had made a tarball of the files or even compared them to one another before I deleted them. So, much for forensic software investigation. What can I say? It was 2:45 AM. What I WAS wondering was this: How did some clever S*B get the SETI@home project to download these bogus images for him/her?! And, no, it wasn't an alien. It was a smiley sticking out it's tongue. :-^ |
|
9)
Message boards :
Number crunching :
Strange goings on from SETI@home ...
(Message 549499)
Posted 20 Apr 2007 by Carolina Calling
Post: A little while ago, about three hours now, I woke up and, while I was up, decided to check on the SETI@home running on my Linux box. I clicked on the task tab ... and nothing happened. I clicked on all the other tabs ... nothing happened. I contemplated this for a moment, thanked my lucky stars that I had BOINC running as a separate user, su'ed to root from my own account window and killed BOINC and the SETI@home task outright (kill -9 ...). Entertainingly, BOINC or SETI@home made a face as it died! i.e. :-^) (or something close to that...) I then examined the BOINC directory. The slot/0 directory had a new SETI@home image in it and a new .so file. I deleted these, opened a window for BOINC, and started BOINC (and therefore SETI@home) again. It is working fine with no strange behavior. Has anyone else experienced something like this? |
©2026 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.