ifupdown expecting upstart where systemd exists

Bug #1652103 reported by flickerfly
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ifupdown (Ubuntu)
New
Undecided
Unassigned

Bug Description

I was doing an upgrade of a few utilities and noticed them output when ifupdown was upgrading.

Setting up ifupdown (0.8.10ubuntu1.2) ...
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
insserv: warning: script 'screen-cleanup' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup'
insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup'
Setting up initramfs-tools-bin (0.122ubuntu8.7) ...

After the upgrade I ran `status ifpudown` and received one of the same complaints.

$ sudo status ifupdown
status: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused

The same output occurs if I run this against networking.

$ sudo status networking
status: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ifupdown 0.8.10ubuntu1.2
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
Date: Thu Dec 22 07:53:25 2016
InstallationDate: Installed on 2012-12-29 (1454 days ago)
InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 (20120424.1)
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ifupdown
UpgradeStatus: Upgraded to xenial on 2016-08-04 (139 days ago)

Revision history for this message
flickerfly (josiah-ritchie) wrote :
Revision history for this message
flickerfly (josiah-ritchie) wrote :

Also, I've been able to repeat this on multiple 16.04 machines.

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.