Incorrect upstart-job configuration

Bug #1222274 reported by Sebastian Audet
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
rpcbind (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Ubuntu: 12.04.3 LTS
Package: Installed: 0.2.0-7ubuntu1.2
From: http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages
Expected Behavior: Correct configuration, no boot-time warning
Incorrect Behavior:
  1) initctl check-config complains about a bogus event emitted, in rpcbind-boot.conf
  2) Invalid warnings about the .xdr files occur at boot time

Verbose Summary & Explanation (below):

There are multiple problems with the current upstart-job for rpcbind.

The first is that the upstart job events are incorrectly defined per the manual.

The second, is that upon boot rpcbind will complain of two missing files, /run/rpcbind/rpcbind.xdr and /run/rpcbind/portmap.xdr

The files changed (patch should be attached) provided fixes to both of these problems.

The solution is to include the correct line, and to not start with -w on boot, since -w implies a 'warmstart' which only makes sense if the rpcbind has recently been running. Instead, only run with -w when both files are present - both files should be created when the rpcbind terminates, by default.

Note: The patch is for the source package downloaded using:

'apt-get source rpcbind'

Note 2: there is a related bug in Debian, using init.d, not upstart:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620800

Also documented as an issue here:

http://unix.stackexchange.com/questions/13437/rpcbind-warning-on-boot

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: rpcbind 0.2.0-7ubuntu1.2
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
Date: Sat Sep 7 18:21:01 2013
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: rpcbind
UpgradeStatus: Upgraded to precise on 2012-05-14 (481 days ago)
mtime.conffile..etc.init.portmap.conf: 2013-09-07T18:16:00.121056
mtime.conffile..etc.init.rpcbind.boot.conf: 2013-09-06T23:12:01.614469

Revision history for this message
Sebastian Audet (smaudet) wrote :
description: updated
description: updated
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "generated diff patch using dpkg-diffs" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

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

This bug was fixed in the package rpcbind - 0.2.0-8.2ubuntu2

---------------
rpcbind (0.2.0-8.2ubuntu2) saucy; urgency=low

  * debian/rpcbind.rpcbind-boot.upstart: document that this job emits the
    start-rpcbind event. Thanks to Sebastian Audet <email address hidden>
    for the report. LP: #1222274.
  * Don't pass -w to rpcbind on boot up, since the files won't be there to
    be read. LP: #835833.
 -- Steve Langasek <email address hidden> Mon, 09 Sep 2013 02:38:53 +0000

Changed in rpcbind (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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