| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Help with upgrade from F15 to F16, with all files still in tact, except /etc files |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 6
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi all,
----------------------------------------Every time I upgrade Fedora, I end up having problems reconnecting with WCG. I did manage to keep a copy of my /var/lib/boinc directory and got it back, and re-installed boinc. What I forgot to do was to keep the /etc related boinc files. Next time shouldn't be as much of a problem, as I cteated a raid, and now have the /var directory on the same logical volume as everything else, so I can do an upgrade, instead of being forced to do a full install. I am not all that great at bash, but can get myself around. I just can't seem to re-connect. The deamon shows up in service configuration, but when I try to do any thing with boinccmd (including --project_attach), I get "Authorization failure: -155". The last time I upgraded (full install), I spent hours editing the Eric Myers script to make everything work. I like the script, but am not apposed to going with something more straight forward, as Eric included several statements to include several different OS situations. I run two AMD quad core systems, one Win7, the other Fedora. The Fedora machine ALWAYS out performs the windows system by at least 50%. Both systems are all but identical, except for motherboards and CPU's, and the windows machine has an obvious advantage. Linux is on an ASUS M3N72D AMD 940, and Windows is on an M4N82D AMD 945. Both have identical 8GB RAM. Can someone please help?  Thanks, Tom [Edit 6 times, last edit by Former Member at Feb 19, 2012 3:06:27 AM] |
|||
|
||||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Look for the gui_rpc_auth.xml file ownerships and permissions. Those in the etc/boinc-client folder are the real files, symlinked from the /var/lib/boinc-client data dir folder. The permissions on those files have to be right.
------------------------------------------//-- edit: And the official Fedora install Wiki from Berkeley: http://boinc.berkeley.edu/wiki/Installing_BOINC_on_Fedora [Edit 1 times, last edit by Former Member at Feb 19, 2012 9:40:40 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thanks for the reply, I forgot about the boinc page for installing on Fedora.
However in Fedora, the actual files are in the /var/lib/boinc directory, I haven't heard of them being linked from /etc. There is no directory /etc/boinc, or boinc-client. Only scripts in /etc/rc.d/init.d, and /etc/sysconfig. All files have proper permissions. My problem is only in authroization, using the original /var/lib/boinc files from F15. I don't want to loose the work that was started there, and the files already downloaded for crunching need to be completed. The deamon shows up as available, but stops shortly after starting. I'm not really worried about the GUI yet. I need to get the deamon actually running and authorized, then I can use the GUI. Regards, Tom |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The password is also needed if executing boinccmd from outside where the boinc client itself is stored.
Gave you the standard locations for Ubuntu. Don't ask me why different Linux flavors have to have it in different places. Most of the times reinstalling BOINC does not loose already existing project files, but you could always make a backup, then restore them later [do all this when disconnected from the internet or the server will see things out of sync and cancel all tasks]. Daemon starting and then stopping shortly after is a sure thing there's a read/write permission issue with the control files of BOINC. Briefly viewing the wiki, and seeing your paths, suggest to follow to the letter, to include the ln on gui_prc_auth.cfg towards the end. --//-- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Due to the extended time it has taken to attempt to resolve this, the deadlines on the files I have undoubtedly have passed. So, I am forced to just start from scratch, which I have always done before. Had I had the luxury of shutting down calculations before the installation, I never would have had this problem.
However, maybe a point by point proceedure needs to be developed for situations of system crashes, where data has been backed up and is retrievable. I was unable to find anything on any site that even spoke on the subject. The importance of this work is very important to me, and I only wish for smooth transitions, so data is not lost or delayed. Regards, Tom |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
This thread can be closed
|
||
|
|
|