package boinc-client 6.10.17+dfsg-2ubuntu2 failed to install/upgrade: /etc/init.d/boinc-client: 203: cannot create /proc/$PID/oom_adj: Directory nonexistent

Bug #512977 reported by josa
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
boinc (Debian)
Fix Released
Unknown
boinc (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: boinc

Upgrade of Boinc gave error message saying something on failing script. In synaptic however package versions are reported as 6.10.17+dfsg-2ubuntu2 for both Latest and Installed.
Boinc seems to be running fine and there is no update shown in Update manager any more.

I believe there was an Boinc update I got earlier today as well. Is this related to the reason for the new update?
Do not remember the actual message now but I think it was only what is in ErrorMessage bellow. I hope it is in the attached information,

ProblemType: Package
Architecture: amd64
Date: Tue Jan 26 22:11:47 2010
DistroRelease: Ubuntu 10.04
ErrorMessage:
 ErrorMessage: subprocess installed post-installation script returned error exit status 2
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: boinc-client 6.10.17+dfsg-2ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-11.15-generic
SourcePackage: boinc
Title: package boinc-client 6.10.17+dfsg-2ubuntu2 failed to install/upgrade:
Uname: Linux 2.6.32-11-generic x86_64

Related branches

Revision history for this message
josa (johnny-sander) wrote :
description: updated
Revision history for this message
Daniel Hahler (blueyed) wrote :

Thank you for your bug report.

The non-fatal error appears to be:

Setting up boinc-client (6.10.17+dfsg-1ubuntu1) ...
Installing new version of config file /etc/init.d/boinc-client ...
 * Starting BOINC core client: boinc
   ...done.
 * Setting up scheduling for BOINC core client and children:
/etc/init.d/boinc-client: 203: cannot create /proc/12306/oom_adj: Directory nonexistent
invoke-rc.d: initscript boinc-client, action "start" failed.
invoke-rc.d: release upgrade in progress, error is not fatal

Changed in boinc (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
summary: package boinc-client 6.10.17+dfsg-2ubuntu2 failed to install/upgrade:
+ /etc/init.d/boinc-client: 203: cannot create /proc/$PID/oom_adj:
+ Directory nonexistent
Revision history for this message
Dylan Aïssi (daissi) wrote :

Please merge boinc 6.10.17+dfsg-3 from Debian unstable to resolve this bug.

 boinc (6.10.17+dfsg-3) unstable; urgency=low

   * Ignore errors when setting oom_adj for boinc client,
     Thanks to Gábor Gombás <email address hidden> for the bug report
     and the hint for the solution. (Closes: #559053)
   * Fix str_replace.h installation path on boinc-dev package

 -- Rene Mayorga <email address hidden> Fri, 15 Jan 2010 19:34:46 -0600

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package boinc - 6.10.17+dfsg-3ubuntu1

---------------
boinc (6.10.17+dfsg-3ubuntu1) lucid; urgency=low

  * Merge from debian testing. Remaining changes:
    - Bump build-depend on debhelper to install udev rules into
      /lib/udev/rules.d, add Breaks on udev to get correct version.
    - Provide meta package "boinc", which depends on boinc-client and
      boinc-manager.
    - debian/control: libmysqlclient15-dev -> libmysqlclient-dev
      transition.
  * Fixes LP: #512977

boinc (6.10.17+dfsg-3) unstable; urgency=low

  * Ignore errors when setting oom_adj for boinc client,
    Thanks to Gábor Gombás <email address hidden> for the bug report
    and the hint for the solution. (Closes: #559053)
  * Fix str_replace.h installation path on boinc-dev package
 -- Daniel Hahler <email address hidden> Sat, 13 Mar 2010 01:06:53 +0100

Changed in boinc (Ubuntu):
status: Triaged → Fix Released
Changed in boinc (Debian):
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.