Upgraded to 4.13 client - now always

Questions and Answers : Unix/Linux : Upgraded to 4.13 client - now always
Message board moderation

To post messages, you must log in.

AuthorMessage
Bruce

Send message
Joined: 3 Apr 99
Posts: 2
Credit: 862,463
RAC: 0
United States
Message 36519 - Posted: 14 Oct 2004, 14:46:51 UTC
Last modified: 14 Oct 2004, 15:07:49 UTC

I'd been running a previous version of the boinc client for a while and haven't had any problems. I just upgraded to boinc_4.13_i686-pc-linux-gnu, but now whenever I try to run it I just get the error:

2004-10-14 10:39:06 [---] Another instance of BOINC is running

I've gone so far as to reboot my linux box (despite not having any instances of boinc or seti running) but that hasn't helped. Each time I run it it creates a lockfile which I delete, but that doesn't help either. I'm now entirely unable to run boinc. Is anybody else seeing this with the 4.13 client? Any suggestions?

Update: I managed to download a few earlier versions of the client. 4.12 results in the same behavior - it always exits immediately with the error that another instance is running. 4.09 works fine. So I'm sticking with 4.09 for now.
ID: 36519 · Report as offensive
Profile xi3piscium
Volunteer tester
Avatar

Send message
Joined: 17 Aug 99
Posts: 287
Credit: 26,674
RAC: 0
China
Message 36583 - Posted: 14 Oct 2004, 18:09:26 UTC
Last modified: 14 Oct 2004, 18:10:19 UTC

I believe there was a post regarding this
same issue a couple of months ago. I think
the solution was to change the permissions
for your directory where boinc is installed.
By default my permissions for that directory
are set to 775...hope that helps.
Running Fedora Core 2 and 4.13.

Crunching in Chongqing China....

Regards,

Joe


ID: 36583 · Report as offensive
Profile abject
Avatar

Send message
Joined: 3 Apr 99
Posts: 65
Credit: 857,951
RAC: 0
United States
Message 36702 - Posted: 15 Oct 2004, 2:36:21 UTC

4.12 gave Winderz users problems. 4.13 for Winderz fixed thos problems. For Winderz

4.12 (linux) is working fine for me. Are you trying to solve some problem with 4.13? If not, I recommend you go back to 4.12.
ID: 36702 · Report as offensive
Bruce

Send message
Joined: 3 Apr 99
Posts: 2
Credit: 862,463
RAC: 0
United States
Message 36845 - Posted: 15 Oct 2004, 12:10:44 UTC - in response to Message 36583.  

> By default my permissions for that directory
> are set to 775...hope that helps.

Well I went so far as to chmod -R 777 my boinc/seti directory and that didn't help. 4.09 still runs fine but 4.12 & 5.13 still result in the error that another instance is running... This is on debian 3.0 with a 2.4.26 kernel.
ID: 36845 · Report as offensive
Profile abject
Avatar

Send message
Joined: 3 Apr 99
Posts: 65
Credit: 857,951
RAC: 0
United States
Message 36996 - Posted: 15 Oct 2004, 21:57:11 UTC - in response to Message 36845.  
Last modified: 15 Oct 2004, 21:57:43 UTC

I'm running 2.6.7 and a mixed Sarge/Sid. 4.09 won't upload for me, but 4.12 works fine.

If I were you, I'd stick with 4.09 and wait for > 4.13 to see if they fix its problems.
ID: 36996 · Report as offensive
Profile xi3piscium
Volunteer tester
Avatar

Send message
Joined: 17 Aug 99
Posts: 287
Credit: 26,674
RAC: 0
China
Message 38016 - Posted: 18 Oct 2004, 22:47:26 UTC

Bruce...sorry my last suggest did not work for you.
Have you looked at your permissions on the boinc core
client? maybe giving that "write" permissions or just
change the permissions to 775 on boinc cc. I also looked
at my lock file, the permissions there are 644. I had this
problem several months ago, I remember there being a post
in the linux questions and problems and a resolve for that
problem. Also are you running CPDN, lhc@home, pirates@home?
maybe the problem is there. I am running only S@H, my OS is
Fedora Core 2....using boinc 4.13. Just trying to help...

Regards,

Joe
ID: 38016 · Report as offensive

Questions and Answers : Unix/Linux : Upgraded to 4.13 client - now always


 
©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.