Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 714160 - sci-biology/foldingathome-7.5.1: /etc/init.d/foldingathome broken
Summary: sci-biology/foldingathome-7.5.1: /etc/init.d/foldingathome broken
Status: CONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Science Biology related packages
URL:
Whiteboard:
Keywords:
: 715080 (view as bug list)
Depends on:
Blocks:
 
Reported: 2020-03-24 12:24 UTC by Manfred Knick
Modified: 2020-12-09 17:06 UTC (History)
5 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info foldingathome (emerge--info.foldingathome.txt,6.56 KB, text/plain)
2020-03-30 09:34 UTC, Manfred Knick
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Manfred Knick 2020-03-24 12:24:34 UTC
# /etc/init.d/foldingathome status
 * status: crashed                        <-----

 
Mar 24 08:52:41 sid start-stop-daemon[32580]: 
         pam_unix(start-stop-daemon:session): 
         session opened for user foldingathome by manfred(uid=0)

Mar 24 08:52:47 sid /etc/init.d/foldingathome[32678]: status: crashed   <----

Mar 24 08:53:22 sid start-stop-daemon[888]: 
        Will stop /opt/foldingathome/FAHClient

Mar 24 08:53:22 sid start-stop-daemon[888]: Will stop PID 32580


# /etc/init.d/foldingathome stop
 * Stopping foldingathome ...
 * start-stop-daemon: no matching processes found                                                                                                                                                                                                                                                       [ ok ]


Mar 24 08:53:22 sid /etc/init.d/foldingathome[888]: 
        start-stop-daemon: no matching processes found


Reproducible: Always
Comment 1 Manfred Knick 2020-03-24 12:28:57 UTC
In contrast:   WORKSFORME:

# cd /opt/foldingathome

#  ./FAHClient

./FAHClient: /opt/foldingathome/libssl.so.10: no version information available (required by ./FAHClient)
./FAHClient: /opt/foldingathome/libcrypto.so.10: no version information available (required by ./FAHClient)
./FAHClient: /opt/foldingathome/libcrypto.so.10: no version information available (required by ./FAHClient)

07:54:27:INFO(1):Read GPUs.txt
07:54:27:************************* Folding@home Client *************************
07:54:27:        Website: https://foldingathome.org/
07:54:27:      Copyright: (c) 2009-2018 foldingathome.org
07:54:27:         Author: Joseph Coffland <joseph@cauldrondevelopment.com>
07:54:27:           Args: 
07:54:27:         Config: /opt/foldingathome/config.xml
07:54:27:******************************** Build ********************************
07:54:27:        Version: 7.5.1
07:54:27:           Date: May 12 2018
07:54:27:           Time: 22:51:07
07:54:27:     Repository: Git
07:54:27:       Revision: 4705bf53c635f88b8fe85af7675557e15d491ff0
07:54:27:         Branch: master
07:54:27:       Compiler: GNU 4.4.7 20120313 (Red Hat 4.4.7-18)
07:54:27:        Options: -std=gnu++98 -O3 -funroll-loops
07:54:27:       Platform: linux2 4.14.0-3-amd64
07:54:27:           Bits: 64
07:54:27:           Mode: Release
07:54:27:******************************* System ********************************
07:54:27:            CPU: Intel(R) Xeon(R) CPU E3-1276 v3 @ 3.60GHz
07:54:27:         CPU ID: GenuineIntel Family 6 Model 60 Stepping 3
07:54:27:           CPUs: 8
07:54:27:         Memory: 31.36GiB
07:54:27:    Free Memory: 27.14GiB
07:54:27:        Threads: POSIX_THREADS
07:54:27:     OS Version: 5.5
07:54:27:    Has Battery: false
07:54:27:     On Battery: false
07:54:27:     UTC Offset: 1
07:54:27:            PID: 1208
07:54:27:            CWD: /opt/foldingathome
07:54:27:             OS: Linux 5.5.11-gentoo x86_64
07:54:27:        OS Arch: AMD64
07:54:27:           GPUs: 1
07:54:27:          GPU 0: Bus:2 Slot:0 Func:0 NVIDIA:7 GP104 [GeForce GTX 1070 Ti] 8186
07:54:27:  CUDA Device 0: Platform:0 Device:0 Bus:2 Slot:0 Compute:6.1 Driver:10.2
07:54:27:OpenCL Device 0: Platform:0 Device:0 Bus:2 Slot:0 Compute:1.2 Driver:440.64
07:54:27:***********************************************************************
07:54:27:<config>
07:54:27:  <!-- Slot Control -->
07:54:27:  <power v='FULL'/>
07:54:27:
07:54:27:  <!-- User Information -->
07:54:27:  <passkey v='********************************'/>
07:54:27:  <team v='11298'/>
07:54:27:  <user v='***********************************'/>
07:54:27:
07:54:27:  <!-- Folding Slots -->
07:54:27:  <slot id='0' type='CPU'>
07:54:27:    <paused v='true'/>
07:54:27:  </slot>
07:54:27:  <slot id='1' type='GPU'>
07:54:27:    <paused v='true'/>
07:54:27:  </slot>
07:54:27:</config>

07:54:27:Trying to access database...
07:54:27:Successfully acquired database lock
Comment 2 Manfred Knick 2020-03-24 12:30:01 UTC
CROSS-REFERENCE:

     Bug 712744
Comment 3 Manfred Knick 2020-03-25 17:23:09 UTC
"F@H on Gentoo"   HOWTO:

[ https://foldingforum.org/viewtopic.php?f=89&t=33333 ]
Comment 4 Larry the Git Cow gentoo-dev 2020-03-27 07:17:49 UTC
The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8590abe524112ff82b52b9a91ad120885f1e65fb

commit 8590abe524112ff82b52b9a91ad120885f1e65fb
Author:     Joonas Niilola <juippis@gentoo.org>
AuthorDate: 2020-03-27 07:15:22 +0000
Commit:     Joonas Niilola <juippis@gentoo.org>
CommitDate: 2020-03-27 07:17:34 +0000

    sci-biology/foldingathome: attempt to fix init and service files
    
     - non-maintainer commit, since axs seems to be inactive.
    
    Bug: https://bugs.gentoo.org/712744
    Bug: https://bugs.gentoo.org/714160
    Signed-off-by: Joonas Niilola <juippis@gentoo.org>

 .../{foldingathome-7.5.1.ebuild => foldingathome-7.5.1-r1.ebuild} | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)
Comment 5 Stephen Mollett 2020-03-27 14:59:51 UTC
This change breaks starting the client for me:

# /etc/init.d/foldingathome start
foldingathome      | * Starting foldingathome ...
foldingathome      | * command_background option used but no pidfile specified            [ !! ]
foldingathome      | * ERROR: foldingathome failed to start
Comment 6 Joonas Niilola gentoo-dev 2020-03-27 15:14:36 UTC
Did the previous version work for you? 

I don't get this error :\
Comment 7 Larry the Git Cow gentoo-dev 2020-03-27 16:25:17 UTC
The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=88b07eb3669c9c60ea17a9f0e7c4bbf6c4ca35d1

commit 88b07eb3669c9c60ea17a9f0e7c4bbf6c4ca35d1
Author:     Joonas Niilola <juippis@gentoo.org>
AuthorDate: 2020-03-27 16:22:40 +0000
Commit:     Joonas Niilola <juippis@gentoo.org>
CommitDate: 2020-03-27 16:24:59 +0000

    sci-biology/foldingathome: revert init fix
    
     - apparently it broke for some users, needs more testing and
       feedback.
    
    Bug: https://bugs.gentoo.org/714160
    Signed-off-by: Joonas Niilola <juippis@gentoo.org>

 .../{foldingathome-7.5.1-r1.ebuild => foldingathome-7.5.1-r2.ebuild}  | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
Comment 8 Stephen Mollett 2020-03-27 20:42:56 UTC
(In reply to Joonas Niilola from comment #6)
> Did the previous version work for you? 

The previous version worked fine most of the time, although I did occasionally get the error when stopping the service.
Comment 9 Joonas Niilola gentoo-dev 2020-03-28 08:05:08 UTC
*** Bug 715080 has been marked as a duplicate of this bug. ***
Comment 10 Ian Stakenvicius (RETIRED) gentoo-dev 2020-03-29 21:13:41 UTC
With the original issue, was foldingathome actually crashed/dead or was the openrc script identifying the crash due to i.e. a PID change?

Also please post emerge --info 

At this time, I cannot reproduce what you're seeing on any system I have tried with.
Comment 11 Manfred Knick 2020-03-30 08:42:29 UTC
(In reply to Ian Stakenvicius from comment #10)
Hi, Ian,
nice ti see you back!

> With the original issue, was foldingathome actually crashed/dead or was the
> openrc script identifying the crash due to i.e. a PID change?
The OP was a 1:1 copy'n'paste from terminal output.
 
I'm just in the process of completely cleaning up and re-building ...
More  to follow.
Comment 12 Manfred Knick 2020-03-30 09:33:28 UTC
o) emerge foldingathome

# grep foldingathome passwd
foldingathome:x:999:27:added by portage ...

# grep foldingathome group
foldingathome:x:981:

!) MISSING: no entry to video group               <-----

o) entering this manually ( vigr )                <---++

o) emerge --config foldingathome

as before, throws

./FAHClient: /opt/foldingathome/libssl.so.10:
             no version information available (required by ./FAHClient)
./FAHClient: /opt/foldingathome/libcrypto.so.10:
             no version information available (required by ./FAHClient)
./FAHClient: /opt/foldingathome/libcrypto.so.10:
             no version information available (required by ./FAHClient)

but continues accepting input values.

o) expanding PATH manually                         <---??

  PATH=$PATH:/opt/foldingathome
  export PATH

  ease "FAHClient  --send-pause" and the like

!) EVERY call to FAHClient will throw above 3 errors again

  but otherwise, seems to work.

# /etc/init.d/foldingathome start
 * Caching service dependencies ...                                                                                                                                                                                                                                                                     [ ok ]
 * Starting foldingathome ...                                                                                                                                                                                                                                                                           [ ok ]

+) +++ succeeds
+) +++ "WEB CONTOL" ( http://localhost:7396/# ) up and running


SUGGESTION:

-) fix "add to video group"

-) enhance "emerge --config  foldingathome"
   by asking machine-id with default value='0'

-) afterwards, close this BUG as "RESOLVED" "OBSOLETE"
Comment 13 Manfred Knick 2020-03-30 09:34:09 UTC
Created attachment 627252 [details]
emerge --info foldingathome
Comment 14 Manfred Knick 2020-03-30 09:44:15 UTC
Both
- libcrypto.so.10 -> ../../usr/lib64/libcrypto.so.1.0.0
- libssl.so.10 -> ../../usr/lib64/libssl.so.1.0.0
belong to openssl-compat:

# equery list -p dev-libs/openssl-compat

[-P-] [  ] dev-libs/openssl-compat-0.9.8z_p8-r1:0.9.8
[IP-] [  ] dev-libs/openssl-compat-1.0.2u:1.0.0            <-----


# equery uses dev-libs/openssl-compat

 - - abi_x86_32    : ...
 + + asm           : ...
 - - bindist       : ...
 - - gmp           : ...
 - - kerberos      : ...
 - - rfc3779       : ...
 - - sctp          : ...
 - - sslv2         : ...
 + + sslv3         : ...
 - - static-libs   : ...
 - - test          : ...
 + + tls-heartbeat : ...
 - - vanilla       : ...
 + + zlib          : ...
Comment 15 Manfred Knick 2020-03-30 13:16:05 UTC
Success of first WU :   WORKSFORME

including
- /etc/init.d/foldingathome start
- /etc/init.d/foldingathome status
- running a (GPU) WU
- /etc/init.d/foldingathome stop

including
- tail -n 80 -f /opt/foldingathome/log.txt

Unfortunately, besides "video group", I see no reasoning why ...


##### ##### ##### ##### ##### ##### ##### 
##### for comparison: my config.xml #####
##### ##### ##### ##### ##### ##### ##### 

<config>
  <!-- Configuration file created by FAHClient on 2020-03-30T08:57:49Z -->
  <!-- edited ... after first start/stop-cycle -->
  <!-- state: ... after running first (GPU) WU -->

  <smp value='true'/>
  <gpu value='true'/>

  <!-- Folding Core -->
  <checkpoint v='3'/>
  <cpu-usage v='75'/>
  <gpu-usage v='75'/>

  <!-- Slot Control -->
  <power v='FULL'/>

  <!-- User Information -->
  <passkey v='********************************'/>
  <team v='11298'/>
  <user v='******'/>
  <machine-id v='**'/>

  <!-- Work Unit Control -->
  <next-unit-percentage v='100'/>
  <stall-detection-enabled v='true'/>

  <!-- Folding Slots -->
  <slot id='0' type='CPU'/>
  <slot id='1' type='GPU'/>

</config>
Comment 16 Manfred Knick 2020-03-30 19:11:42 UTC
HINT:

. . . WEB CONTROL -> "Stop Folding" -> "Finish up, then stop"

seems not to work;

. . .  FAHClient --send-finish

does, reliable,
as well as

. . .  FAHClient --send-pause


config.xml Option

. . . <checkpoint v='3'/>

reduces loss of computational results,
compared to default value=15.
Comment 17 Jeff Hubbs 2020-04-04 17:39:23 UTC
After updating to 7.5.1-r3 I was able to configure and start it under openrc. It won't stop cleanly, though. I have also learned that user "foldingathome" needs to be included in the "video" group for GPU to work. I have yet to see a work unit come up that uses CPU since I made that change. Log has said:



16:23:33:WU01:FS01:Connecting to 18.218.241.186:80
16:23:33:WU01:FS01:Assigned to work server 40.114.52.201
16:23:33:WU01:FS01:Requesting new work unit for slot 01: READY gpu:0:GF119 [GeForce GT 610] from 40.114.52.201
16:23:33:WU01:FS01:Connecting to 40.114.52.201:8080
16:23:34:ERROR:WU01:FS01:Exception: 10002: Received short response, expected 512 bytes, got 0

but so far that's the extent of it.
Comment 18 Manfred Knick 2020-04-09 08:14:47 UTC
( Ian Stakenvicius from comment #10)
                   2020-03-29 21:13:41 UTC

( Manfred Knick    from comment #12)
                   2020-03-30 09:33:28 UTC 

> SUGGESTION:
@ Ian Stakenvicius: PING: R u alive?
Comment 19 Iade Gesso 2020-04-10 21:07:52 UTC
This new issue is blocking

emerge --config =foldingathome-7.5.1-r3 


Configuring pkg...

./FAHClient: /opt/foldingathome/libssl.so.10: version `libssl.so.10' not found (required by ./FAHClient)
./FAHClient: /opt/foldingathome/libcrypto.so.10: version `OPENSSL_1.0.1_EC' not found (required by ./FAHClient)
./FAHClient: /opt/foldingathome/libcrypto.so.10: version `libcrypto.so.10' not found (required by ./FAHClient)


Iade Gesso, PhD
Comment 20 Manfred Knick 2020-04-11 15:20:59 UTC
(In reply to Iade Gesso from comment #19)

WORKEDFORME (see above).

NEEDINFO:
Please, be so kind to supply.
Comment 21 Ian Stakenvicius (RETIRED) gentoo-dev 2020-04-27 16:06:42 UTC
I still can't reproduce -any- of these issues listed in this bug.

Could all of you report back after trying version 7.6.9?  Note that I am going to confirm soon if openssl-compat is actually required anymore, as there has been a report submitted that it isn't, and if so I will be pushing an -r1 to remove that dependency.
Comment 22 Jeff Hubbs 2020-12-09 17:06:10 UTC
I have good service start/stop on amd64 arch as of version 7.6.13