| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Problems running BOINC in Linux |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 9
|
|
| Author |
|
|
Gort
Cruncher Joined: Dec 29, 2005 Post Count: 19 Status: Offline Project Badges: 
|
For years, I have been running BOINC under opensuse. After the most recent linux upgrade it no longer works. I tried all the advice I found to get BOINC manager to run but none worked.
I did get the boinc client to run in a terminal, or so I thought. Checking this website, I find the last three results I uploaded came back with this error: <core_client_version>6.10.58</core_client_version> I leave my computer running 24/7 for months at a time to keep crunching. This latest difficulty is very disappointing. I hope I don't have to give up on WCG. |
||
|
|
Falconet
Master Cruncher Portugal Joined: Mar 9, 2009 Post Count: 3315 Status: Offline Project Badges: 
|
Maybe you could install a newer version?
----------------------------------------6.10.58 is a few years old. Maybe opensuse no longer works well with it.  - AMD Ryzen 5 1600AF 6C/12T 3.2 GHz - 85W - AMD Ryzen 5 2500U 4C/8T 2.0 GHz - 28W - AMD Ryzen 7 7730U 8C/16T 3.0 GHz |
||
|
|
sunfolk
Master Cruncher Super Kiwi Socialistic Empire Of Jacinda Joined: Oct 8, 2006 Post Count: 1769 Status: Offline Project Badges:
|
Hi Gort, thanks for opening a new thread, it keeps things tidy.
---------------------------------------- In the other thread you say that linking libraries resolved some issues, and here the boinc client cant write an init file. It sounds like you have a non standard installation (symbolic links shouldn't be needed) with broken permissions (no write permission). There are two ways to install boinc on linux, the messy WCG download or use your distributions package manager. The package manager will take care of permissions etc automatically. I dont know which installation you had but the upgrade clearly wasnt compatible. If you are unable to fix your permissions manually I would just remove all traces of the original client & manager and do a clean install using your package manager (YUM?). Hope this helps , Good luck     [Edit 1 times, last edit by sunfolk at Jan 8, 2014 6:31:26 AM] |
||
|
|
Gort
Cruncher Joined: Dec 29, 2005 Post Count: 19 Status: Offline Project Badges:
|
Sometimes, when you're up to your butt in alligators, it's hard to remember that you came there to drain the swamp.
I'm all the way back to the error that started me: can't connect to localhost. I've been searching the forum for a post that I saw telling that there is a password somewhere that must be entered when you select "connect to a computer" from the menu. I can't find the post or the password! In the meantime, I removed the installation of BOINC and re-installed via the package manager. That gave me a boincmgr that runs but can't connect to the localhost. I get an error message saying the manager exit 3 times in the last 2 minutes and asking if I want to try again. I do, but it never connects. My package manager, yast, gave me 6.12.6- something. I tried running the manager from the terminal. It crashes immediately, giving me this: SIGSEGV: segmentation violation Stack trace (7 frames): ./boincmgr(boinc_catch_signal+0x64)[0x817e354] linux-gate.so.1(__kernel_sigreturn+0x0)[0xb76fc400] /lib/libc.so.6(__longjmp_chk+0x25)[0xb6ad39e5] /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-png.so(+0x2254)[0xace27254] ./boincmgr(png_error+0x53)[0x83da273] ./boincmgr(png_create_read_struct_2+0x2a0)[0x83dd420] /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-png.so(+0x303b)[0xace2803b] Exiting... When I upgraded to the 3.11 (?) kernel and opensuse 13.1, I had a terrible time with the nvidia driver. It took me 2 weeks to get the gui going. I have been working on this almost as long. I just tried to run the client from a terminal. It tells me it is 6.10? I don't understand what happened to the 6.12 I downloaded. Where do I begin? |
||
|
|
sunfolk
Master Cruncher Super Kiwi Socialistic Empire Of Jacinda Joined: Oct 8, 2006 Post Count: 1769 Status: Offline Project Badges:
|
Lets ignore the Alligators and look for the drain.
----------------------------------------If the manager cant connect to the client on the localhost it could be because the client isnt running. open a terminal and check with: ps -e | grep boinc You should see something like this: 1158 ? 00:00:31 boinc 2091 ? 00:05:01 boincmgr if boinc isn't running in Ubuntu you start the service with: sudo service boinc-client start I am unsure what the Suse command is(maybe /etc/init.d/boinc-client start ) you need to google. Then restart the manager. |
||
|
|
Gort
Cruncher Joined: Dec 29, 2005 Post Count: 19 Status: Offline Project Badges:
|
Lets ignore the Alligators and look for the drain. If the manager cant connect to the client on the localhost it could be because the client isnt running. open a terminal and check with: ps -e | grep boinc You should see something like this: 1158 ? 00:00:31 boinc 2091 ? 00:05:01 boincmgr if boinc isn't running in Ubuntu you start the service with: sudo service boinc-client start I am unsure what the Suse command is(maybe /etc/init.d/boinc-client start ) you need to google. Then restart the manager. I adapted your syntax to get boinc-client started. Then I started boinc_manager from cli and got the same crash and output as shown before. Using grep, I now get 5970 ? 00:00:00 boinc-client Note the dashes. I got boinc client to run as boinc-client. But the syntax to start the manager is sh run_manager Next, I tried to get manager to run as a service. Terminal tells me there is no such service. I think I got out all the old vestiges of BOINC before the last install via the package manager. The dash vs. underscore in the file names makes me wonder. Also, I had the client running without manager before but when I checked, the files were returned as errors because boinc couldn't open (or write to ?) a file. I will leave it run as a service (thanks for showing me how!) to see if there is a permissions problem that a service overcomes. Still, no manager. |
||
|
|
sunfolk
Master Cruncher Super Kiwi Socialistic Empire Of Jacinda Joined: Oct 8, 2006 Post Count: 1769 Status: Offline Project Badges:
|
Oh what a tangled web we weave,
----------------------------------------When first we practise to deceive! Sir Walter Scott, Marmion, Canto vi. Stanza 17. Scottish author & novelist (1771 - 1832). Ok, so we have some little Victory's  You can not get the manager to run as a service/daemon, its a GUI program.Start it from the desktop NOT the CLI. Like you I wonder about the - versus _ in file names. Linux is horribly inconsistent when it comes to naming conventions, I'm sure they just make it up as they go along  I dont think I can offer any more in terms of your problem, other than this observation born of cold cruel experience: Linux upgrades are often more trouble than they are worth. A fresh install IMHO is often the best policy. If you value stability over innovation try FreeBSD or Windoze! Have a lot of fun  |
||
|
|
Gort
Cruncher Joined: Dec 29, 2005 Post Count: 19 Status: Offline Project Badges:
|
There may be another root to this problem: the password. In another thread (which I can't find but I will keep looking!) a poster described command line switches. One of them was to run boinc in an insecure mode. I tried it and it worked! boinc manager ran and I returned a few results. However, I rebooted and now can't remember how to run insecure. I tried to do a copy and paste from the gui-something-something file into the manager by choosing select computer from the menu. That did not get the program to connect to the host like running insecure.
|
||
|
|
adriverhoef
Master Cruncher The Netherlands Joined: Apr 3, 2009 Post Count: 2346 Status: Offline Project Badges: 
|
I tried to do a copy and paste from the gui-something-something file into the manager by choosing select computer from the menu. That's probably the file /var/lib/boinc/gui_rpc_auth.cfg At the commandline prompt, if you do echo > /var/lib/boinc/gui_rpc_auth.cfg(if /var/lib/boinc is the directory where your installation of BOINC lives), then it should look like this afterwards: $ ls -l /var/lib/boinc/gui_rpc_auth.cfg NOTE: This is called 'insecure', because there's no password used. If you installed BOINC through your package manager, make sure you know how to start and stop the BOINC client (running as a service). When the BOINC client is running, you can connect to it with the graphical BOINC manager in your desktop environment. |
||
|
|
|