Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 270134 (darf) - /etc/init.d/boinc attach fails with sched_setscheduler error
Summary: /etc/init.d/boinc attach fails with sched_setscheduler error
Status: RESOLVED NEEDINFO
Alias: darf
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-17 08:13 UTC by Nick Gotsinas
Modified: 2009-10-07 18:54 UTC (History)
1 user (show)

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


Attachments
emerge info (emergeinfo.log,9.16 KB, text/plain)
2009-05-17 17:57 UTC, Nick Gotsinas
Details
output of /etc/init.d/boinc --debug start (boinc_debug.log,49.63 KB, text/plain)
2009-05-20 03:24 UTC, Nick Gotsinas
Details
boinc.conf (boinc,447 bytes, text/plain)
2009-10-07 18:52 UTC, Tim Bowers
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Gotsinas 2009-05-17 08:13:31 UTC
Boinc fails to start when trying to attach, not sure what else I can show
I have no idea what the sched_setscheduler error means and google isn't helping either. 

%  /etc/init.d/boinc attach                                          
    Enter the Project URL: http://setiathome.berkeley.edu
    Enter your Account Key: mykey
 * Attaching to project ...                                               [ ok ]
sched_setscheduler: Invalid argument
failed to set pid 0's policy
sched_setscheduler: Invalid argument
failed to set pid 0's policy
sched_setscheduler: Invalid argument
failed to set pid 0's policy
sched_setscheduler: Invalid argument
failed to set pid 0's policy
sched_setscheduler: Invalid argument
failed to set pid 0's policy

It does however work if I start it manually:

% boinc_client --daemon --dir /var/lib/boinc --allow_remote_gui_rpc --attach_project http://setiathome.berkeley.edu/ mykey

The above works and does stuff, however the gui fails to connect.
Comment 1 Sebastian Luther (few) 2009-05-17 09:32:51 UTC
Please attach emerge --info and emerge -pvq boinc.
Comment 2 Nick Gotsinas 2009-05-17 17:57:46 UTC
Created attachment 191574 [details]
emerge info

emerge --info
Comment 3 Nick Gotsinas 2009-05-17 17:58:52 UTC
(In reply to comment #2)
> Created an attachment (id=191574) [edit]
> emerge info
> 
> emerge --info
> 

emerge -pvq boinc
% [ebuild   R   ] sci-misc/boinc-6.4.5-r2  USE="X server -cuda"
Comment 4 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2009-05-19 22:46:49 UTC
Please attach the ouptut of

  /etc/init.d/boinc --debug start

to this bug.
Comment 5 Nick Gotsinas 2009-05-20 03:24:46 UTC
Created attachment 191871 [details]
output of /etc/init.d/boinc --debug start
Comment 6 Tomáš Chvátal (RETIRED) gentoo-dev 2009-05-21 14:57:13 UTC
Are you using boinc under existing user?
Also arent you trying to run boinc as root, are you?
Comment 7 Tomáš Chvátal (RETIRED) gentoo-dev 2009-05-21 14:57:44 UTC
(In reply to comment #6)
> Are you using boinc under existing user?
> Also arent you trying to run boinc as root, are you?
> 

These two you can find by pasting your /etc/conf.d/boinc
Comment 8 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2009-06-06 14:07:11 UTC
Please attach your /etc/conf.d/boinc file as Tomáš requested.

Reopen this bug when you provide the requested information.
Comment 9 Tim Bowers 2009-10-07 18:52:55 UTC
Created attachment 206355 [details]
boinc.conf

/etc/conf.d/boinc
Comment 10 Tim Bowers 2009-10-07 18:54:08 UTC
(In reply to comment #9)
> Created an attachment (id=206355) [details]
> boinc.conf
> 
> /etc/conf.d/boinc
> 

I have the exact same issue - Wasn't sure if I should clone the bug? - Attached requested info, hope this helps