Questions and Answers :
Unix/Linux :
Error: GUI RPC request from non-local address, like, a million times.
Message board moderation
Author | Message |
---|---|
abject Send message Joined: 3 Apr 99 Posts: 65 Credit: 857,951 RAC: 0 |
I think I've seen this discussed someplace, but can't find the thread. Please redirect me if you see it. Anyway, Linux client 3.18, Debian testing/unstable. Something very bad happened last night while I was watching fireworks. It was so bad that I can't even find the logfile anymore :(. Well... I'm such a klutz that I blasted the logfile. So, I went to restart boinc and got "another copy is already running" so I: $ mv lockfile lockfile.was And then: $ ./boinc_3.18_i686-pc-linux-gnu 2004-07-05 10:20:16 [---] Starting BOINC client version 3.18 for i686-pc-linux-gnu 2004-07-05 10:20:16 [SETI@home] Project prefs: using your defaults 2004-07-05 10:20:16 [SETI@home] Host ID not assigned yet 2004-07-05 10:20:16 [---] General prefs: from SETI@home (last modified 2004-07-04 08:33:38) 2004-07-05 10:20:16 [---] General prefs: using your defaults 2004-07-05 10:20:16 [---] GUI RPC bind failed (retval = '-1') 2004-07-05 10:20:16 [---] GUI RPC bind failed (retval = '-1') 2004-07-05 10:20:16 [SETI@home] Deferring communication with project for 59 minutes and 39 seconds 2004-07-05 10:20:16 [SETI@home] Deferring communication with project for 59 minutes and 39 seconds 2004-07-05 10:20:16 [---] GUI RPC request from non-local address 0x78570e08 2004-07-05 10:20:16 [---] GUI RPC request from non-local address 0x78570e08 [Repeats forever until ^C...] It looks like some or all of the XML files in my boinc directory got hosed. So, How to fix this? I could re-register and merge the new and old incarnations of this computer. Is there a way to do it without dumping my WU cache? Or is it already too late for that? Thanks |
EclipseHA Send message Joined: 28 Jul 99 Posts: 1018 Credit: 530,719 RAC: 0 |
Stop boinc and see if you have a process "setiathome_3.08_i686-pc-linux-gnu" running. (ps -eaf|grep seti) If so, kill -it. (kill -9 [pid from above]) When you restart boinc, it should be ok. I've seen this a couple of times where killing boinc doesn't stop the seti process... Rebooting should clear it up too. |
©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.