touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #28932
[Bug 1323648] Re: initctl scripts report "unknown job" on rpcbind and ypbind
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: upstart (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1323648
Title:
initctl scripts report "unknown job" on rpcbind and ypbind
Status in “upstart” package in Ubuntu:
Confirmed
Bug description:
root@u14:/etc/init# lsb_release -rd
Description: Ubuntu 14.04 LTS
Release: 14.04
root@u14:/etc/init#
root@u14:/etc/init# apt-cache policy upstart
upstart:
Installed: 1.12.1-0ubuntu4
Candidate: 1.12.1-0ubuntu4
Version table:
*** 1.12.1-0ubuntu4 0
500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
root@u14:/etc/init#
root@u14:/etc/init# apt-cache policy nis
nis:
Installed: 3.17-32ubuntu6
Candidate: 3.17-32ubuntu6
Version table:
*** 3.17-32ubuntu6 0
500 http://de.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
100 /var/lib/dpkg/status
root@u14:/etc/init#
3) On some fresh installations of Ubuntu 14.04, nis was post-installed via apt-get install nis.
On some installations, the installation notes a failure to start
rpcbind, ypbind, ypserv during the installation process. On other
installations, these processes start correctly.
Trying to use initctl scripts for these processes (after reboot)
fails, e.g.:
root@u14:/etc/init# status ypbind
status: Unknown job: ypbind
root@u14:/etc/init#
even though these processes get started correctly on boot normally.
init-checkconf sometimes reports the conf file as invalid. Never got
an invalid syntax with -d switch used on init-checkconf though.
root@u14:/etc/init# init-checkconf /etc/init/ypbind.conf
ERROR: File /etc/init/ypbind.conf: syntax invalid:
root@u14:/etc/init#
Sometimes init-checkconf reports invalid syntax on one run and valid
syntax on next run.
We did observe similar mis-behaviour after apt-get install ssh, so it
seems to be a problem with upstart and not nis.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: upstart 1.12.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
Date: Tue May 27 15:04:26 2014
ExecutablePath: /sbin/upstart-udev-bridge
InstallationDate: Installed on 2014-05-27 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcEnviron:
PATH=(custom, no user)
TERM=linux
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash
SourcePackage: upstart
UpgradeStatus: No upgrade log present (probably fresh install)
UpstartBugCategory: System
UpstartRunningSessionVersion: init (upstart 1.12.1)
UpstartRunningSystemVersion: init (upstart 1.12.1)
modified.conffile..etc.default.cups: [modified]
mtime.conffile..etc.default.cups: 2014-04-17T03:25:57
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1323648/+subscriptions