Install issues on Ubuntu

[CatSpirent]

My install gives a number of warnings. I tried a backup anyway afterwards but it failed on creating the snapshot.
First I want to know if the install warnings are a problem in which case how do I resolve them.
Googling was of no use. Obviously the failed backup is irrelevant if I need to resolve the install warnings first.
=======================================================

Code: Select all

root@Docker1:/home/ckieffer/veeam# apt-get install veeam
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  apt-xapian-index aptitude-common augeas-lenses libapt-inst1.5 libaugeas0 libboost-iostreams1.46.1 libcgi-fast-perl libcgi-pm-perl
  libclass-accessor-perl libclass-isa-perl libcwidget3 libept1.4.12 libfcgi-perl libio-string-perl libnetcf1 libnl-route-3-200
  libparse-debianchangelog-perl libsigc++-2.0-0c2a libsub-name-perl libswitch-perl libxapian-1.3-5 libxapian22v5 libxtables10 python-xapian
  python3-xapian1.3 watershed
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  veeamsnap
The following NEW packages will be installed:
  veeam veeamsnap
0 upgraded, 2 newly installed, 0 to remove and 239 not upgraded.
Need to get 23.8 MB of archives.
After this operation, 51.8 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://repository.veeam.com/backup/linux/agent/dpkg/debian/x86_64 noname/veeam amd64 veeamsnap all 1.0.1.364 [73.5 kB]
Get:2 http://repository.veeam.com/backup/linux/agent/dpkg/debian/x86_64 noname/veeam amd64 veeam amd64 1.0.1.364 [23.7 MB]
Fetched 23.8 MB in 11s (2,159 kB/s)
Selecting previously unselected package veeamsnap.
(Reading database ... 112952 files and directories currently installed.)
Preparing to unpack .../veeamsnap_1.0.1.364_all.deb ...
Unpacking veeamsnap (1.0.1.364) ...
Selecting previously unselected package veeam.
Preparing to unpack .../veeam_1.0.1.364_amd64.deb ...
Unpacking veeam (1.0.1.364) ...
Processing triggers for systemd (229-4ubuntu8) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up veeamsnap (1.0.1.364) ...
Loading new veeamsnap-1.0.1.364 DKMS files...
Building only for 4.8.0-040800rc4-generic
Building initial module for 4.8.0-040800rc4-generic
Done.

veeamsnap:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.8.0-040800rc4-generic/updates/dkms/

depmod....

DKMS: install completed.
Setting up veeam (1.0.1.364) ...
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
insserv: warning: script 'atd' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `atd'
insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script `atd'
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
insserv: warning: script 'plymouth' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `plymouth'
insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script `plymouth'
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
insserv: warning: script 'ufw' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `ufw'
insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script `ufw'
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
insserv: warning: script 'libvirt-bin' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `libvirt-bin'
insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script `libvirt-bin'
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
insserv: warning: script 'udev' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `udev'
insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script `udev'
insserv: Script nsrps is broken: incomplete LSB comment.
insserv: missing `Provides:' entry: please add.
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'
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
insserv: warning: script 'whoopsie' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `whoopsie'
insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script `whoopsie'
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
insserv: warning: script 'apport' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `apport'
insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script `apport'
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
insserv: warning: script 'rsyslog' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `rsyslog'
insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script `rsyslog'
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
insserv: warning: script 'plymouth-log' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `plymouth-log'
insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script `plymouth-log'
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
insserv: warning: script 'procps' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `procps'
insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script `procps'
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
insserv: warning: script 'acpid' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `acpid'
insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script `acpid'
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
insserv: warning: script 'dbus' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `dbus'
insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script `dbus'
Processing triggers for shim-signed (1.18~16.04.1+0.8-0ubuntu2) ...

[PTide]

Hi,

Are you trying to install the agent inside a Docker container by any chance?

Thanks

[CatSpirent]

I don't think so, but docker is installed so it is always possible.

I am not sure how this system is set up. The engineers created it and asked if I could move it to a VM.
P2V failed, but I thought VEEAM agent also included that ability via restore from backup.
I figured it would also give me more experience installing the agent on a different flavor of Linux.

I can always just try to run dd of the disk and see if that will work.

That or as a last resort install a fresh Ubuntu OS on a VM and tell the engineers it is up to them to set it up like the old one.

[nielsengelen]

Looks like it's a broken Upstart package. Which Ubuntu version is this ?

[CatSpirent]

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS"
NAME="Ubuntu"
VERSION="16.04.1 LTS (Xenial Xerus)"


root@Docker1:/var/log# dpkg --list upstart
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-================================-=====================-=====================-======================================================================
ii upstart 1.13.2-0ubuntu21.1 amd64 event-based init daemon - essential binaries

[CatSpirent]

I was setting up a VM for the dd and it seems VMWare prefers BIOS boot but this PC is UEFI, so I may be better off with a fresh Ubuntu install and let the engineers practice their skills in duplicating their dev system setup skills. In the meantime, the dd copy to the VM disk is occurring, though when I do it, it always seems to take a while.

I did try a reinstall of the upstart just in case, but it didn't make a difference.

[nielsengelen]

Could it be this server has been upgraded through the years (from previous Ubuntu versions)? As Upstart has been replaced by systemd this might be the issue.

[CatSpirent]

Since it is an engineering development pc that they maintained, anything is possible.

You can close this item. I am guessing the best option is to start fresh.