Ubuntu
boinc package

boinc-client fails to install/start, if ioprio_set is not allowed

Bug #218468 reported by Daniel Hahler on 2008-04-17

Affects		Status	Importance	Assigned to	Milestone
	boinc (Ubuntu)	Fix Released	Medium	Daniel Hahler

Bug Description

When installing/starting boinc-client in e.g. a OpenVZ container, it fails as follows:

Unpacking boinc-client (from .../boinc-client_5.10.45-1_i386.deb) ...
Setting up boinc-client (5.10.45-1) ...
* Starting BOINC core client: boinc_client
...done.
* Setting up scheduling for BOINC core client and children:
ioprio_set: Operation not permitted
invoke-rc.d: initscript boinc-client, action "start" failed.
dpkg: error processing boinc-client (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
boinc-client
E: Sub-process /usr/bin/dpkg returned an error code (1)

Revision history for this message

Daniel Hahler (blueyed) wrote on 2008-04-17:

debdiff for Hardy Edit (2.0 KiB, text/plain)

Daniel Hahler (blueyed) on 2008-04-17

Changed in boinc:
importance:	Undecided → Medium

Revision history for this message

Scott Kitterman (kitterman) wrote on 2008-04-17:

Ack. Gor it.

Revision history for this message

Sarah Kowalik (hobbsee-deactivatedaccount) wrote on 2008-04-17: Re: [Bug 218468] Re: boinc-client fails to install/start, if ioprio_set is not allowed

signature.asc Edit (252 bytes, application/pgp-signature; name="signature.asc")

status confirmed

Changed in boinc:
status:	New → Confirmed

Revision history for this message

Frank S. Thomas (fst) wrote on 2008-04-17: Re: [Bug 218468] Re: boinc-client fails to install/start, if ioprio_set is not allowed

unnamed Edit (189 bytes, application/pgp-signature; name=signature.asc )

Hi Daniel,

On Thursday 17 April 2008 02:33, Daniel Hahler wrote:
> ** Attachment added: "debdiff for Hardy"
> http://launchpadlibrarian.net/13530861/boinc_5.10.45-1ubuntu1.dsc.diff

     if [ ! -x "`which ionice 2>/dev/null`" ]; then
       log_progress_msg "ionice not found,"
     else
- ionice -c 3 -p $pid
- log_progress_msg "idle,"
+ if ionice -c 3 -p $pid 2>/dev/null; then
+ log_progress_msg "idle,"
+ else
+ log_progress_msg "idle not allowed,"
+ fi
     fi

If ionice fails does this always means that "ioprio_set" is not allowed? If
the answer to this question is no, I would rather suggest to echo a more
generic message like "ionice failed," or something similar.

If you want to, you can commit this into boinc's trunk.

Cheers,
--
Frank S. Thomas <email address hidden> PGP public key ID: 0xDC426429
Debian Developer finger <email address hidden>

Revision history for this message

Daniel Hahler (blueyed) wrote on 2008-04-17:

Thanks for your suggestion, Frank.
I've changed the warning to be more generic, like you've suggested and will commit it to pkg-boinc/trunk in a minute.

Changed in boinc:
assignee:	nobody → blueyed
status:	Confirmed → Fix Committed

Revision history for this message

Launchpad Janitor (janitor) wrote on 2008-04-18:

This bug was fixed in the package boinc - 5.10.45-1ubuntu1

---------------
boinc (5.10.45-1ubuntu1) hardy; urgency=low

  * debian/boinc-client.init:
    Do not fail, if ionice/ioprio_set is not allowed (LP: #218468)
  * Modify Maintainer value to match the DebianMaintainerField
    specification.

-- Daniel Hahler <email address hidden> Thu, 17 Apr 2008 02:31:28 +0200