| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Fedora F23 23 BOINC Client stops running |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 10
|
|
| Author |
|
|
mrerick
Cruncher Joined: Dec 31, 2005 Post Count: 5 Status: Offline Project Badges: 
|
I just upgraded a couple of machines to the final release version of Fedora 23 F23 via their DNF plugin upgrade process.
When booted, the BOINC-Client will start, but fails almost immediately with an error code 2. I also briefly saw an error message on the BOINC-Manager indicating a problem writing state information. Here's the BOINC Log: 24-Oct-2015 17:54:13 [---] cc_config.xml not found - using defaults 24-Oct-2015 17:54:13 [---] Starting BOINC client version 7.2.42 for x86_64-pc-linux-gnu 24-Oct-2015 17:54:13 [---] log flags: file_xfer, sched_ops, task 24-Oct-2015 17:54:13 [---] Libraries: libcurl/7.43.0 NSS/3.20 Basic ECC zlib/1.2.8 libidn/1.32 libssh2/1.6.0 nghttp2/1.3.3 24-Oct-2015 17:54:13 [---] Data directory: /var/lib/boinc 24-Oct-2015 17:54:13 [---] Failed to delete old coproc_info.xml. error code -110 24-Oct-2015 17:54:13 [---] No usable GPUs found 24-Oct-2015 17:54:13 [---] Host name: xxxxxxxxxx 24-Oct-2015 17:54:13 [---] Processor: 2 GenuineIntel Intel(R) Core(TM)2 Duo CPU P8700 @ 2.53GHz [Family 6 Model 23 Stepping 10] 24-Oct-2015 17:54:13 [---] Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts nopl aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm ida dtherm tpr_shadow vnmi flexpriority 24-Oct-2015 17:54:13 [---] OS: Linux: 4.2.3-300.fc23.x86_64 24-Oct-2015 17:54:13 [---] Memory: 2.84 GB physical, 3.78 GB virtual 24-Oct-2015 17:54:13 [---] Disk: 49.09 GB total, 31.00 GB free 24-Oct-2015 17:54:13 [---] Local time is UTC -4 hours 24-Oct-2015 17:54:13 [---] Can't open client_state_next.xml: fopen() failed 24-Oct-2015 17:54:13 [---] Couldn't write state file; check directory permissions 24-Oct-2015 17:54:13 [World Community Grid] URL http://www.worldcommunitygrid.org/; Computer ID 2764480; resource share 100 24-Oct-2015 17:54:13 [World Community Grid] General prefs: from World Community Grid (last modified 07-May-2015 20:34:37) 24-Oct-2015 17:54:13 [World Community Grid] Host location: none 24-Oct-2015 17:54:13 [World Community Grid] General prefs: using your defaults 24-Oct-2015 17:54:13 [---] Reading preferences override file 24-Oct-2015 17:54:13 [---] Preferences: 24-Oct-2015 17:54:13 [---] max memory usage when active: 1452.78MB 24-Oct-2015 17:54:13 [---] max memory usage when idle: 2615.00MB 24-Oct-2015 17:54:13 [---] max disk usage: 1.00GB 24-Oct-2015 17:54:13 [---] don't use GPU while active 24-Oct-2015 17:54:13 [---] suspend work if non-BOINC CPU load exceeds 35% 24-Oct-2015 17:54:13 [---] (to change preferences, visit a project web site or select Preferences in the Manager) 24-Oct-2015 17:54:13 [---] Not using a proxy 24-Oct-2015 17:54:21 Initialization completed 24-Oct-2015 17:55:03 [---] Can't write state file, exiting in 10 seconds 24-Oct-2015 17:55:14 [---] Can't write state file, exiting now 24-Oct-2015 17:55:14 [---] Time to exit 24-Oct-2015 17:55:14 [---] Can't open client_state_next.xml: fopen() failed |
||
|
|
petehardy
Senior Cruncher USA Joined: May 4, 2007 Post Count: 318 Status: Offline Project Badges: 
|
24-Oct-2015 17:54:13 [---] Can't open client_state_next.xml: fopen() failed 24-Oct-2015 17:54:13 [---] Couldn't write state file; check directory permissions Looks like Boinc can't access it's data directory.  "Patience is a virtue", I can't wait to learn it! |
||
|
|
mrerick
Cruncher Joined: Dec 31, 2005 Post Count: 5 Status: Offline Project Badges:
|
24-Oct-2015 17:54:13 [---] Can't open client_state_next.xml: fopen() failed 24-Oct-2015 17:54:13 [---] Couldn't write state file; check directory permissions Looks like Boinc can't access it's data directory. Yes - but I made no changes between releases. BOINC no longer has ownership, control and read/write access to the files and directory. I tried setting SELinux to Permissive and it made no difference. Tried removing and re-installing it. No difference. - - I'm doing some checking now. Install process under the DNF system-upgrade may have left the /var/lib/boinc subdirectory under "root" ownership, changing it from it's original "boinc" ownership. An installation script for Fedora rather than the manual process outlined here would be helpful: http://boinc.berkeley.edu/wiki/Installing_BOINC_on_Fedora If the upgrade resulted in a remove and re-install of the packages, many BOINC clients will start failing. [Edit 2 times, last edit by mrerick at Oct 26, 2015 4:04:37 PM] |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Can't open client_state_next.xml: fopen() failed
----------------------------------------Never heard of such a file. The procedure is to backup the client_state.xml file every so many seconds to client_state_prev.xml, then write a new client_state.xml. But ah lah, google revealed a discussion at times, http://permalink.gmane.org/gmane.comp.distributed.boinc.devel/6545 , too many files open it reads as. What client version are you using and reinstalling? What would we do without search functions ;P) edit: see in log 7.2.42. Is that latest tested on for your version of Fedora? [Edit 2 times, last edit by SekeRob* at Oct 25, 2015 3:41:10 PM] |
||
|
|
petehardy
Senior Cruncher USA Joined: May 4, 2007 Post Count: 318 Status: Offline Project Badges:
|
10/25/2015 12:14:34 PM | | cc_config.xml not found - using defaults 10/25/2015 12:14:34 PM | | Starting BOINC client version 7.6.9 for windows_x86_64 10/25/2015 12:14:34 PM | | log flags: file_xfer, sched_ops, task 10/25/2015 12:14:34 PM | | Libraries: libcurl/7.39.0 OpenSSL/1.0.2a zlib/1.2.8 10/25/2015 12:14:34 PM | | Data directory: C:\ProgramData\BOINC 10/25/2015 12:14:34 PM | | Running under account Pete Here are the first few lines of my event log. Did you remove the line with the account being used by Boinc? "Patience is a virtue", I can't wait to learn it! |
||
|
|
mrerick
Cruncher Joined: Dec 31, 2005 Post Count: 5 Status: Offline Project Badges:
|
Hi, I am using the latest version of BOINC for Fedora 23. 7.2.42(x64).
----------------------------------------I made no changes to the BOINC installation, including anything having to do with it's subdirectories or control files / token in my user's space. The thing that is different is that there is a new migration procedure to Fedora 23 using their "dnf" package manager. Instead of the old "Fedup" process (which automatically protected configurations), DNF removes the old packages associated with Fedora 22 and installs new F23 version packages directly from distribution. This process appears to end up changing both the ownership and group associated with the /var/lib/boinc subdirectory and files within it. After the upgrade, they end up owned by "root" instead of "boinc". I did get things working by manually deleting boinc-client and boinc-manager, manually deleted the /var/lib/boinc subdirectory and then re-installed boinc-client and boinc-manager. Before starting the boinc-client, I changed ownership and group of the /var/lib/boinc subdirectory back to "boinc" with: chown boinc /var/lib/boinc chgrp boinc /var/lib/boinc then manually following the steps in http://boinc.berkeley.edu/wiki/Installing_BOINC_on_Fedora then re-launched the boinc-client and boinc-manager. These steps include the following: /usr/sbin/usermod -G boinc -a username chmod g+rw /var/lib/boinc chmod g+rw /var/lib/boinc/*.* ln -s /var/lib/boinc/gui_rpc_auth.cfg /home/username/gui_rpc_auth.cfg I expect that as of Fedora 23 there is a problem successfully changing ownership of the /var/lib/boinc directory during the DNF install script. [Edit 4 times, last edit by mrerick at Nov 4, 2015 3:09:31 AM] |
||
|
|
mrerick
Cruncher Joined: Dec 31, 2005 Post Count: 5 Status: Offline Project Badges:
|
Using the just released final version of Fedora 23 Workstation, and their standard "dnf" based upgrade path:
http://fedoramagazine.org/upgrading-from-fedora-22-to-fedora-23/ I just confirmed again that this will break an existing BOINC installation and that a new installation will also fail. The problem is that the owner and group associated with /var/lib/boinc is changed to "root" in this process. It has to be changed back to "boinc" to get things working again. The symptom is that the boinc client will report an error trying to save it's state, and the tasks will not run. As mentioned earlier, you can fix this by changing the /var/lib/boinc permissions back. I used the following commands, and re-booted: sudo chown boinc:boinc /var/lib/boinc sudo chown boinc:boinc /var/lib/boinc/*.* On a new or replacement installation you have to also follow the steps in http://boinc.berkeley.edu/wiki/Installing_BOINC_on_Fedora then re-launched the boinc-client and boinc-manager. These steps include the following: /usr/sbin/usermod -G boinc -a username chmod g+rw /var/lib/boinc chmod g+rw /var/lib/boinc/*.* ln -s /var/lib/boinc/gui_rpc_auth.cfg /home/username/gui_rpc_auth.cfg Has anyone determined if this is a BOINC install script problem, or a problem with the Fedora "dnf" upgrade process? Why is the ownership of /var/lib/boinc being changed? |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
You'd have to ask the Fedora package maintainer. If you have determined the steps to make things working again on F23, then it is surely greatly appreciated if you'd update the linked wiki reference with your newly gained experience. Better place to ask may be at the Berkeley fora. Information/Issues posted there often get forwarded to the BOINC developers, but to mention [if not already], build testing is only done under Ubuntu.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thanks, I had the same problem.
However, placing all data into /var/lib has a certainty of deleting an existing installation when yuo reinstall a system, because /var will be erased in Fedora. for other distros's io can not tell, because I only run Fedora. To change this I mounted /var/lib/boinc to a directory in my homedirectory with: >>/home/%%NAME%%/BOINC /var/lib/boinc none defaults,bind 0 0<< which solved that problem. |
||
|
|
adriverhoef
Master Cruncher The Netherlands Joined: Apr 3, 2009 Post Count: 2346 Status: Recently Active Project Badges: 
|
1) Unless you specify that you want to erase a filesystem, there may be a very small chance that a filesystem will be erased. In the past 10 years the directory /var/lib/news (part of the filesystem /var) has never been erased on my computer during an upgrade. NOTE: Always backup your data before upgrading!
----------------------------------------2) The problem with the ownership of /var/lib/boinc on Fedora 23 has been addressed (see https://bugzilla.redhat.com/show_bug.cgi?id=1278881 ). [Edit 1 times, last edit by adriverhoef at Nov 25, 2015 7:37:51 PM] |
||
|
|
|