Solve with SaltStack: initctl: `Unable to connect to Upstart: Failed to connect to socket / com / ubuntu / upstart: Connection refused
I got the following error when I tried to "stray" on standard ubuntu / vivid64 using virtualbox: initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
The full bug stream is here: https://pastee.org/hnh8x
Don't forget to say hello to our old friend stdin: is not a tty
.
Please find the corresponding one Vagrantfile
here: https://pastee.org/sfyb7 , created with vagrant init --force ubuntu/vivid64 https://cloud-images.ubuntu.com/vagrant/vivid/current/vivid-server-cloudimg-amd64-vagrant-disk1.box
.
Can this error be corrected with Saltstack preparation? If so, how?
Below is the closest bit of documentation on Saltstack related to Upstart: http://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.upstart.html
The Ubuntu documentation for this topic, https://wiki.ubuntu.com/SystemdForUpstartUsers , recommends installing the package upstart-sysv
. Is that all it takes to go back with Saltstack?
The following issues do not appear to fix boot issues:
upstart-sysv:
pkg.installed
Is there anything I can add to this to help solve the problem?
source to share
Vivid now uses systemd instead of upstart.
You can try "sudo systemctl start" instead.
I'll post some of the content: https://wiki.ubuntu.com/SystemdForUpstartUsers . I ran into this issue with Ceph and used the above method to get around it.
Introduction
This document compares Upstart and systemd to help you transition to the latter.
Support status
First, it's important to note that systemd is only supported on Ubuntu 15.04 and later. While systemd is available in previous releases through the Ubuntu repositories, there is a lack of support for these releases, as noted here. Therefore, it is recommended that you use the default excerpt for previous releases.
System Init daemon
This changed as part of the Ubuntu 15.04 development cycle.
Ubuntu 15.04 (using Systemd by default):
Systemd runs with PID 1 as /sbin/init.
Upstart runs with PID 1 as /sbin/upstart.
Previous versions (using Upstart by default):
Upstart runs with PID 1 as /sbin/init.
Systemd runs with PID 1 as /lib/systemd/systemd.
Switching init systems
If you are using Ubuntu vivid (15.04), you can easily switch between upstart and systemd as you see fit, since both packages are currently installed. As of March 9, 2015 bright has been changed to use systemd by default, before upstart was the default.
Switch to upstart for one boot
In grub select "Advanced Options for Ubuntu" where you will find the entry "Ubuntu with Linux ... (upstart)". This will be loaded with init = / sbin / upstart.
If you have upstart-sysv installed and thus boot from the default upstart, the entry "Ubuntu with Linux ... (systemd)" will appear and will boot with init = / lib / systemd / systemd.
Permanent switch back to upstart
Install the upstart-sysv package, which will remove ubuntu-standard and systemd-sysv (but shouldn't uninstall anything else - if so, yell!) And run sudo update-initramfs -u. After that, the grub "Advanced Options" menu will have a corresponding "Ubuntu with Linux ... (systemd)" entry where you can do a one-time boot using systemd.
If you want to revert to systemd, install the systemd-sysv and ubuntu packages.
Currently, you can switch to the upstart, inform the package developers about the need for systemd support.
source to share